Windows 8: the DX10 cure ?

 

http://forum.avsim.net/topic/395291-dx10-no-more-flickeringshimmering-runways-in-windows-8/

When I installed my windows 8, I tried DX10, I did get all the flickering that I used to with windows 7, so its too good to be true.

Steve Parsons new shaders for DX10 have been a boon for me on an elderly rig with Vista 32 bit. The sim is smooth, locked at 30 fps with the Avsim forums Nvidia Inspector settings.

It's nothing more than a placebo. Windows 8 will not fix the miscomings of FSX however, Steve's fixs come pretty darn close.

 

Bob

I installed Steve's DX10 fixes (including the latest v3.2.2) and I have ONLY ran with DX10 (Windows 7 - 64 bit) and have loved it!! Still an occasional odd graphic appears BUT nothing major and the performance has been excellent. Steve has done a wonderful service for all of us hoping to use DX10. :lol:

When I installed my windows 8, I tried DX10, I did get all the flickering that I used to with windows 7, so its too good to be true.

From what you say, I would suspect that you have other issues with the fsx.cfg, Mehmet, or some other graphical anomaly which caused, or is causing your flashing.

 

DX10 doesn't cause "flashing", and neither does DX9, but the wrong BufferPools setting will certainly cause flashing, as will not having HighMemFix=1 in your [Graphics] section, or simply having to many settings which are too high.

 

Start another thread and tell us exactly your problem, posting your fsx.cfg (as fsx.txt) here, and adding your system's specs to your profile - OK? :wink:

 

All the Best,

 

pj

From what you say, I would suspect that you have other issues with the fsx.cfg, Mehmet, or some other graphical anomaly which caused, or is causing your flashing.

 

DX10 doesn't cause "flashing", and neither does DX9, but the wrong BufferPools setting will certainly cause flashing, as will not having HighMemFix=1 in your [Graphics] section, or simply having to many settings which are too high.

 

Start another thread and tell us exactly your problem, posting your fsx.cfg (as fsx.txt) here, and adding your system's specs to your profile - OK? :wink:

 

All the Best,

 

pj

 

I have actually created another thread, I am having an entirely different issue, artifacts, when I use the DX10 mode with Steve's fix. Here is the link:

 

http://forum.avsim.net/topic/395492-problems-with-dx10-mode/

 

I will post my fsx.cfg in that thread.

 

That being said, what I meant by my comment was the fact that Windows 8 alone does not fix the runway or other texture issues that happens once DX10 preview mode is enabled (without Steve's fix).

Windows 8 won't fix the DX 10 shaders in FSX, you still need Steve's DX10 Fix to avoid the flickering runways and dodgy taxi direction arrows.

I have actually created another thread, I am having an entirely different issue, artifacts, when I use the DX10 mode with Steve's fix. Here is the link:

 

http://forum.avsim.n...with-dx10-mode/

 

I will post my fsx.cfg in that thread.

 

That being said, what I meant by my comment was the fact that Windows 8 alone does not fix the runway or other texture issues that happens once DX10 preview mode is enabled (without Steve's fix).

 

Of course. The OS has very little to do with the functionality provided by DirectX. DirectX v.10 being "enabled" within FSX is a matter of it switching to a different set of Shader files - which are really gpu-centric, and are a set of functions/rules which allow, or instruct the (compatible) gpu how and where to create better graphics.

 

Work on creating a set of files to interact with DirectX v10 was started by the ACES team , but they were never given the opportunity to finish the development, and so what you have are some shader files that work in some fashion, and other shader files that produce quite unpredictable results.

 

The initiative, enthusiasm and work output which Stevejp - on his own - has displayed in taking on the job of actually finishing that development, is an incredible achievement. There is no such thing as "never intended as a finished product" - they were simply left in that state by an uncaring project management, and probably directed by Marketing. It is one thing to 'better' a product with an improvement, or to fix a known issue - but it is quite another to knowingly allow a product to market, and label something like DX10 as a "Preview" with that "Preview " programming barely functional, and not representing a Preview of "what's coming with DX10".

 

Steve is repairing these files one by one. When he will be finished I cannot say, but my gut feeling is that the issue of incorrect shader function will very likely be done with early this next year.

 

Incompatible textures - i.e. those textures produced with tools and methods outside of the ground rules set down in the MS-released SDK, or the use of legacy textures from fs7 or fs8 - are a separate issue, and some possible fixes, like those available through AddonConverterX, are being considered at this time.

 

I hope this clears up some misconceptions about Steve's fix.

 

All the Best,

 

pj