SpritesMind.Net

That's awesome - thanks!

Yeah I built the code before so that shouldn't be a problem. I used VS2017 last time, it looks like the project files have been upgraded to VS2022, is there anything else I'll need to change if I pull down the latest repo?

Thanks for replying, and great news that Exodus is being developed again! I ended up hacking the source code to add what I needed, writing to a certain address would trigger the emulator to write the current time to a text file. Bus tracing would be overkill I think as I just want to be able to figu...

I guess more helpful where be a tool, that cold do this trick from GameHut sleeve: Unforuntately you can't get 3375 colours, because you can't indepently set shadow/highlight mode for individual R,G,B channels. The standard 3-bits per channel gets you 512 colours. Shadow mode gets you an additional...

I have a different question if you don't mind. I assume the numbers in that table are for DMA transfers. I've seen a lot of people quoting the official SEGA development manual as saying: The DMA is quite fast during VBLANK. About double the tightest possible 68K loop speed, but during active scan th...

Thanks. I'm doing a variation of that currently using the background colour, but there are some limitations, you can't see what's going on during h-blank and v-blank, and it's a very manual process. It feels like it would be easy for an emulator to provide timing data directly...

Hi I'm looking to perform some timing analysis of my ROM to find out which parts of the code are using the most cycles. I can't seem to find any tools for doing this in Exodus 2.1 (there is a trace feature but it only records which instructions are executed, not when). Ideally I'd like to be able to...