Stop start problems with FS9

[JohnWillimas]

I've just upgraded my monitor and installed an HP2159m which has a1920 x 1080 native resolution.

Previously FS9 was giving me up to around 30+fps (15 - 20 in heavy scenery) and performed nicely but now I get a slightly lower performance at system start and then after a few minutes running the thing grinds down to 1 to 2 fps. Leave it a bit and suddenly the performance seems to come back for a while but then its clunk clunk clunk again.

I've tried updating and back tracking on video drivers (I'm currently running Nvidia's 182.50 drivers) but with no real difference.

I'm running on a box with 2.40 gigahertz Intel Core2 Quad, Nvidia 8800 GTS/ 640M and 2G memory.

I'd welcome any advice or am I being optimistic trying to run this monitor on this card?

[TSR2]

Hi John,

Try this... With FS closed, find your FS9.cfg file and rename it to FS9.cfg.old

Ensure you have a reasonably current driver from Nvidia

start FS and adjust you screen setting using the sliders, then try again

[JohnWillimas]

Good thought Ben, but regrettably.... same problem.

Racked the resolution back to 800x600x16 too and I still have the same problem. I'll try some other settings though.

Cheers.

John

[TSR2]

Have you got FS running at the same native resolution of your new monitor?

[tonymadge]

I had a 8600GTS card and had a new monitor with a similar res it slowed FS and everyhting else down due to the card running at pretty much its max res, I then changed the monitor to a Samsung T220 and the slightly lower res of 1650x? made life a bit better but not as good as the old monitor on 1280x1024 or similar... Anyway that res your using is making the card work bloody hard... I bought a GTX260 and life is sweet as it copes with the high res very well...

[JimCooper]

I doubt its the 8800GTS, it has a bandwidth of 64GB/sec and a fill-rate of 24 billion px/sec
The 8600GTS only has a bandwidth of 32GB/sec and a fill rate of 10.8 billion px/sec

So on fill rate the 8800GTS is over 2 times better than the 8600GTS. And you're only filling 2.1 Million pixels

It's more likely to be along the lines of mis-match between Windows Res and FS9 Res as suggested by Ben.

A couple of years ago I was running FS9 on a 2.4GHz Dual Core connected to a TH2Go running 3x1024x768 on one output and the other output to a 24" running 1920x1200 (About 4.5 million pixels in total). This was through a 7900GTX (512M) (Bandwidth 51.2 and fill-rate 15.6). Frames were 15-30 fps.

Regards

Jim

[tonymadge]

I stand corrected I did not realise the 8800 would be that much better. Ok I agree it could be the res, I always run FS the same res as desktop.
Hope you get it sorted

[JohnWillimas]

Ben / Tony

Thanks for the replies. I have been running at the same resolution as the desktop, so its not that.

I'm trying some other stuff suggested over at the Nvidia forums -if that works I'll post an update here.

[JohnWillimas]

Hmmm, still no progress.

Tried replacing my new monitor with the old one (1280x1024) and found I had the same problem with that, so its obviously something else.

Backtracked to some 160 series NVIDIA drivers and still no joy.

I've decided its not an FS problem either as I fired up RailWorks yesterday and had the same experience. So, it seems like something more core to the PC.

Graphics card doesn't appear to be running hot and I've tried reseating it, so its not that. Memory shows at only around 55% used (of 2G) so it doesn't sound like a memory problem....

Curiouser & curiouser as the Cheshire PC mechanic might have said....

[Garry Russell]

HI John

I did have a similar problem when I ran very low on HD space as everything slowed up and then cleared when the cache empted.

Defragging helped after off loading a load of stuff. I was down to les than 2 GB though at that time.

Sounds crazy but perhaps running defrag, disk clesup and a registry cleaner might help, basic as it sounds.

Crap cleaner used on tools finds a lot of dead links and unused stuff clogging up my system from time to time.

Does sound to me like running out of memory then emptying and improving things until it fills again.

I'm not a technical person but have experienced this sort of thing.

Garry