Page 2 of 3
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Fri Jul 14, 2023 10:53 am
by SolidSonicTH
They had to set it to be free play in the initial release somehow, though. So there must be a way to change the values in the game.
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Fri Jul 14, 2023 12:44 pm
by MoeFoh
SolidSonicTH wrote:They had to set it to be free play in the initial release somehow, though. So there must be a way to change the values in the game.
It might be - Difficulty (Very Hard), round count (3), and damage level (110%) are at defaults (unchanged) on the OG sram. I've seen enough to think this probably isn't going to work. After all, it is a prototype. Maybe megavolt85 can chime in on his thoughts? I would like verification the dd command parameters are correct, however.
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sat Jul 15, 2023 3:10 pm
by megavolt85
hell i don't know why but i can't enter service menu on demul
note that demul saves a sram file called dummy.sram
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sat Jul 15, 2023 3:51 pm
by megavolt85
SolidSonicTH wrote:Difficulty (Very Hard), round count (3), and damage level (110%). May have been one other thing.

- Снимок экрана от 2023-07-15 22-38-15.png (7.87 KiB) Viewed 2671 times
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sat Jul 15, 2023 6:19 pm
by MoeFoh
megavolt85 wrote:SolidSonicTH wrote:Difficulty (Very Hard), round count (3), and damage level (110%). May have been one other thing.
Снимок экрана от 2023-07-15 22-38-15.png
force5.zip
Now, insert that into the Dreamcast image, run on real Dreamcast hardware and you'll see the problem.
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sat Jul 15, 2023 9:02 pm
by SolidSonicTH
It even happens if you just load the GDI on Demul before moving it to an SD card.
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sun Jul 16, 2023 4:32 am
by megavolt85
SolidSonicTH wrote:It even happens if you just load the GDI on Demul before moving it to an SD card.
have you tried pasting sram from my previous post? it is obtained from the dc version of the game by cutting sram from RAM. and yes, I tried to insert it into the image and it works for me, now you need to understand what exactly does not work for you. paste my sram file and tell me the result
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sun Jul 16, 2023 6:42 am
by MoeFoh
megavolt85 wrote:SolidSonicTH wrote:It even happens if you just load the GDI on Demul before moving it to an SD card.
have you tried pasting sram from my previous post? it is obtained from the dc version of the game by cutting sram from RAM. and yes, I tried to insert it into the image and it works for me, now you need to understand what exactly does not work for you. paste my sram file and tell me the result
Digging sram out of RAM is working!
Tested on real hardware using GDEMU 5.15.
Here's my test build to download:
https://www.mediafire.com/file_premium/ ... 29.7z/file
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sun Jul 16, 2023 8:45 am
by megavolt85
most likely converted for Naomi rom does not have access to the atomiswave settings menu.
when did you set up the game via demul settings window like in my screenshot?
Re: Help with patching SRAM into Force Five (and possibly other Atomiswave GDIs)...
Posted: Sun Jul 16, 2023 9:32 am
by MoeFoh
megavolt85 wrote:most likely converted for Naomi rom does not have access to the atomiswave settings menu.
when did you set up the game via demul settings window like in my screenshot?
Loaded encrypted forcefive.bin from naomi load screen in demul. No problem getting to settings menu using 'test' switch. But, the sram created and later inserted into track03 caused a game failure.