I noticed on several of the default aircraft a weird problem: Some minutes into the flight, gauges may "freeze" in the VC. They will simply stay in one position and won't refresh anymore. Anybody seen something like that or know how to solve it? This is a completely fresh install, with some tweaking per an enormous handbook/post I found somewhere on this forum (I must say that after that, FSX runs, with the default stuff, anyway surprisingly well!)

Oh come on, nobody here for a solution? It's an issue that annoys the hell out of and I'd like it to be solved...

The only such problem i know of is the pitot that freezes up so your IAS always reads zero.This i resolve by switching on pitot heat, and after a short while it starts working again.Or you can also reset or reload the plain, not the flight.If the gauges work when you reload the plane then it gives you more clues to work on.

Never mind...

the same is happening to me.I think it might relate to the video driver, I am using NVIDIA 186 series notebook driversI have reverted to an old NVIDIA driver 179 series notebook drivers and the problem has not recurred.

I'm using the 185.85 notebook driver. I hope there is no problem because of that, that'd be really crappy. I'll see what happens when resetting the flight or turning on stuff like pitot heat. When I flew I was just tetsing out performance, although in the boeing 747 I had problems with the flap gauge, which showed it was on 30 degrees, which i was most certainly not.

I'm using the 185.85 notebook driver. I hope there is no problem because of that, that'd be really crappy.

What's the big problem with that? Just uninstall the 185 drivers. Use a driver cleaner, such as DriverSweeper, to remove any reamining driver files. Then download and install an older driver.

What's the big problem with that? Just uninstall the 185 drivers. Use a driver cleaner, such as DriverSweeper, to remove any reamining driver files. Then download and install an older driver.

I also have apps like nHancer that will therefore require older versions and I'd hate to start reinstalling all of them...

I also have apps like nHancer that will therefore require older versions and I'd hate to start reinstalling all of them...

Are you sure? I have a new nHancer version and I have the nVIDIA driver 182.50 installed. No problems.

Are you sure? I have a new nHancer version and I have the nVIDIA driver 182.50 installed. No problems.

you are right it is not the drivers it was caused by the following line in the cfg [bUFFERPOOLS]PoolSize=300000000I have removed the line and all is fine

you are right it is not the drivers it was caused by the following line in the cfg [bUFFERPOOLS]PoolSize=300000000I have removed the line and all is fine

I was getting ready to recommend renaming the FSX.cfg and that would have fixed it too. I doubt this is a video driver issue but an issue with the FSX.cfg, a addon, or the dll.xml. I've done numerous searches on this problem and haven't seen it discussed before so it's a rare issue. Glad you were able to find the cause and fix it!Best regards,Jim Young

I can't find the line in the fsx.cfg, it doesn't seem to be there at all. I can't even find the [bUFFERPOOLS] entry... Where is it supposed to be? I'm looking in the FSX.cfg, but it's not there.Note that I noticed this problem at just about the first flight I did with FSX (which was the day before yesterday), which is a completely clean install of FSX Gold Edition.

I can't find the line in the fsx.cfg, it doesn't seem to be there at all. I can't even find the [bUFFERPOOLS] entry... Where is it supposed to be? I'm looking in the FSX.cfg, but it's not there.Note that I noticed this problem at just about the first flight I did with FSX (which was the day before yesterday), which is a completely clean install of FSX Gold Edition.

A standard install does not have this entry.. it is a "tweak" which is best not attempted..

Ah, too bad... so it's not really a solution for my problem. As of late I haven't seen the problem (instead I got a OOM, which I hope is fixed as of now), but I didn't fly with the default aircraft. I'll be flying soon again (with TrackIR 5!) and see what happens.

Right, I haven't seen this issue now for at least two or three flights. I don't know what happened, but all seems okay now...