Its Thanksgiving Day in the U.S. and I hope you are having a good day wherever you are. One of the blessings for which I am grateful is all of the good people who are willing to give a helping hand to people like me who may be real world pilots but who are not very computer or graphic "smart!"NOW my Problem: This is my last shot on AVSIM. I'm not positive this is a Hardware problem ... but my initial post was booted off of the main forum. I reposted there and also on the "PC/MAC forum with a few helpful comments but NO solution. This is my last shot. Here are the symptoms and conditions:1. I am using a Samsung 226BW display. In SP-2/DX-9 my image is rock solid (no distortion). BUT IN Acceleration, SP-2/DX-10 Preview mode, I am getting a wavy display. As long as I am not moving the view, things are not too bad, though there a little "bending" here and there, but not too much... B U T when I pan, or bank the aircraft... there are "waves" that move across the screen... and everything becomes somewhat unstable. I'm obviously no expert at graphics, but from examples I have seen online, I think this is "tearing" but not full blown tearing. It almost makes me "seasick" or woosy to watch it long. Its like I'm looking through water or heat waves ... something like that.2. Here is my Setup:E6700 @ 3.625 ghz; EVGA 8800GTX, EVGA 680i MB, 4GB Crucial Balistix Ram at 800, Samsung 226BW display, VISTA 32bit, 3. I have tried to resolve this with the following: (Sometimes at the suggestions of others and sometimes on my own)a. I have tried numerous NVidia drivers including both WHQL and Beta. Currently I am using what was (yesteday) the latest NVidia Beta, which I think is 169.12. THE PROBLEM REMAINS with EVERY driver.b. I have tried to FORCE ON VSync... both with nHancer and with the nVidia Control Panel. I can't seem to tell a difference. The nHancer manual says that VSync won't work unless the application calls for "triple buffers" ... whatever that means. I don't know if FSX does that or not. The nHancer has a place to check that supposedly "forces" triple buffers, but it says it only works with OpenGL. I tried it anyway... THE PROBLEM REMAINED.c. I have set my frame rate at every place known to man between 10 and unlimited. I read that with 60hz (unadjustable) refresh rate on my monitor I should try whole number fractions of that to get vSync to fix the problem. So of course, among my many ajustments, I tried 60 (that's a laugh except in the desert... which could be a lot of places in FSX ;^)... I also tried 45, 30, 20, 15, 10. THE PROBLEM REMAINED.d. One good soul pointed out that Phil Taylor mentioned some Vsync lines to add to the Display part of the cfg... But those mentioned on his blog are for SP-1 and were suggested months ago. I tried them anyway. THE PROBLEM REMAINED.e. I inserted the BUFFER POOLS line and the PROBLEM REMAINS.I DID NOT turn all sliders to zero to see if the problem was still there. Sheesh! Why didn't I think of that? I may try that today!I DID NOT start uninstalling my add ons. I have several. FEX, Megascenery SC/Hawaii, UTX USA, FSDIscover, ASX/X Graphics, VancouverPlusX, probably a few others, and several airplanes.Since this the problem is only in the DX-10 mode... I didn't think it was a hardware problem... but those more experienced than me must have thought it was, since my original post was deleted from the main forum (and NOT placed here). I thought I should make a last try on this forum. I really like the DX-10 renderings even with the flashing textures here and there. But it is (for me) unusable as it stands.Thank you so very much for reading this long post. Whether or not you have any suggestions, I wish you well and have a great Holiday Season!!Steve

Hi Steve,IMHO, this is another one of the driver issues not yet addressed by nVidia. AA/AF can't be controlled either. Someone mentioned that there are several DX10 titles that don't allow the level of customization that DX9 allows.Microsoft and nVidia will need to collectively work on the issues to make the options available in the driver. Phil Taylor stated they were, but it's probably a lot of work and not some simple tweak.Happy Thanksgiving.Regards,Jim Karn

Thanks for your thoughts regarding the solution lying in a new driver, Jim.My only problem is that another poster said this:Quote: I turned it on in the Nvidia Control Panel.Not sure if DX9 and DX10 are treated the same... also read somewhere that some driver releases have predefined settings for specific games, that need to be deleted... I'll wait for someone else to fill in the blanks, but if you have the same wavey screen that I did, Vsynch=On will fix it. [For me it is not clear if he means BOTH DX-10 and DX-9 were both fixed or just one]Also this post:Quote:In my case, I turned it from "Application Preference" to "On" in the Control Panel. No changes in fsx.cfg.Just make sure that there is not some kind of over-ride in the Control Panel application presets..The effect was dramatic, first: wavy scenery updates when I banked the plane and after: rock solid scenery just as it was prior to Acceleration.****I am going to email this gentleman and ask if he is referring ot DX-10 or just DX-9But if it is DX-10 that is stable... there is still hope before a new driver fix.Thank you,Steve

Steve,If its any consolation I have the same issues with DX10. No matter what anyone else has stated regarding the NVIDIA control panel you just can't control anything with it in DX10.You cannot increase AA or AF. You cannot force V-Synch on.If a driver does not come out to fix theses issues, one thing is for sure. I will not be using DX10. On my system DX10 looks just plain horrible compared to DX9.

Hi Sargeski ...Thank you for your response. Actually I just received an e-mail response from the other poster quoted above. He confirmed that it was only under DX-9 where the VSync worked. He isn't even trying DX-10. I'm with you. I hope a new driver comes out to fix this sometime soon... maybe by Christmas at the latest??? That would be a Christmas present for me. I can't believe I bought that 8800GTX and Vista 7 months ago in anticipation of all the "Magic-screen" propaganda of MS stating that FSX would be quite a showcase for DX-10 under Vista. Ah well ... a lot of us learned our lessons. Hopefully we will be able to enjoy DX-10 before FS-11. Thankfully DX-9 is doing a nice job under SP-2.Steve

>I can't believe I bought>that 8800GTX and Vista 7 months ago in anticipation of all the>"Magic-screen" propaganda of MS stating that FSX would be>quite a showcase for DX-10 under Vista. Ah well ... a lot of>us learned our lessons. Hopefully we will be able to enjoy>DX-10 before FS-11. >>Thankfully DX-9 is doing a nice job under SP-2.Steve,I have the exact sentiments as you regarding the spin campaign on FSX, DX10 and Vista and you are right....Thankfully DX9 is doing a nice job under SP-2.

If ACES didn't lose so much time doing SP1 and SP2 I think FSX DX10 would have been alot different. They just ran out of time to do anything incredible.Imo they never anticipated the need for SP1, let alone SP2. It just set the whole development process back nearly a year.

I think you are pretty much on track there. I remember when Phil Taylor posted on his blog, or somewhere, saying they were turning the corner to DX-10 work. I think that was after SP-1 release. Then I knew there was Acceleration coming with a deadline (which would include the SP-2 package)... I couldn't imagine how they would have the manpower or hours to create some really special things [not to say the lighting and cockpit shadows aren't "special"] but I think most of us had hoped for much more. Hopefully, when FS-11 is created, ACES won't be blasted with a new OS or a major modification to DX, and a huge new processor architecture. Who knows... maybe even Vista will be optimized by then?!?Of course... there will probably be the required $2500 to $4000 donation to have hardware that will make it run right... and who knows... after the donation NEXT time... maybe it WILL run right! ;^)Actually, under the FAA Light Sport Aircraft rules... you might be able to earn a RW license for that $4000 figure. I'm planning to invest my Flight Sim budget next summer in getting current (already licensed as ATP/CFI-I) and starting to instructh in these planes. They look wonderful. Saw many of them in person at Oshkosh this year.

