SpritesMind.Net

If that's the problem then I won't worry about it too much. I'm eventually going to add in the option for the user to completely customize the color palette to their tastes.

http://www.mediafire.com/download/t7gx8ovfokdxdb3/YMDJreg80.bin

That's the most recent working one. But the current version ...

http://www.mediafire.com/download/t7gx8 ... Jreg80.bin

This works on real hardware. However it's not completely current, I'm in the middle of rewriting code for better ram usage so the most current one is unavailable.

Posting in the main thread again because I have a comment.

There needs to be some sort of timer to count how long a direction button is pressed and act accordingly. Currently the cursor will slide across the screen at a fast pace even if you tap the button for very little time. This makes it hard ...

Thanks to TascoDLX and Jazzmarazz for helping get this tracker working on real hardware. Now a new issue is apparent. These are the pictures Jazzmarazz posted of YMDJ being run on a model 3 Sega Genesis and HD screen.

http://i.imgur.com/M86MZYnl.jpg
http://i.imgur.com/YED3Dc6l.jpg
http://i ...

Thanks so much for testing. Maybe they're both the fix haha. I haven't a clue why the font looks like that... Is it really as pixellated as it looks?

Btw, I had a look at your disassemblies, and noticed you like to keep spare parts. I have an HP stereoscopic 3d monitor 1920x1080, that recently ...

I misunderstood then.

The first link is with the loop count set to 12 https://www.mediafire.com/?ffaa00nfrm05k4k

The second link is with register 17 set to 80 https://www.mediafire.com/?t7gx8ovfokdxdb3

All the dma regs were initially set to 00 anyways so maybe I'm still misunderstanding but ...

https://www.mediafire.com/?u1juo2h3j6rwfr5

In this test version, I put a loop counter that gives it an extra few seconds before beginning the main program. It still shows the font changes in the emulator, so I suspect this won't work. The next thing I'll try is fixing the ending rom address.

Well it's probably been more than a couple of hours. I managed to get my array drawing routines working for reading my new arrays and displaying their data to screen, but I can't test their functionality 100% until I fix a crash I'm having. There's alot of variables involved that tie in to this so I ...

Still changes the font in an emulator and hangs on real hardware. Keep trying pal! I bet you're close.

There was something I read in another thread around here that caught my attention. This may be related to the problem. I'll work on it in another hour or two, after I get some of this code ...

Thanks for the useful information friend. I corrected the issues you mentioned, and now after reading some of those posts have a feeling there will be more even once this gets running on real hardware.

Well... here goes nothing.
https://www.mediafire.com/?l8dsi6pyiosyeqh

The TMSS is thusly satisfied then. Meaning I'm going to have a real trick debugging this crash. I'm taking a look at that source in that link you posted and am impressed, it seems to me that the rom header can be nearly trashed and still work fine as long as SEGA is there. Really impressive is Pong ...

Yes, I'm saying that what if that attempt to load the font and palette too early is what causes the crash? Or maybe some register wasn't set up properly or something. I'm starting to think the problem is after the TMSS check and before the palette is loaded in my code.

If it's not poor emulation, and if the same thing is happening on real hardware then that would basically mean that my palette and font is loaded into VRAM before TMSS is complete. Which makes debugging very interesting.

I came across something interesting. I don't know how useful Fusion can be, but you can load the TMSS bios into it. Well I started up the YMDJ v005 rom in Fusion with the bios enabled and it showed the TMSS, and although it does load the tracker, the TMSS font is visibly replaced with my font before ...

Jazzmarazz, I sent you a PM @ chipmusic but I don't know if you got it... Here's the code after the TMSS. It's 68k yes, but it's interacting with the z80, perhaps you'll see something I don't. The declared #Z80DATA address label points to the data at the bottom of this post ...