It was nice after I figured out how to install it LOL. Here are my likes:

• I liked how fluid FSX felt.
  
• I liked how changing from full screen to windowed mode was almost instantaneous.
  
• Felt like a whole new sim.
  

Here are my dislikes:

• AA & AF was an issue even with the NI settings, lots of jagged edges and shimmering.
  
• Water looked terrible.
  
• AI on VATSIM were without liveries and were stark white.
  
• Could not add an ENB tweak.
  
• DX10 Testing Pics and Settings is broken so I was on my own there.
  

So I have reverted back to DX9 for the time being, I think I did it right by copying the General10.fx.ORIG to General10.fx, (instructions are a little vague) and finally I deleted the Shaders10 folder but it was not rebuilt after restarting FSX. Could be due to the fact that I use Low 2x water.

 

If anyone wants to take a look I have attached my fsx.cfg.

 

 

Pump in some higher levels of SGSS and everything will look pretty again. :smile:

So I have reverted back to DX9 for the time being, I think I did it right by copying the General10.fx.ORIG to General10.fx, (instructions are a little vague) and finally I deleted the Shaders10 folder but it was not rebuilt after restarting FSX. Could be due to the fact that I use Low 2x water.

 

You did not have to revert back to the original General10 folder. That folder only applies to DX10 and won't affect DX9 whatsoever. When in DX9, that folder is not read by FSX whatsoever. Only in DX10 mode. It just means you'll have to reinstall the DX10 shader fix should you ever decide to go that route in the future. I would have left the DX10 Shader fix just in case I ever wanted to try it again as it really only fixed the runways that were stuttering/shimmering and the issue with not seeing the progressive taxi's. BTW, there is no special settings for DX10. Some here have modified their DX10 settings to make DX10 look better in their eyes but there is no reason you can't use DX9 display driver settings and fsx.cfg settings. All you need to do this is just enable DX10 Preview. Microsoft made DX10 a preview feature before firing the developers and DX10 should work great with DX9 settings too. I'm a little amazed that your ENB series program does not work. It should. There's nothing special with DX10. It is especially important that you enable AA and AF in the FSX settings or you will definitely get jagged edges. DX10 will not work without one or the other or both not enabled. I have to agree with you that DX10 is not compatible with aircraft made from previous versions of FS. The Addon Converter will fix that most of the time but not always.

 

Best regards,

Jim

Let me know if there is some fix/tweak for that DX10 stutters, or microstutters. i tried DX10, but reverted to DX9 and Word Not Allowed's guide very quickly becouse of that...

Let me know if there is some fix/tweak for that DX10 stutters, or microstutters. i tried DX10, but reverted to DX9 and Word Not Allowed's guide very quickly becouse of that...

 

This is what the DX10 Shader fix fixes.

 

Best regards,

Jim

This is what the DX10 Shader fix fixes.

 

Best regards,

Jim

 

Thanks Jim. I folowed Paul's guide to DX10, replaced shaders etc... And i have stutters, didn't find any solution for this. I found that is something common for DX10: http://forum.avsim.net/topic/389904-stutters-with-dx10/

 

One solution is to move some sliders to the left, but i can do this in DX9 too, i can't see advantage of DX10 in this case. My fsx is pretty smooth in DX9 with rare ocasional stutters. I tried DX10 becouse of better virtual memory usage

@B247NG - I'm positive we are talking about two different things and I apologize for the confusion. I am talking about the z-fighting on the runways and taxiways at many airports (not all) w/o the DX10 fix. I couldn't think of the name so called it stuttering. If you have good DX9 settings, I would keep them and make no modificatons, then activate DX10 with Steve's DX10 Shader fix. Do you still see stuttering? You shouldn't. Again, here are the features of DX10 as taken from the developer's website:

 

** VC Shadows - VC shadows greatly enhance the realism in the virtual cockpit and are the logical extension of the aicraft exteriod self-shadowing.

 

** HDR Bloom - Atmospherics are an important part of the flying experience so they wanted to improve bloom. HDR Bloom takes a feature that is almost unusable in DX9 because of performance and makes it both visually better and usable from a performance standpoint.

 

** Water enhancements - water is visually different with whitecaps and DX10 makes water react to weather - wind causes whitecaps on the water. The water shaders are more efficient.

 

