I was trying to fix the annoying texture flicker where a taxiway joins onto a runway, as if two texture maps are in comflict.

Here is an example of the problem at EGJJ Jersey.

 

I tried turning the DirectX 10 preview mode off in FSX and this stopped the flicker problem straight away. However by doing this it has introduced a problem with the PMDG NGX and as you see the displays do not show up?

 

It would be good if I could keep the Preview off and also keep the PMDG displays working. Any ideas on this? Or is there a better way of fixing the texture overlape and flicker, without doing anything with DX10 or 11.

 

I have windows 7 which uses DirectX 11.

 

I have a Nivida GeForce GTX 480

And I7 processor

 

 

Many thanks

 

Julian

Sounds like everyone has this problem reading lots of threads on the internet.

 

Is there a patch for this, or any updated airport files on AVSIM?

I use the NGX,without DX10 preview and don't get that issue.i would stick to that.

with dx10 preview the downsides are too many.

does look nice though if only it was fixed

steve-0

unfortunatly, this is a common proplema

 

I think no solution so far was discovered,

 

Thanks for highlighting this issue, I hope if anyone here know some solution to help, DX10 is way better than DX9 in terms of FPS.

I use the NGX,without DX10 preview and don't get that issue.i would stick to that.

with dx10 preview the downsides are too many.

does look nice though if only it was fixed

steve-0

 

 

It is funny how preview off works for you steve?

 

Generally i turn the water textures down, I always feel that the water looks too reflective and unrealistic anyway. I tend to fly in English air space were water is grey and muddy anyway.

 

I wish i knew why the panels are not working with preview off.

 

unfortunatly, this is a common proplema

 

I think no solution so far was discovered,

 

Thanks for highlighting this issue, I hope if anyone here know some solution to help, DX10 is way better than DX9 in terms of FPS.

 

I always assumed it was my pc being goofy. But it is a problem with dx10 11 genarlly.

There is a solution. Add a texture with concrete to the runway fixes it - http://www.fsdeveloper.com/forum/showthread.php?t=17921.

 

Best regards,

Jim

There is a solution. Add a texture with concrete to the runway fixes it - http://www.fsdevelop...ead.php?t=17921.

 

Best regards,

Jim

 

There must be a different way microsoft intended to use to fix this matter,

 

I found many enteries in the g2d.dll

D3DX10ReflectShader D3DX10ReflectShader D3DX10CreateEffectPoolFromMemory D3DX10CreateEffectPoolFromMemory D3DX10CompileFromMemory D3DX10CompileFromMemory D3DX10CompileFromFileA

D3d10compileshader

There must be a different way microsoft intended to use to fix this matter,

 

DX10 Preview is a preview and the first attempt by Microsoft to offer FSX with DX10. It was pretty much a total failure as DX10 did not live up to the pictures Microsoft had posted as what DX10 would look like in FSX. FSX was released around the same time as DX10 compatible cards were released. I was one of many who bought a DX10 compatible card in preparation for the release of FSX/DX10. As far as I know there was no further attempt by the Microsoft Aces Team to make FSX fully DX10 compatible. In fact, the Team Leader for the Aces Team, Phil Taylor, thought the problem was a Nvidia driver issue. I and several others sent problem reports to Nvidia trying to get them to fix this issue in FSX. Later, the Aces Team was abolished and any further work on FSX was stopped. It was one of the flight simmers here that finally provided the fix using concrete textures. Google it.

 

Best regards,

Jim

DX10 Preview is a preview and the first attempt by Microsoft to offer FSX with DX10. It was pretty much a total failure as DX10 did not live up to the pictures Microsoft had posted as what DX10 would look like in FSX. FSX was released around the same time as DX10 compatible cards were released. I was one of many who bought a DX10 compatible card in preparation for the release of FSX/DX10. As far as I know there was no further attempt by the Microsoft Aces Team to make FSX fully DX10 compatible. In fact, the Team Leader for the Aces Team, Phil Taylor, thought the problem was a Nvidia driver issue. I and several others sent problem reports to Nvidia trying to get them to fix this issue in FSX. Later, the Aces Team was abolished and any further work on FSX was stopped. It was one of the flight simmers here that finally provided the fix using concrete textures. Google it.

 

Best regards,

Jim

 

Many thanks Jim for the clarifications, I am convinced

 

Kind regards,

 

Michael

I was a die hard DX10 user until I learned about running Nvidia inspector with the 1/2 refresh rate adaptive Vsync option in DX9.

I get as many FPS as I did with DX10 without all the DX10 downgrades, such as AA and the flickering issues.

I was a die hard DX10 user until I learned about running Nvidia inspector with the 1/2 refresh rate adaptive Vsync option in DX9.

I get as many FPS as I did with DX10 without all the DX10 downgrades, such as AA and the flickering issues.

 

Oooo, that is interesting as you have a very similar system to me, and Word Not Allowed's 1/2 refresh rate Vsync worked for me. Maybe I will have a go with DX9 and see what happens - whenever I've switched back before I've ended up back in DX10 as it gives me 5/10fps in places.

New member stevejp has come up with a fix for this that you all may be interested in: http://forum.avsim.net/topic/376140-dx10-flashing-runways-experimental-shader/

New member stevejp has come up with a fix for this that you all may be interested in: http://forum.avsim.n...imental-shader/

 

Is it a risk, if I can keep safe the original files? I would certainly look at this at the weekend if you think it might help?

 

Thanks for all your advice.

New member stevejp has come up with a fix for this that you all may be interested in: http://forum.avsim.n...imental-shader/

 

Many thanks this has worked, at Jersey EGJJ. I will test it out a bit more at other airports before I assert it is fixed.

 

I am amazed a few lines of code has possibally fixed it.

 

 

Many thanks for find the link. It seemed a bit of a shame down grading DX11 to 9

 

Julian

Glad it worked for you. My first attempt at a fix was about 1500 lines of c++ so it amazes me too that such a tiny change to the shader can do it.

 

Steve