Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
Not to be confused with FPS of course. SR2 can be running at a smooth 60 FPS but still be battering the CPU and not running well. It's basically a different kind of "chop".
When you said after a load, I assumed that you meant it was getting worse as game time went on - which is typical of what I was talking about.
If the game is running 60 tps pre-save, then 5 tps post load then there something going terribly wrong somewhere. Either it's a problem with the save or the game.
Does it smooth out if you leave it paused for a few minutes? It could simply be the game still loading assets in the background (a feature of the game engine, not a bug). Loading a large game, particularly with a lot of mod content can take a little time to load and start to run smoothly. If not, then I'd say you're back to something having gone terribly wrong.
For what it's worth, what you're describing is not my experience with saved/loaded games. Aside from the typical loading time/delay, they generally run about as well as when I saved them.
One of the main points I wanted to make was that when you mention projectiles jumping around and doing wierd things, that is definitely a TPS issue. So CPU not graphics. You'd get a stuttery flight if it was GPU, but it wouldn't overshoot then fly back and that sort of thing if it was just GPU. The overshoot means that the CPU hasn't had time to recheck the progress of the projetile fast enough - which results in them going past and then rubberbanding back.