Log in

View Full Version : Any else have this problem


gdogghenrikson
10-01-05, 05:02 PM
I defraged me hard drive this morning(I always do on the first month) now when I run sh3 my Frame rate is bad at 512 time comp. like 5-10 fps used to me like 60-70 fps

Gizzmoe
10-01-05, 10:20 PM
I don“t think that it has anything to do with the defrag. Is the framerate always 5-10 fps, no matter where you are on the map?

Kalach
10-02-05, 03:35 AM
I've given up defragmenting ever.
Every time I do everything runs noticeably slower :-?

Average Joe
10-02-05, 04:29 PM
gdogghenrikson, I recently had the very same problem, time-accel was no greater than 5fps at 512x, no matter what. Anything higher and time-accel dropped to 1fps! Clear-sailing usually shows about 18-20fps even at 2048x accel.

No torpedoes left, sailing 3300Km back to home-base at 5fps is torture!:x :88 I had to turn it down to 256x.

The TC slow-down seemed to occur after just a few enemy contacts. I saved the patrol, quit, re-boot, reload the save, it was still stuck at 5fps at 512x. I thought my video-card or CPU was going bad.

I'm into a fairly new campaign, but can't remember if it happened with this one, or during the last (late-war) campaign. No mods were added the whole time period.

Very strange because I've done so many patrols and never saw it 'bog-down' -that- slowly, even when very close to returning to base, were frame-rate is typically higher.

The only thing I tried was turning down particles from 85% to 55%, an disabled (Nvidia) anti-aliasing, but I can't remember if that helped or not... I doubt these settings have anything to do with TC on the patrol-map. This weird slowdown never occurred even when particles were set to 100% and FSAA always enabled.

Anyway the slow time-accel FPS totally 'vanished' after 2 patrols, and things are back to normal again. No slowdown problem after 6/8 patrols.

I defrag quite often, but will do so again before loading my current patrol. If it slows-down again I'll report back. I doubt it will, and really hope it was just a fluke.