"The ONLY way to get Vsync working under DX10 Preview is to recode FSX. It just will not happen.... hence the term DX10 Preview." Sargeski,I don't know where you got that info. Recode FSX? Phil Taylor stated otherwise in his blog and in comments made on various FS forums. As I recall, Phil Taylor put an item on his blog regarding "DX10 Preview" and explained the reason why the guru's at Microsoft decided to name it that instead of DX10. It was done because of the hype that was put out about what DX10 would look like after SP2 was installed (if you had a compatible computer, video card, and OS). Remember the nice, almost real pictures of the mountain and the water in comparison to the same scene in FSX/FS9? They found they couldn't replicate that and decided to call it DX10 Preview so we wouldn't be depressed (or something like that) over not seeing exactly what was in the DX10 photos. I just wanted to set the matter straight as there's a lot of misconceptions, rumors, etc., being put out that are really confusing the heck out of the flight simming community.Ciao,Jim

"Watch the following youtube video, it shows the runway/taxiway clipping I experience under FSX DX10 with my nvidia 8800GTX"Great video newburn! Great representation of what us "lucky" people who upgraded our systems/OS's/video cards to get what's in the video. Maybe some terrain/scenery experts who didn't upgrade to DX10 capable systems and don't understand what we're so upset about will see this and maybe see a possible solution or at least clarify what exactly is the problem.Ciao,Jim

>"The ONLY way to get Vsync working under DX10 Preview is to>recode FSX. It just will not happen.... hence the term DX10>Preview." >>Sargeski,>I don't know where you got that info. Recode FSX? Phil Taylor>stated otherwise in his blog and in comments made on various>FS forums. As I recall, Phil Taylor put an item on his blog>regarding "DX10 Preview" and explained the reason why the>guru's at Microsoft decided to name it that instead of DX10. >It was done because of the hype that was put out about what>DX10 would look like after SP2 was installed (if you had a>compatible computer, video card, and OS). Remember the nice,>almost real pictures of the mountain and the water in>comparison to the same scene in FSX/FS9? They found they>couldn't replicate that and decided to call it DX10 Preview so>we wouldn't be depressed (or something like that) over not>seeing exactly what was in the DX10 photos. I just wanted to>set the matter straight as there's a lot of misconceptions,>rumors, etc., being put out that are really confusing the heck>out of the flight simming community.>>Ciao,>JimJim,One of the supposed benefits of DX10 was to allow an application to directly control certain graphic functions, such as AA, AF, Vsync etc..Some of this methodogly was incoporated into FSX. What this means is that any graphic function under direct control of FSX in DX10 Preview cannot in anyway shape or form be altered or changed (not by a control panel, a tweaking tool such as nHancer, anything). It is hard coded and under the exclusive control of FSX. Vsync is one such graphic function. An FSX code change would be required to allow a user to turn Vsync ON.IMHO if Microsoft had deemed that DX10 implementation in FSX was 100% complete it would not have been called DX10 Preview. There are way too many people having issues running DX10 both performance wise and graphically to call it a finished product. Hence why, in my opinion Microsoft termed it DX10 Preview.I also regularly read Phil's blog and remember the artist renderings quite well. So, I'm not sure exactly what record you are trying to set straight or clear what misconception I may have because I do not have any.I love FSX and am reserved to the fact that I will enjoy it operating under DX9 (the DX platform on which the game was designed). I wish DX10 performed as advertised (thats why I built my system around a DX10 card) but for me as well as countless others it does not. What amazes me is the amount of people that purport that graphics drivers are/may solely correct the implementation of DX10 in FSX that I feel is a real disinformation/disservice to the flight sim community.If anyone feels that I may have misinformed them then I apologize to you.Regards,--Bob

Hi sargeskiThe main reasons ppl think that there DX10 issue's (V sync aside) are driver related are that 1. Phil T has stated that Nv have major driver problems with FSX under DX10 in that Aces coded to the DX10 standard feature set but Nv's driver are(STILL)borked and dont comform to the DX10 spec & 2. ATI users dont seem to suffer the same issues under DX10 that Nvidia users do...There for id suggest (as many others would im sure)that if ATI doesnt have these problems under DX10(again Vsync aside)either Nv have broken drivers that they need to fix or broken DX10 hardware...the fact that they have'nt fixed these DX10 issue's when FSX has been code locked for over 5 months now suggests to me that they either dont give a toss about FSX(hey it doesnt feature a benchmark after all)& FSX Nv user community or they have broken hardware So Phil T if your reading this thread could you give us the real lowdown on this once and for all?

