-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optional fast loader integration for Ozmoo when used with REU #72
Comments
We did look for solutions to do fastloading several years ago. We found it hard to figure out how to do it properly ourselves, and no one else stepped up to help. Existing solutions tend to support file load only, and that doesn't help, as game data is stored in raw disk sectors. Loading from SD2IEC is a bit faster, as it eliminates seek times and read times, it's just transmission of data that takes time. I think JiffyDOS also speeds up block reads, and should be compatible with Ozmoo. |
Yeah, I was fearing that a JiffyDOS mod might be in order. I do like the optionality of Action Replay. You can simply unplug it and don't need to hardware mod any device. I will try and check out some of the software based fastloaders... |
Well, it seems all the usual software fastloaders that you load before a game don't work. They don't accelerate loading stuff after the program's start. |
Very few fastloaders can speed up raw block reads. They usually speed up LOAD operations only, or LOAD and SAVE. |
Yesterday we started playing Sherlock using Ozmoo on the C64. Using an Action Replay 6, load times are quite bearable, but since Sherlock is quite complex it has to load A LOT. This slows down playing experience. Instead I now opted to use my REU to cache the game in memory, which eliminates all load times (on my 256K REU), but takes about 5 minutes to load the game into memory at startup. Would it be possible to optionally build Ozmoo with an integrated fast loader for this exact purpose? I can't plug in the REU and AR6 at the same time to achieve the same result.
The text was updated successfully, but these errors were encountered: