Open bbeamz opened 1 year ago
I really really (REALLY!) appreciate you reporting this in so much detail. hope the devs take a swing at fixing this!
does the same happen for 60fps ?
does the same happen for 60fps ?
It's mostly fine at 60 fps, the dragon is a bit slower, but the animation is not glitchy.
There are numerous bugs when playing at 120 fps, I really don't recommend it.
Describe the issue
After trial-and-error to determine which version broke this, after upgrading from BOTW graphics pack
v833
-->v834
+ (seems to be all graphics pack versions afterv833
), enabling FPS++ causes Dragon pathing animations (tested Farosh and Dinrahl) to be between 1/3 - 1/4 normal speed. This also causes them to distort in strange ways after you shoot them and their "escape to the sky" animation triggers.I have 3 test case videos below:
v833
@ 120fpsv897
@ 120fpsv833
-->v834
as the point of breakage]For these test cases / videos, the following setup exists:
VIDEO: FPS++ disabled (baseline)
Notes:
VIDEO: FPS++
v833
@ 120fpsNotes:
VIDEO: FPS++
v897
@ 120fpsNotes:
To Reproduce
Steps to reproduce the behavior:
v834
or laterv8343
, enable FPS++ with similar configs, and observe that this behavior does not occurExpected behavior
Dragons should path at normal 30fps real-world speed (and same speed prior to Graphics Pack
v833
). Their sky ascent animation should also not be glitched/distorted.In general, the newest version(s) of FPS++ have fixed a lot of the old issues running at 60+FPS. However, the dragons being broken is very game breaking, as they're meant to be encountered "naturally," and needing to manually relaunch CEMU with new FPS settings is very immersion-breaking.
Even the solution of downgrading FPS++ to
v833
is sub-optimal, because ragdoll physics are very broken around the 120fps mark (an issue which is mostly fixed in newer version).Screenshots
See description above for videos. Additionally, here are some screenshots of CEMU config:
FPS++ graphics pack
v897
setupOLD
v833
FPS++ config used in videos in Description above:Desktop (please complete the following information):
v2.0-36
(or any version within the last year-ish); Graphics Pack version(s)v834
+Additional context Was able to verify by manually downloading previously releases, that graphics packs v833 and earlier do not cause this issue for BOTW.