>There for id suggest (as many others would im sure)that if ATI>doesnt have these problems under DX10(again Vsync aside)either>Nv have broken drivers that they need to fix or broken DX10>hardware...the fact that they have'nt fixed these DX10 issue's>when FSX has been code locked for over 5 months now suggests>to me that they either dont give a toss about FSX(hey it>doesnt feature a benchmark after all)& FSX Nv user community>or they have broken hardware The orginal poster of this thread is a recently converted ATI user...he still has issues. As well as other ATI users. I think part of the problem is that many non ATI users say that ATI cards have no issues which evidently they do. I'm not saying that some of the graphical problems cannot be solved by a driver update some of them may. But a driver update is not going to be the cure all for FSX utilizing DX10 Preview.

"What amazes me is the amount of people that purport that graphics drivers are/may solely correct the implementation of DX10 in FSX that I feel is a real disinformation/disservice to the flight sim community."Thanks Bob for your comments. I'm not going to respond to everything you stated other than the above. It was Phil Taylor who told everyone that it was the drivers causing the DX10 problems in FSX and it wasn't DX10 Preview. That's why you have so many people complaining about the video card drivers. But YOU may be correct in that we are now finding that the DX10 problems are not only with the NVIDIA hardware/drivers but also ATI's equipment. Best regards,Jim

Hi sargeskiI like many ppl here was a little let down by Aces showing on the DX10 front,sure it didnt end up like they original alluded to with the magic screenies but ive come to live with that fact and except it for what it became & it does give my system a nice boost GFX wise i can run higher than like for like setting under dx10 with about a nice 20% frame boost to boot + better light and shadowWhat i would like now is for Nv to step upto the plate and fix what have been stated as errors on the part of there driver code is it really tomuch for us or Aces to ask of them to sort out there drivers so it atleast runs to the DX10 spec it was coded to run? it would be great if Phil would go on record and state just what the issues really are and who we as users should point the finger at as at the moment theres one set of ppl blaming Aces for the problem and one set blaming Nv (myself i blame Nv as ATI doesnt seem to have the same problem & Nv's driver support for vista and anything other than crysis under DX10 really sucks)As you say a hand full of newer ATI users are having problems but i think these are more likely config problems or control pannel setup errors that can be sorted out by the user as many many more ATI users dont report having those same problems in the end they are not like the long suffering Nv users who ALL have the runway clipping under DX10 Now if FSX had a built in benchmark that was used by all the major review sites i bet you'ed never see a driver bug in FSX or if you did i would get hot fixed in a day or 2,maybe Aces should keep that in mind for FSXIIngame Benchmark = better driver supportPeace Gizmo

HiComplied shaders not the ones in the FSX install folder dont delete those or your looking at a reinstall to get them back!Under vista the complied DX10 shaders can be found in X:UsersXXXAppDataLocalMicrosoftFSXShaders10(replace X with your drive and XXX with your vista user name)(dx9 shader are in X:UsersXXXAppDataLocalMicrosoftFSXShaders)btw you will need to use the tools - folder options - show hidden folders & file option in windows explorer to see the above pathsBack them both up just to be on the safe side ;)Once you restart FSX will rebuild/re complie the shaders for youIf you dont have it already let me know and i'll post CB's fixed DX10 rain/clipping plane shader for you hope that helps and keep us upto date on how you get onBTW if your using ATI tray tools to control your 3870X2 ive read that it doesnt work yet and your better off sticking with the CCC (even if it is bloatware)Peace Gizmo

>Hi sargeski>>I like many ppl here was a little let down by Aces showing on>the DX10 front,sure it didnt end up like they original alluded>to with the magic screenies but ive come to live with that>fact and except it for what it became & it does give my system>a nice boost GFX wise i can run higher than like for like>setting under dx10 with about a nice 20% frame boost to boot +>better light and shadow.Gizmo,I couldn't agree more with you on being let down. However unlike you if I try to run in DX10 mode with like DX9 settings I take a 20-50% performance hit depending on where I fly. Again, I would like to iterate, like for like settings. I am but one of many FSX users who exhibit this behavior. Maybe it has to do with the resolution I'm running at, who knows. What I do know is that Microsoft cannot expalin why I and many others have this performance decrease and others have a performance increase. Driver related or correctable.....in my logical mind I tend to think not (else everyone with this NV video hardware would be experiencing comparable issues).Let's keep our fingers crossed that a driver update helps those that are getting a performance boost from DX10 Preview.I on the otherhand am now resolved to run and enjoy FSX under DX9.

I have a NVIDIA and of course the problem. However it was cured in a lot of airports by new afcads.Jos

Hi Bob, Same here, a ca 40% hit in DX10. For me FSX has been good since SP1, also very happy with DX9. :-) And frankly, I don't feel let down, IMHO, DX10 was too hard to tackle with Vista being too late. The DX10 Preview might have made more sense now after SP1? Kind regards Jaap

Hi Jos

"I have a NVIDIA and of course the problem. However it was cured in a lot of airports by new afcads."Jos

Interesting. The shots are at LPPT rwy 03. I'm using latest WQL NVIDIA drivers.Jos

MyTraffic.