A few people on steam and myself as well (as I've been unable to test until next weekend) were wondering about locking the fps through the sw.cfg file.
"Apparently" since the update that method no longer works to cap framerates? I haven't tried myself to check yet physically. Does it still work and it's simply a matter of editing the file in the My Documents folder instead now?
I did notice myself during my testing last weekend that my fps was running amok, but I've yet to go back and make absolutely sure it wasn't me turning it off to check bottlenecks.
[EL 1.0808] FPS lock option? *INFO*
-
matchbox2022
- Commander
- Posts: 609
- Joined: Fri Nov 13, 2015 3:21 pm
-
Vice
- Administrator
- Posts: 12227
- Joined: Fri Apr 25, 2003 1:38 am
Re: FPS lock?
Yes, it does still work, just tested it myself. To set the maximum framerate to a fixed value, locate the sw.cfg file in the game's save data folder (default location is now Documents\EvochronLegacy and also \Users\[username]\Documents\EvochronLegacy). Open the file in notepad and edit the third line below 'TextRes=2048' from '0' to the framerate you want to apply. Then save file and launch the game. As a redundant check, if the game has to fall back to the old \sw3dg\EvochronLegacy folder (ie unsupported folder string or older build), it would be a good idea to include that in any automated change system as well. But under most conditions, the \Users\[username]\Documents\EvochronLegacy folder is what is needed.
If it doesn't work, it usually means the file may have been saved with a redundant extension (that is, it was saved with a text file extension rather than its 'cfg' extension, so the file ended up being named 'sw.cfg.txt' or 'sw.txt' instead of 'sw.cfg'). Otherwise, the framerate will apply while you are in the game. Menus will run at an independent framerate for certain optimal mouse response and rendering timing operations, so the FPS cap will apply in-game. And although it may not have much of an effect, you can also optionally switch between VSync and NoVSync display modes to gauge framerate behavior with the setting applied for performance/consistency.
Since it's been quite a long time since I last recall when someone wanted to limit the framerate below a monitor refresh and there have been a lot of code changes in recent years, I just tried it myself to verify and it did work correctly for me.
If anyone needs direct support, they are welcome to contact me via starwraith.com > contact.
If it doesn't work, it usually means the file may have been saved with a redundant extension (that is, it was saved with a text file extension rather than its 'cfg' extension, so the file ended up being named 'sw.cfg.txt' or 'sw.txt' instead of 'sw.cfg'). Otherwise, the framerate will apply while you are in the game. Menus will run at an independent framerate for certain optimal mouse response and rendering timing operations, so the FPS cap will apply in-game. And although it may not have much of an effect, you can also optionally switch between VSync and NoVSync display modes to gauge framerate behavior with the setting applied for performance/consistency.
Since it's been quite a long time since I last recall when someone wanted to limit the framerate below a monitor refresh and there have been a lot of code changes in recent years, I just tried it myself to verify and it did work correctly for me.
If anyone needs direct support, they are welcome to contact me via starwraith.com > contact.