Dingoonity.org

wow thanks hi-ban for this new release

thanks!

Daaaaaamn, that's a lot of changes from 5.0 --> 5.1. 

I've installed, using the latest firmware, and it worked for some minutes. Now, when I load it, it automatically loads the save file and as soon as I touch any control it crashes to the os.

Thanks for your work

I've deleted the files on the savestate folders and now the game works fine. The problem is that it crashes when I try to select vsync on.

Many options on the game menu are leftovers from the PC version (because the game thinks it's running on a PC). So don't expect everything to work there.

Things i'm aware don't work are window/fullscreen option (nothing happens when you change it) and the vsync option (game crashes). You also shouldn't touch the controls, as they are set to the GCW buttons from a PC, i think because there was some problem when redefining them from the GCW.

I might try some different configurations, and see what works better, though.

Is there any chance of working vsync or triple buffer in the future? The tearing is very noticiable without it.

No. Unless the author of the game makes a specific build for the GCW Zero. Which is unlikely, because the project was removed from public distribution by SEGA.
As far as i know the author is spanish, so you could try to find and convince him if you want.

What are the controls? I've had a couple of crashes, so I accidentally discovered that there are save states. Is there a direct way to create a save state and exit? Or just create a save state?

Thanks!

So, recently a new SORR version (v5.1) was discovered on the net.

Any chance you could provide the Windows and/or Linux versions? I can't seem to find them.

I've been experiencing a surprising number of crashes. They seem to appear only on certain levels, and at times when I think the game might be loading a lot of resources from disk. Unfortunately, the savestates are even more prone to crashes; they usually crash while the player health bars are still filling.

I've tried adjusting the SD cards' read-ahead buffers, but I don't see any change.

I know you're not the maintainer--whoever that is--but if you have some kind of workaround... ?

It's strange, because i don't have any of those problems.
Anyway, no, there is no workaround.

The reason you don't have any of those problems is because I cranked up the SD read-ahead buffer from a default of 128KiB to 2048KiB to... partially ...fix stuttering problems in Sega CD games and Scummvm games with big audio files.

Apparently, trading off random access speed for sustained transfer rate on the SD cards makes SoRR twitchy and prone to crashing. Or I may have found an SD-related bug in the firmware. I just re-tested after moving my initscript to change the SD buffer sizes; a savestate that had a 100% chance of crashing SoRR about 1 second into initializing the stage now causes no problems at all.

Think there's any chance of a tool to change SD buffer sizes in the Zero's GUI? Per-OPK settings stored in the metadata and a little bit of code to change the buffer size while loading games?

Some games benefit a lot more from the sustained transfer rate improvement, and some benefit a lot more from the random access speeds. SoRR is the only app that outright crashes if it doesn't have the random-access speed it's looking for, however.