You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Maken Shao patch provides a no-interlacing code but pushes a PAL Interlaced format into a NTSC Progressive format, making it into a 60 FPS game too. It desyncs every FMV by playing them too fast and considering every cutscene is pre-rendered, this pretty much makes the story impossible to follow.
The description of the no-interlacing code doesn't provide any mention of a 60 FPS framerate mode coming with the no-interlacing option. I think this will make it a worse experience for players to leave it as is
Removing the second line patch=1,EE,202000c4,extended,24050002 brings it back to a PAL Progressive format and removes the 60 FPS NTSC format stuck in there. As long as FMVs remain desynced without an included fix, I think this line should be removed from the patch and have a more accurate comment description to users. Sorry I'm not familiar enough to make the fixes myself
The text was updated successfully, but these errors were encountered:
The Maken Shao patch provides a no-interlacing code but pushes a PAL Interlaced format into a NTSC Progressive format, making it into a 60 FPS game too. It desyncs every FMV by playing them too fast and considering every cutscene is pre-rendered, this pretty much makes the story impossible to follow.
The description of the no-interlacing code doesn't provide any mention of a 60 FPS framerate mode coming with the no-interlacing option. I think this will make it a worse experience for players to leave it as is
Removing the second line
patch=1,EE,202000c4,extended,24050002
brings it back to a PAL Progressive format and removes the 60 FPS NTSC format stuck in there. As long as FMVs remain desynced without an included fix, I think this line should be removed from the patch and have a more accurate comment description to users. Sorry I'm not familiar enough to make the fixes myselfThe text was updated successfully, but these errors were encountered: