Graphics configuration suggestions?

[Over50]

I'm flying out of Toul (Spad VIII) and I've experienced the same graphics miscue three times in my campaign mission attempts (I'm getting killed regularly but that's another topic...) and I'm open for suggestions as to what settings change(s) might have an effect.

All three times (once just patroling the front line and twice a balloon busting mission) I've noticed a thin straight white line appear in the near-distant ground scenery to begin with and then gradually worsen to unrendered squares of white. Exiting at that point the game hangs at the mission quit prompt for a period of time.

My sliders are conservatively set to (3) for terrain, scenery and clouds with effects and aircraft at (5). I'm running the latest Nvidia 181.22 driver as well. Of note I've had V-sync forced off in the Nvidia 3D control panel - but what I'm seeing is not tearing, rather, a rendering issue. Also of note I have yet to run across this in QC free flight or combat, but then the flights have mostly been near the base.

I reset my vsnyc to application preference last night after it happened(which caps my fps at 60 dang it..) and will try flying missions this evening from a different location than Toul to see if it shows up again. Again, this has only happened three times and not in succession.

 

[Giant2111]

Appearently, you are out of the modelled terrain? I had the same issue on the coastline,..then thin white line, and green after that. Checked the map, I noticed I had to be somewhere over the channel, northeast of Calais, which was also not modelled, just a white triangle there.

lets see, if I can get some pics from there

 

[Over50]

Appearently, you are out of the modelled terrain? I had the same issue on the coastline,..then thin white line, and green after that. Checked the map, I noticed I had to be somewhere over the channel, northeast of Calais, which was also not modelled, just a white triangle there.

lets see, if I can get some pics from there

I don't think so as it has occurred easily within the mission boundaries either approaching the target or looking behind in snap view. I've not seen this issue mentioned anywhere here which leads me to believe it's possibly a hardware or other type of glitch on my end. Again, I've reset vsync to application preference and will try a different squadron locale to see if it occurs again.

 

[ftgc]

I'm flying out of Toul (Spad VIII) and I've experienced the same graphics miscue three times in my campaign mission attempts (I'm getting killed regularly but that's another topic...) and I'm open for suggestions as to what settings change(s) might have an effect.

All three times (once just patroling the front line and twice a balloon busting mission) I've noticed a thin straight white line appear in the near-distant ground scenery to begin with and then gradually worsen to unrendered squares of white. Exiting at that point the game hangs at the mission quit prompt for a period of time.

My sliders are conservatively set to (3) for terrain, scenery and clouds with effects and aircraft at (5). I'm running the latest Nvidia 181.22 driver as well. Of note I've had V-sync forced off in the Nvidia 3D control panel - but what I'm seeing is not tearing, rather, a rendering issue. Also of note I have yet to run across this in QC free flight or combat, but then the flights have mostly been near the base.

I reset my vsnyc to application preference last night after it happened(which caps my fps at 60 dang it..) and will try flying missions this evening from a different location than Toul to see if it shows up again. Again, this has only happened three times and not in succession.

Over50,

First set your slider for clouds to 1. The clouds are real frame rate hogs and to be honest I can't tell the difference in them between 1 and 5. Second try setting your vsync to forced on (as opposed to app controlled) I had a similar problem when I had vsync set to off and boosted my sliders to much for my video card. I think it happens when your card try to render more scenery textures then it has memory for.

Scott

 

[Over50]

Over50,

First set your slider for clouds to 1. The clouds are real frame rate hogs and to be honest I can't tell the difference in them between 1 and 5. Second try setting your vsync to forced on (as opposed to app controlled) I had a similar problem when I had vsync set to off and boosted my sliders to much for my video card. I think it happens when your card try to render more scenery textures then it has memory for.

Scott

While I don't know what may be causing the rendering problem, I really don't think 898 MB of video RAM with a GTX 260-216 card is a factor. I've been playing continuous for the past hour and a half and haven't had it show up and the only thing I've changed is (1) squadron location (flying the Sopwith now), (2) vsync set to application preference, (3) and disabled high resolution z buffering to see what happens. My sliders are still set to 5,3,3,5,3 and my frame rate is pretty much locked at 60 even in a dogfight.

I'll try forcing vsync ON as you suggested and continue to run the game with the sliders as noted and z buffering disabled and see if the problem shows up again. Just to mention, with vsync forced off my frame rate will hit 180 at higher elevations (above 4000 ft., etc.). Sure hate to give that up ....