Virtual Jaguar v1.0.5 (support) thread

[nwagenaar]

Since we can expect Virtual Jaguar v1.0.5 real soon, I decided to start e new thread about the upcoming version.

Please discuss everything about this version (bugs, todo, what you think about it, etc) and maybe we can help you or resolve issues in the next version

A big thanks goes out to Shamus, he made enormous progress during my absence/vacation. Keep up tha good work! BTW, your humor in the sourcecode is quite funny to read

Virtual Jaguar v1.0.5 is released!

- Source can be downloaded from here
- The WIN32 binary can be downloaded from here

Regards,

Niels Wagenaar
SDLEMU Crew

[}{eretic]

Hi...

I emailed your website yesterday about this project and as I promised in the email, here is the fix for the game Flipout...

// Fix for Flipout!
if (jaguar_mainRom_crc32 == 0x6f57dcd2)
memset(jaguar_mainRom + 0x200000, 0x1, 0x200000);

The game seems to run fine after this...I hope that helps...I have it doing this in the rom loading function but it may take a little more coercing in your version...

Chris

[nwagenaar]

Hi Chris!

I indeed saw your e-mail but just didn't have any time to reply all my e-mails I'm a bit curious, do you also use the Virtual Jaguar GCC/SDL emulation core for you project? Perhaps we can work together at this point to enhance the emulation

And thank you for this fix! We will add this to the CVS of Virtual Jaguar

Regards,

Niels Wagenaar
http://sdlemu.ngemu.com

[}{eretic]

At this point no....I switched over to Direct Draw and Input because of SDL's lack of a stretchBlt function, so I could change the display size...I do however have a older version that did use SDL with a menu...I would be happy to work with you on some level...

Your very welcome for the fix,
Chris

[Shamus]

Originally Posted by }{eretic

// Fix for Flipout!
if (jaguar_mainRom_crc32 == 0x6f57dcd2)
memset(jaguar_mainRom + 0x200000, 0x1, 0x200000);

The game seems to run fine after this...I hope that helps...I have it doing this in the rom loading function but it may take a little more coercing in your version...

Hm. In general, I'd rather not use any game specific hack like this, because it means that there is something in the hardware that we don't understand. The original source code was littered with this kind of stuff and all it does is make the source that much harder to debug and maintain.

From a quick scan of your patch and looking at the file size of the Flipout ROM, it looks like the Jaguar hardware is returning a value of $01010101 in each longword of the ROM address on attempts to read where there is no physical ROM. If this is the case, then it would be worthwhile to do this on the hardware level instead of just for this one ROM...

Anyway, if you run into any other little nuances like this, please do tell us about it! Without an actual Jaguar and an attached debugger, we can't really test these things directly.

[}{eretic]

I completely understand that...No one likes cluttered code...But if it leads everyone down the right path then I'm happy If I come across anything else I'll let you know...

BTW.... the 0x1 in the memset() was arbitrary. I think any non-zero value would work...But you're right, if there are other games that behave this way the hardware level is better...

Chris