I don't see how the NGX could actually be the cause of that - we have no control or manipulation at all of the FSX graphics engine, view switching etc. It looks like there's frames rendering and being displayed very quickly there before it switches views. I do not see this on my GTX570.

I don't see how the NGX could actually be the cause of that - we have no control or manipulation at all of the FSX graphics engine, view switching etc. It looks like there's frames rendering and being displayed very quickly there before it switches views. I do not see this on my GTX570.

 

Hi Ryan, thanks for the reply. Sure, I agree, I too can't see how the NGX can cause that. However, don't get me wrong, I am not suggesting the NGX causes the issue, only that it only appears with the NGX. That just happens to be a fact, on my particular system. It may be that because of the extra workload that the CPU has to drive in the VC, compared with less intense aircraft, is a contributing factor. It may be the way the polygons are drawn (this is me trying to sound knowledgeable) or some other factor that goes unnoticed at other times. What makes it more irritating is when others, like yourself, have no exerience of the issue, but yet there seems to be a small number who do in fact suffer. I have tried without Ezdok, without TRir, I have tried numerous changes to the cfg tweaks, different inspector settings and different gpu driver. However, as I said originally, reverting back to ForceFullScreenVSync=1 in the cfg has eradicated the problem, but in doing so I don't get the benefit of the extra smoothness by being able to use the Vsync tweak in Inspector. So Ryan, if you could offer any suggestions I'd be interested in trying them.

I have this also, I'm sure it happend after changing to the 300 drivers. Will try the last 200 (295.73) I used tomorrow.

 

i700 4.8, GTX 670, Win 7, with all Word Not Allowed's tweeks

Question from a non expert: I did not think that you used Bufferpools=0 with a RejectThreshold figure in your .cfg

 

True or False?

Question from a non expert: I did not think that you used Bufferpools=0 with a RejectThreshold figure in your .cfg

 

True or False?

 

Correct Rick, as far as I understand things, BufferPools=0 effectively switches the buffer off and allows all data through to the GPU. Adding a RejectThreshold, determines the amount of data that is sent to the GPU which in turn is dependent on the rejectThreshold value. So if you have BufferPools=0 in the cfg, then it is pointless having anything else in there as it will be overrun.

Thanks Howard for simplifying things for me.

Hi, Howard.

 

To me this looks like keyboard shortcut-conflicts. To be more precise; your EZDok "next-view" is in conflict with another internal FSX shortcut. I had the same flicker as seen in your video. Making sure I did not have multiple assignments to keyboard shortcuts resolved the issue in my case. I see from your cfg you do run EZDok.

 

Good luck!

 

PS, and sorry - I see someone has already mentioned ezdok.

 

 

 

 

 

 

A couple of months ago I posted about an issue I was having with the NGX and how, when changing views the view would, in a fraction of a second, flash or jump. It is a very odd issue which only showed itself with the NGX. I almost found a workaround by not using the 1/2 Vsync in inspector. I say almost, because the issue was still apparent but not as bad as when running with 1/2 Vsync. So I would fly all my other aircraft using 1/2 Vsync and then change to just standard Vsync in Inspector when flying the NGX. BUT, the issue was still very irritating and I could not find a way to solve it until yesterday. I came to the conclusion that the problem was somehow associated with Vsync (unsurprisingly) and so yesterday I decided to add the fullscreen Vsync value to the cfg. and set it to none in Inspector. VOILA! Yep, the jumping views had gone, no more, disappeared... except... I was experiencing some tearing. So now I don't know whether the Vsync in the cfg works and it has had the desired affect or it doesn't work, hence the tearing, and the jumping views have disappeared because there is no Vsync, a dilemma, and one I'd be interested in hearing about. Here's a vid of the original problem, best viewed at 720

 

http://youtu.be/OU3VkgvAUns

Hi, Howard.

 

To me this looks like keyboard shortcut-conflicts. To be more precise; your EZDok "next-view" is in conflict with another internal FSX shortcut. I had the same flicker as seen in your video. Making sure I did not have multiple assignments to keyboard shortcuts resolved the issue in my case. I see from your cfg you do run EZDok.

 

Good luck!

 

PS, and sorry - I see someone has already mentioned ezdok.

 

Hi Bernt, sure, that was my first thought too, but after spending ages trying to fathom any conflict, i couldn't find any. But sure, you're right, at first glance it does look like that. Maybe, I'll check it out again, who knows, maybe I missed something.

Hi Howard,

This won't win me the brightest idea award, but try setting your pre-render in Nvdia inspector to "1".

With the pre- render set @1 you should be able to use 1/2 vysnc without the nonsense that comes with it.

 

Edit: BTW, Pre-Render @1 stops texture spiking when using BufferPools=0. It gives the most smooth experience.

Hi Howard,

This won't win me the brightest idea award, but try setting your pre-render in Nvdia inspector to "1".

With the pre- render set @1 you should be able to use 1/2 vysnc without the nonsense that comes with it.

 

Edit: BTW, Pre-Render @1 stops texture spiking when using BufferPools=0. It gives the most smooth experience.

 

Now that is interesting... thanks Julian, I'll try that...

I also get this flashing when changing views with EzDok.

 

I will try the suggestions mentioned and report back.

Julian, I've tried the different settings on pre rendered frames, but with no success I'm afraid...

I checked my GPU's & and the two drivers. With the 480 card & 200 seris drivers no flashing, With 300 seris drivers & 480 or 670 GPU's I get flashing on all aircraft panel view changes. There is no flashing with outside view changes. I don't have EzDoc. It looks like the new GPU's & drivers with vsync cause this.

I checked my GPU's & and the two drivers. With the 480 card & 200 seris drivers no flashing, With 300 seris drivers & 480 or 670 GPU's I get flashing on all aircraft panel view changes. There is no flashing with outside view changes. I don't have EzDoc. It looks like the new GPU's & drivers with vsync cause this.

 

Hey nice find Paul. I'll install one of my old 2xx drivers. The only thing will be the likely loss of being able to run 1/2 Vsync in Inspector. I'll do some testing, cheers...

I also have this issue (I'll say right now that I haven't found a fix, to save you getting your hopes up ) and these are my findings:

 

Only exists with the 737NGX

Only exists with FSX in fullscreen mode

Exists whether using EZCA or not

Exists to a much greater extent when using "1/2 refresh rate" Vsync mode in Nvidia Inspector, though turning this off and not using any other Vsync modes or Vsync lines in FSX.cfg does NOT entirely solve the problem i.e. I still get flickering with no Vsync, but it's not as bad

When using the 1/2 refresh rate Vsync mode with the windowed fix from here I don't notice the problem at all

 

I am currently using the latest WHQL drivers (306.97) with a 1GB GTX 460, which is overclocked and overvolted significantly. Reverting to stock, however, has no effect on the flickering. My CPU (Core i5-2500K) is also overclocked but I highly doubt it is the cause and it should be very stable.

 

Note that I have recently performed a clean install of Windows 7 (64-bit), FSX + Acceleration, and the only add-on I currently have installed is the NGX. I've tweaked my FSX.cfg file according to the previously linked guide.