Game Modification: 60 FPS Hacks and Patches

[masterotaku]

(10-13-2016, 07:29 PM)retroben Wrote: There is a chance that a value of 01 or 02 can be changed to make the game run at 60fps because I managed to get a similar result to the previous black flickering fake 60fps one but near that 8027 address range.

I tried a handful of close values with savestate exploiting and eventually hit that particular address with flickering.

Seizure Warning
80272A34 2C0000xx
Not realtime if that wasn't already obvious.
00=Also Flicker Fake 60fps
01=Flickering Fake 60fps
02=Default

Interesting fact: Using the fast 60fps code with this makes the counter reach 120fps at default clock speeds but with 60VI/s,hence the flickering.

Aaaaaawweeeessssoooommmmeeeee!

With the 80272A34 2C000001 code I can use Zelda TP perfectly at 30fps! No more motion blur, no more double image... it's perfect. I can totally endure 30Hz strobing . I tried it with 3D Vision (smooth and perfect, instead of having double strobing) and also in 2D with my G-Sync+ULMB trick (getting perfect 30fps too. I need your code because I would get double strobing under 40fps). I guess if someone doesn't use vsync, it will behave badly.

If you can do the same for Wind Waker or the PAL version of Zelda TP too (or other 30fps games you want), I would appreciate it eternally.


Black frame insertion is something I have been wanting as a feature in Dolphin for years (there is no way I can have strobing under 38-40fps with this monitor, and 50fps with the previous one). Having it at least in a few games is cool too.

[retroben]

wat

It doesn't seem consistent on my end though,maybe Windows DWM causes that problem for me but in general it tears the screen viciously at times and otherwise stays black ("fake 60fps" fully) or runs at normal 30fps in small moments too.

[masterotaku]

(10-14-2016, 05:01 AM)retroben Wrote: wat

It doesn't seem consistent on my end though,maybe Windows DWM causes that problem for me but in general it tears the screen viciously at times and otherwise stays black ("fake 60fps" fully) or runs at normal 30fps in small moments too.

Use exclusive fullscreen with vsync at 60Hz (try not using "adaptive vsync" in the drivers just in case. I also set vsync to "Force on" there). It should work. At least it does for me with 3D Vision, which doesn't even use G-Sync. Synchronization is perfect for me.

[retroben]

Due to huge similarities,I eventually found the NTSC Wind Waker address quickly in mere moments by knowing its 32bit value and searching only a few slots in the memory viewer.

Seizure Waker
80255ADC 2C0000xx
00=Also Fake 60fps Flickers
01=Fake 60fps Flickering
02=Default

[masterotaku]

Mmmm, this one doesn't work for me. Weird. One of our ISOs is busted or there is something else going on.

[Meowmaritus]

(10-14-2016, 07:04 AM)masterotaku Wrote: Mmmm, this one doesn't work for me. Weird. One of our ISOs is busted or there is something else going on.

Make sure you're adding it as a patch and not an AR code (AR codes start with a prefix like 04 so I'm pretty sure its a patch)

[masterotaku]

(10-14-2016, 07:23 AM)Meowmaritus Wrote: Make sure you're adding it as a patch and not an AR code (AR codes start with a prefix like 04 so I'm pretty sure its a patch)

Oh, OK. I was adding it as an Action Replay code. Zelda TP worked as an AR code, weirdly. I'm in bed now, but I'll try to try it before going to work, in 7 hours.

[retroben]

Maybe Wind Waker's boot sequence is faster or something?
This can make codes not work even on boot cycles thanks to cached ram on dynarec being the common cause.

Still would be hugely grateful if a developer or even anyone else could create a fix (that would technically make it more accurate) to make ASM related address cache update whenever the real RAM for it has been changed,much like savestates can do when loading one right after saving it over an ASM address value change which is what I used to find that "flickering fake 60fps" code with great success.
Like N64 emulation such as Mupen64Plus AE,it may have a "non-shader" stutter whenever these values are changed,but that wouldn't matter since these ASM-altering codes in Dolphin usually never work for changing in realtime on dynarec while Interpreter wouldn't stutter at all.

Also,this is the reason size mods for Wind Waker (e.g Seagulls and Red Lion Boat "d-pad" by Cosmo Cortney) outright don't work on Dolphin for everything except Link himself oddly.

[Meowmaritus]

So about the flickering black code: The game switches between updating the audio thread and updating the video thread. I believe the black frames are during the audio thread's updating. Anyways, I've been trying to reduce the amount of time the video thread sleeps after each update, with absolutely no success whatsoever.

Pretty much every single change:

• Does absolutely nothing.
• Hard crashes the entire game (even the music freezes).
• Soft crashes only the video (the video freezes and the music continues).
• CAUSES DOLPHIN TO CRASH
  

Edit: I even tried rerouting the OSGetTime function to a custom function created in blank memory which halves the amount of time that has passed, but it just crashes the game:

Code:

043095EC 7C6D42E6
043095F0 7C8C42E6
043095F4 7CAD42E6
043095F8 60000000
043095FC 48CF8505
04309600 4E800020
05001B00 3A200002
05001B04 7C848BD6
05001B08 7C638BD6
05001B0C 7CA58BD6
05001B10 7C032800
05001B14 4E800020

Edit 2: Forgot to mention that the above is an AR code. Using a patch with the same effect also crashes the game.

[theboy181]

(10-14-2016, 06:15 AM)retroben Wrote: Due to huge similarities,I eventually found the NTSC Wind Waker address quickly in mere moments by knowing its 32bit value and searching only a few slots in the memory viewer.

Seizure Waker
80255ADC 2C0000xx
00=Also Fake 60fps Flickers
01=Fake 60fps Flickering
02=Default

I cant seem to get this code to work? Wat am I missin?