Max/spice2x_spice2x.github.io
1
0
Fork 0
mirror of https://github.com/spice2x/spice2x.github.io.git synced 2026-09-30 02:38:11 +03:00
Code Issues Packages Projects Releases Wiki Activity

Updated PC optimization (markdown)

bicarus
2026-02-17 16:15:45 -08:00
parent 6b749a8412
commit acc6a3bdf5
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PC-optimization.md
+1 -1
@@ -19,7 +19,7 @@
* Press F12 to see the FPS counter, confirm that it's what you expect. Also check your monitor (if not, check `log.txt`) to see that the game launched at the correct refresh rate. You want those numbers to match (60FPS and 60Hz, 120FPS and 120Hz).
* Avoid using patches that run at refresh rates not originally intended by the game engine, as it may result in graphical glitches or overlapping sound effects.
* In menus, your framerate will swing wildly, and this is perfectly normal, as the games aren't perfectly optimized for menus. Check for FPS only during gameplay.
* Do not, under any circumstances, use "skip monitor check" or "shorten monitor check" patches. You might be asking, "why does the hex edit exist if you're not supposed to use it?" - the answer it that those were added for tools and EA server developers to boot the games quicker. If you're actually playing the game, you should keep monitor check.
* Do not, under any circumstances, use "skip monitor check" patches. You might be asking, "why does the hex edit exist if you're not supposed to use it?" - the answer it that those were added for tools and EA server developers to boot the games quicker. If you're actually playing the game, you should keep monitor check.
* It's OK if monitor checks aren't exactly 60.000Hz or 120.000Hz - because they're not like that at the arcade either. For example, IIDX LM cabs stabilize around 119.98xx.
* Your monitor may boot into 59.94Hz or 119.2Hz (for example). This is OK for most games, as monitor check will eventually stabilize to match your refresh rate.