More details can be found at the lead developer's blog - http://blogs.msdn.com/b/ptaylor/archive/2007/10/02/acceleration-and-sp2.aspx. Also found on the blog is the fact they tested the efficiency of the water and bloom improvements between DX9 and DX10. DX9 had 24.1 fps with 30 set as goal and DX10 had 30 fps with 30 set as goal, a 20% improvement under load.

 

I remember this z-fighting issue with runways/taxiways when DX10 was released with SP2/Acceleration. The developer said it was the fault of Nvidia drivers and we needed to get them to fix the issue. I set up a post to get everyone to send in a problem report to Nvidia as I figured it would get their attention if we sent in a lot of problem reports. Phil Taylor, the lead developer for FSX thought this was a good idea too and also said he would bring it up with Nvidia techs when he met with them. A lot of AVSIM members followed my detailed instructions and submitted problem reports but Nvidia techs didn't seem to care or notice (what about ATI techs you say? Well, ATI was still out of the picture as they had not issued any display drivers for DX10 or Vista. Many of those users sold their ATI card and bought a Nvidia card). Now, with Steve's DX10 Shader Fix, he was able to fix this z-fighting issue and make progressive taxi arrows visible again and that's all he did. I understand he's working on more possible fixes/improvements but that all remains to be seen. I hope he is successful. We need more people like him! I have DX10 enabled and I am now getting 40 plus FPS with an unlimited setting. I use the same display and FSX settings used for DX9 but those can be tweaked to one's satisfaction.

 

Best regards,

Jim

@B247NG - I'm positive we are talking about two different things and I apologize for the confusion. I am talking about the z-fighting on the runways and taxiways at many airports (not all) w/o the DX10 fix. I couldn't think of the name so called it stuttering. If you have good DX9 settings, I would keep them and make no modificatons, then activate DX10 with Steve's DX10 Shader fix. Do you still see stuttering? You shouldn't. Again, here are the features of DX10 as taken from the developer's website:

 

** VC Shadows - VC shadows greatly enhance the realism in the virtual cockpit and are the logical extension of the aicraft exteriod self-shadowing.

 

** HDR Bloom - Atmospherics are an important part of the flying experience so they wanted to improve bloom. HDR Bloom takes a feature that is almost unusable in DX9 because of performance and makes it both visually better and usable from a performance standpoint.

 

** Water enhancements - water is visually different with whitecaps and DX10 makes water react to weather - wind causes whitecaps on the water. The water shaders are more efficient.

 

More details can be found at the lead developer's blog - http://blogs.msdn.co...on-and-sp2.aspx. Also found on the blog is the fact they tested the efficiency of the water and bloom improvements between DX9 and DX10. DX9 had 24.1 fps with 30 set as goal and DX10 had 30 fps with 30 set as goal, a 20% improvement under load.

 

I remember this z-fighting issue with runways/taxiways when DX10 was released with SP2/Acceleration. The developer said it was the fault of Nvidia drivers and we needed to get them to fix the issue. I set up a post to get everyone to send in a problem report to Nvidia as I figured it would get their attention if we sent in a lot of problem reports. Phil Taylor, the lead developer for FSX thought this was a good idea too and also said he would bring it up with Nvidia techs when he met with them. A lot of AVSIM members followed my detailed instructions and submitted problem reports but Nvidia techs didn't seem to care or notice (what about ATI techs you say? Well, ATI was still out of the picture as they had not issued any display drivers for DX10 or Vista. Many of those users sold their ATI card and bought a Nvidia card). Now, with Steve's DX10 Shader Fix, he was able to fix this z-fighting issue and make progressive taxi arrows visible again and that's all he did. I understand he's working on more possible fixes/improvements but that all remains to be seen. I hope he is successful. We need more people like him! I have DX10 enabled and I am now getting 40 plus FPS with an unlimited setting. I use the same display and FSX settings used for DX9 but those can be tweaked to one's satisfaction.

 

Best regards,

Jim

 

No need to apologize Jim, and yes - Paul's shaders works perfect, i liked all experience except stuttering. I saw other DX10 users discutions, it seems to be DX10 issue. So i reverted to DX9 until someone find the fix/tweak for that.

Fps was better than in DX9, but i don't have fps problem in DX9, only in bad weather becouse of my GPU(which will be replaced with geforce 580 next Year). I bought 560ti when general opinion was that you don't need anything better for fsx.

