I tried using nHancer and got really nice results until the GPU went nuts and I could only see half the scene. That was supersampling 2x2.Probably some re-purposed driver function caused the glitch. Are their safe settings?jja

I tried using nHancer and got really nice results until the GPU went nuts and I could only see half the scene. That was supersampling 2x2.Probably some re-purposed driver function caused the glitch. Are their safe settings?jja

Ryan, from PMDG wrote a very informative post in the Video Cards section, explaining how now is not necessary to use nHancer in FSX to enable AA when using the NEW nvidia drivers. A good experiment, would be to download the latest drivers, and control settings via the nV Panel (application controlled) and see if it makes any difference.

Ryan, from PMDG wrote a very informative post in the Video Cards section, explaining how now is not necessary to use nHancer in FSX to enable AA when using the NEW nvidia drivers. A good experiment, would be to download the latest drivers, and control settings via the nV Panel (application controlled) and see if it makes any difference.

Well that is where I'm at now and still have the dancing white lines on top of my gauges. nHancer did away with them. I agree that we should have all functinality exposed at the driver level.jja

Well that is where I'm at now and still have the dancing white lines on top of my gauges. nHancer did away with them. I agree that we should have all functinality exposed at the driver level.jja

By any chance is your mesh resolution set to 1m? I discovered (by accident) that ANY mesh resolution under 10m (5m, 2m and 1m) will SPIKE the GPU of my GTX 480 when flying around Manhattan (which is completely FLAT) I noticed this first on my laptop (which is VERY SLOW) and started making cralcking sounds and popping, then checked in the desktop using GPU-Z and I confirmed it... so it seems there is some kind of scheduling terrain problem when mesh is set lower than 10m. It would be a nice thing to check and have someone confirm this.EDIT: I checked GPU usage with *EVERY* mesh resolution option, from the lowerst, to the highest.. they ALL produce the EXACT same GPU load, except the ones lower than 10m strange isn't it? one more thing is that I DO NOT have any mesh scenery under 10m resolution, so it could ALSO be a problem in FSX when you set your mesh resolution to a value lower of what you have installed.

By any chance is your mesh resolution set to 1m? I discovered (by accident) that ANY mesh resolution under 10m (5m, 2m and 1m) will SPIKE the GPU of my GTX 480 when flying around Manhattan (which is completely FLAT) I noticed this first on my laptop (which is VERY SLOW) and started making cralcking sounds and popping, then checked in the desktop using GPU-Z and I confirmed it... so it seems there is some kind of scheduling terrain problem when mesh is set lower than 10m. It would be a nice thing to check and have someone confirm this.EDIT: I checked GPU usage with *EVERY* mesh resolution option, from the lowerst, to the highest.. they ALL produce the EXACT same GPU load, except the ones lower than 10m strange isn't it? one more thing is that I DO NOT have any mesh scenery under 10m resolution, so it could ALSO be a problem in FSX when you set your mesh resolution to a value lower of what you have installed.

I can confirm this too. I noticed that any mesh setting lower than 10m would add an occasional stutter when turning using BP=0 (which i guess from your statement is the GPU spiking). I do have 5m meshes installed for some parts of the world so I do think it is something inherrent in the FSX code.