Exchord | Baten Kaitos 2 HD in 17:57 (PC, 24-165 Hz) @Exchord | Uploaded July 2024 | Updated October 2024, 2 hours ago.
A few mistakes here and there, but I don't think it's worth improving any further. Plus, I suspect this run may violate some future rules for competitive leaderboards.
Notes:
- Chinese text: This saves time on dialogue because there are fewer characters to advance through. It seems consistently faster than Japanese, Korean, and English.
- 165 FPS: I'm generally playing at 165 FPS, even though video recording happens at 60 FPS. There is some frame-based logic in the game that high framerates benefit from. For example, Tarazed's elevators move 2.75 times faster than they're supposed to, regardless of the Game Speed setting. This is because the remaster was designed for 60 FPS, not 165 FPS.
- 24 FPS: At a few points in the run, I change the display refresh rate to 24 Hz to perform tricks that would otherwise be inconsistent or not possible. For example, Travel Log Mode at 1:06 and 5:35 is very inconsistent at high framerates. At 7:04, I have to slow down the game for TLM because otherwise the cutscene would not play at the end (though it wasn't usually as laggy as this time). At 8:08, playing at 24 FPS delays the map loads, allowing me to warp to Tarazed. Otherwise, I would warp to Cujam instead.
- Ending: The PC version doesn't have the 30 second delay on the black screen before "The story continues to Baten Kaitos" (at least not at high framerates). In the Switch version, I would have had to use a glitch to save those 30 seconds.
Window Mode: Full Screen
Resolution: 2560 x 1440
Vertical Sync: ON
Anti-aliasing: High
Gamma Correction: 0
It seems that when Vertical Sync is turned off, the game runs at ~120 FPS regardless of the display refresh rate set in Windows. For comparison, I did a test run with Vertical Sync off, and it clocked in at around 18 minutes and 24 seconds.
Auxiliary tools: AutoHideMouseCursor, JoyToKey, NirCmd
For gameplay, I'm using a Switch Pro controller. I turned off "Use Nintendo Button Layout" in my Steam settings and increased the right stick deadzone to the maximum.
For framerate switching, I use two buttons on an Xbox 360 controller. These buttons are assigned a "Special" function in JoyToKey that launches nircmd.exe with the parameters "setdisplay 2560 1440 32 24" or "setdisplay 2560 1440 32 165".
If you want to learn more about glitches used in this run, check out these links:
docs.google.com/document/d/1R58dc43Z1AU-zFzkWlojPFhlGPQRLaRbAFN4pq_d2cU/edit?pli=1
youtube.com/watch?v=l0s_LDiGYK4
youtube.com/watch?v=-dZ2fferK0M (video description)
youtube.com/watch?v=IFVSs1ANe1U (video description)
A few mistakes here and there, but I don't think it's worth improving any further. Plus, I suspect this run may violate some future rules for competitive leaderboards.
Notes:
- Chinese text: This saves time on dialogue because there are fewer characters to advance through. It seems consistently faster than Japanese, Korean, and English.
- 165 FPS: I'm generally playing at 165 FPS, even though video recording happens at 60 FPS. There is some frame-based logic in the game that high framerates benefit from. For example, Tarazed's elevators move 2.75 times faster than they're supposed to, regardless of the Game Speed setting. This is because the remaster was designed for 60 FPS, not 165 FPS.
- 24 FPS: At a few points in the run, I change the display refresh rate to 24 Hz to perform tricks that would otherwise be inconsistent or not possible. For example, Travel Log Mode at 1:06 and 5:35 is very inconsistent at high framerates. At 7:04, I have to slow down the game for TLM because otherwise the cutscene would not play at the end (though it wasn't usually as laggy as this time). At 8:08, playing at 24 FPS delays the map loads, allowing me to warp to Tarazed. Otherwise, I would warp to Cujam instead.
- Ending: The PC version doesn't have the 30 second delay on the black screen before "The story continues to Baten Kaitos" (at least not at high framerates). In the Switch version, I would have had to use a glitch to save those 30 seconds.
Window Mode: Full Screen
Resolution: 2560 x 1440
Vertical Sync: ON
Anti-aliasing: High
Gamma Correction: 0
It seems that when Vertical Sync is turned off, the game runs at ~120 FPS regardless of the display refresh rate set in Windows. For comparison, I did a test run with Vertical Sync off, and it clocked in at around 18 minutes and 24 seconds.
Auxiliary tools: AutoHideMouseCursor, JoyToKey, NirCmd
For gameplay, I'm using a Switch Pro controller. I turned off "Use Nintendo Button Layout" in my Steam settings and increased the right stick deadzone to the maximum.
For framerate switching, I use two buttons on an Xbox 360 controller. These buttons are assigned a "Special" function in JoyToKey that launches nircmd.exe with the parameters "setdisplay 2560 1440 32 24" or "setdisplay 2560 1440 32 165".
If you want to learn more about glitches used in this run, check out these links:
docs.google.com/document/d/1R58dc43Z1AU-zFzkWlojPFhlGPQRLaRbAFN4pq_d2cU/edit?pli=1
youtube.com/watch?v=l0s_LDiGYK4
youtube.com/watch?v=-dZ2fferK0M (video description)
youtube.com/watch?v=IFVSs1ANe1U (video description)