Thanks for all links and explanations, i'll watch this forum for the news!

Paul's shaders works perfect

 

Steve is the developer of the DX10 Shader Fix. Paul has been the instigator of putting the fix and all the settings together in one location so that anyone who wants to install the fix has a basic one-stop location to get all the info.

 

I saw other DX10 users discutions, it seems to be DX10 issue.

 

Again, I respectfully am saying that there is no difference in the settings whatsoever between DX9/DX10. What works in DX9 as settings works in DX10 with the exception of a few improvements to FSX that I documented in Post #7. The Nvidia 560ti is an excellent video card that should run FSX well. Remember that FSX is more dependent on the CPU rather than the GPU (it was the reverse for FS9). Your system is overclocked to 4.9GHz which I consider way too much for FSX. You will only have problems (overheating mostly) and it could be the cause of your stuttering issues. Just saying...

 

Best regards,

Jim

The Nvidia 560ti is an excellent video card that should run FSX well. Remember that FSX is more dependent on the CPU rather than the GPU (it was the reverse for FS9). Your system is overclocked to 4.9GHz which I consider way too much for FSX. You will only have problems (overheating mostly) and it could be the cause of your stuttering issues. Just saying...

 

Best regards,

Jim

 

560ti is ok untill you get bad weather, than you can see big fps drop if you using REX textures, i mean high resolution textures. This is not the case with NVIDIA 580 series.

About my overclock, i don't have any problems with temperatures or stability. My temperatures are below 60c with FSX. And i don't have stutters with DX9, only in DX10.

So, i was thinking, I may have done something wrong with DX10 settings, becouse DX10 should be smoother then DX9?

Well that was a long departure from DX10. I gave it another try today and I am liking it. ENB mod still does not work but luckily I have Shade. I had my REX textures set to 4096x4096 and things were progressing very well until a few minutes into the flight and I received an error that said the memory could not be read. Not sure if it has anythig to do with AlacrityPC or the REX and FSX.cfg settings which I may have to tune down a little.

 

I am glad to see that Ultimate Traffic II textures show up, however I need to figure out why IVAO MTL aircraft are all white when I fly on VATSIM. When I compared MTL which are DXT1 16 bit to UT2 which are DXT3 16 bit and made then MTL DXT3 they would still not appear.after being converted.

 

Still, I think it's a whole new sim at the very least.

Remember that FSX is more dependent on the CPU rather than the GPU (it was the reverse for FS9). Your system is overclocked to 4.9GHz which I consider way too much for FSX.

 

Best regards,

Jim

 

Jim, how can you say FSX is CPU dependant then comeback and say 4.9 Ghz is too much for FSX? Makes no sense when we all know how well FSX scales with increasing CPU speed. You can never have too much CPU power when it comes to FSX.

 

- Sent from my rooted, Verizon Samsung Galaxy Nexus LTE smartphone via Tapatalk because haters gonna hate.

 

 

It's probably not an issue if you have sufficient cooling.

It's probably not an issue if you have sufficient cooling.

 

That applies to ANY CPU at ANY speeds. I agree that high temps can cause a CPU to throttle down, this applies across the board. I just think it's wrong to say 4.9 or any speed for that matter, is too much for FSX.

 

- Sent from my rooted, Verizon Samsung Galaxy Nexus LTE smartphone via Tapatalk because haters gonna hate.

 

 

Jim, how can you say FSX is CPU dependant then comeback and say 4.9 Ghz is too much for FSX? I just think it's wrong to say 4.9 or any speed for that matter, is too much for FSX.

 

I can say that because FSX runs quite well at 4.2 or 4.4 GHz which I consider pretty safe overclocks. I only said that because the OP indicated he wanted to upgrade his GPU and I saw no need for it. IMHO 4.9GHz is definitely not too much for FSX but I consider it to be too much. I frequent the CTD Forum here a lot and there's a lot of probable causes there. Of course, if you are a computer expert and really know what you are doing (as far as voltages and cooling), then there should be no problem. A lot of flight simmers have had their systems overclocked to 5.0 and I think there are some still around. But why? Why overclock a system to almost the max of its capabilities and risk destruction of your system? It doesn't make sense to me.

 

Best regards,

Jim