I also have the tearing problem.Im reading on alot of fora around that they have this problem and blame nvidia's drivers etc..I use a HD3870 and i also have the tearing problem, with the latest catalyst drivers.. So its not nvidia related..Hope it will soon be fixed!!

>I also have the tearing problem.>>Im reading on alot of fora around that they have this problem>and blame nvidia's drivers etc..>>I use a HD3870 and i also have the tearing problem, with the>latest catalyst drivers.. So its not nvidia related..>>Hope it will soon be fixed!!If your running DX10, it will never be fixed (Vsync is controled by FSX under DX10 and is forced OFF there will be no more SPs for FSX and you cannot override FSXs setting with your driver settings). If your running DX9 you need to force Vsync on via your driver control panel.

>>I also have the tearing problem.>>>>Im reading on alot of fora around that they have this>problem>>and blame nvidia's drivers etc..>>>>I use a HD3870 and i also have the tearing problem, with the>>latest catalyst drivers.. So its not nvidia related..>>>>Hope it will soon be fixed!!>>If your running DX10, it will never be fixed (Vsync is>controled by FSX under DX10 and is forced OFF there will be no>more SPs for FSX and you cannot override FSXs setting with>your driver settings). If your running DX9 you need to force>Vsync on via your driver control panel.>Hi there,Thanks for your tip! I allready tried it under dx9, and forcing vsync on, on my ati card, but the tearing was the same.. So i just uninstalled sp2, and im happily flying again lol..

">>I use a HD3870 and i also have the tearing problem, with the>>latest catalyst drivers.. So its not nvidia related..>>Hope it will soon be fixed!!>If your running DX10, it will never be fixed (Vsync is>controled by FSX under DX10 and is forced OFF there will be no>more SPs for FSX and you cannot override FSXs setting with>your driver settings). If your running DX9 you need to force>Vsync on via your driver control panel.Hi there,Thanks for your tip! I allready tried it under dx9, and forcing vsync on, on my ati card, but the tearing was the same.. So i just uninstalled sp2, and im happily flying again lol.."Wow! Thanks for posting. I see ATI users are having the same DX10 Preview problems as Nvidia users. What's up with that? Maybe it IS a coding problem within FSX and not a driver issue...Jim

Now that I think about it.. the only thing I ever saw with the x23870 was places where VSYNC may not have been working right.. but I do remember I did not experience those tears all the time or anything that appeared to be a show stopper and it seemd to be variable in how bad it showed through frame lockI saw none of the problems such as flashing textures and other things the 8800GTX displayed.So vsync in DX10 is an FSX issue and probably not driver relatedand I dont use DX10 to fly..just test hardware. I have my opinions around that and I know others prefer the mode for FSX, and, the Vista OS because they want Crysis and other DX10 support.

>So vsync in DX10 is an FSX issue and probably not driver>relatedIt sure is. Vsynch is hard coded off in FSX's DX10 preview. Under DX10 Preview FSX has exclusive control of certain graphics functions. Those that are exclusively controled cannot be manipulated by the Nvidia Control Panel or via Nhancer they are controled by FSX itself period (one of the touted benefits of DX10, supposedly).

Well, I will relay this.. and hope I dont get smacked, which i shouldnt but here goes... I am given a specific set of tasks to complete when I look over hardware and MSFS was not ever on that list, Crysis was the DX10 target application which should tell you guys why there is no real support going on in fixes, at least nothing dramatic as you see in other applications. Modern ATI really has the least issues in all of them and that goes back to the fact they they dropped to the 20 and punted last year instead of trying to use the old wafer technology and resell as much of as they could for the highest return. Once the -true- 'new' nv cores get to market I am sure they will also show the same results.Now, I have said enough.. you guys get the picture