Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Nope. Load accelerator runs fine with vsync.
You want to limit your FPS but not to 20 in the Sanctuary and Boston Commons.
Use the FPS limiter to set to 150fps, won't have the 3x speech you get at 300fps, will do great on fps in the low areas.
The root cause of the problem is using the monitor frequency to determine the speed at which the engine runs. It's the tail wagging the dog. The monitor is unaware of the cpu and its capability and what is happening with the engine.
Also you need to take into account your own hardware configuration. How good is your cpu? What fps are you actually getting? Do script monitoring mods say that scripts are lagging?
Note that there is a hard limit on the time that scripts have to complete within each frame. The default is 1.2 milliseconds. 300 fps = a frametime of 3.3 milliseconds. Given that the scripts also have to sync with the other components of the engine within that 3.3 milliseconds, and compete for cpu with them too, you can figure out what will happen. If there is a problem at 120? fps do you think increasing the fps is going to fix it?
Plus more cpu = more heat.