I just switched over from nvidia to ati in hope of finding better fsx compatibility but unfortunatley AA is still not working with the dx10 preview. That means this is a microsoft problem. What is Microsft doing about this?

Mike, which ATI did you get? I have two FSX systems running perfectly well with the somewhat older HD2400 Pro DX10 cards.If you went with the newest 3800 series, you should be rocking! ;)

Ive got a 3870x2.

Same here, DX10 is broken on my V64. No Vsync for example, but I didn't try hard... Maybe Vista SP1 will help? Luckily, DX9 more than compensates for now. :-) Kind regards Jaap

>Same here, DX10 is broken on my V64. No Vsync for example,>but I didn't try hard... Maybe Vista SP1 will help? >>Luckily, DX9 more than compensates for now. :-) >>Kind regards >>JaapYour DX10 is not broken its DX10 Preview (an unfinished product). There is a good reason Vsync does not work. Under DX10 it is explicitly controlled by FSX (set to OFF under DX10 Preview). One of the supposed benefits of DX10 was to allow applications to explicitly control some of the graphics settings. Some of which has been implemented into FSX.Unfortunately, there is nothing and will be nothing that will make it work (since there will be no further updates to FSX).

AA is not broke in DX10 FSX SP2/Acceleration at least with Nvidia cards. You need to turn on the In Game AA, then using NHancer select Enhance Ingame AA. It works in both Full Screen and Window mode. Not sure what or if there is an equivalent setting for ATI cards, but you should at least get the Default AA from the In Game setting I would think. The thing I notice with DX10 mode, is I can't raise my in game resolution higher the 1280x1024x32. In DX9 mode I can go to 1980x1050x32 (The highest my projector can display)

Well Im not getting any AA with the dx10 preview. If I turn it off then I get aa. No setting I choose has any effect. Phil Taylor himself posted on his blog that "AA had not changed in sp2", maybe Mr. Taylor would like to comment?

>Well Im not getting any AA with the dx10 preview. If I turn>it off then I get aa. No setting I choose has any effect. >Phil Taylor himself posted on his blog that "AA had not>changed in sp2", maybe Mr. Taylor would like to comment?All I can say is it works for me!!

What driver version are you using Pilot533 and have you removed your FSC.cfg file and the complied FSX shader folders and let FSX rebuild them?I know with my 8800gts(640mb)that FSX DX10 preview on vistaX64 has various problems which differ from driver set to driver set under 169.21 i get a driver not responding error within minutes of flight 169.25 last for about 20min 169.44 goes for hours without a problem but has a issue going from full screen to window mode,where if i swap between the 2 full screen only renders what was in the window and shows my desktop for the rest of the screen,I havent had any problem with AA as long as i keep AA ticked ingameAA lvl doesnt seem to change under DX10 regarless of what is trying tobe forced under nhancer/cp/riva tunner so i guess DX10 FSX is also requesting its own AA matrix/lvl inengine that like the Vsync request cant be overidden by 3rd party appsIm thinking about popping for a 3870x2 myself as i've found Nv's driver updates to be very very poor for the 8800 gen of cards(going on 90day+ without a WHQL driver atm!)not just for FSX but for pretty much any game that is'nt crysis or doesnt feature a benchmark.....Do ATI have the Zbuffer/clipping runway textures issues under DX10?Nv drivers have suffered from this for the last 5 months,which is pretty shocking for a code locked game

>>Do ATI have the Zbuffer/clipping runway textures issues under DX10?<< No, there aren't. AIM, I haven't tried hard at all. I'm sure there's a way to get Vsync working. There are also thin 'stripe artefacts' sometimes with the X2 (don't know about regular X38xxs), switching back and forth between Triple Buffering and Aniso and Multisampling and Supersampling fixes that all of a sudden. Kind regards Jaap

Exactly what folder is the folder containing the compiled shaders?I see a folder called "ShadersHLSL".I assume it's safe to delete the folders inside that folder and FSX will rebuild them? I don't want to delete the wrong files.Problably a good idea to do it when updating vid drivers.Thanks Gizmo.

>>>Do ATI have the Zbuffer/clipping runway textures issues>under DX10?<< >>No, there aren't. I find this issue to be very confusing.Some ATI users have the texture clipping on runways/taxiways, and some reportedly do not. It seems all nVidia users have them, or at least I can't recall anyone saying they didn't.Baksteen, and other ATI users, please do me a small favor in the interest of narrowing down who is responsible for the problem.Watch the following youtube video, it shows the runway/taxiway clipping I experience under FSX DX10 with my nvidia 8800GTX and Vista Ultimate x64. Please confirm that you can not replicate the symptom with your ATI hardware under the DX10 preview.

It's been 4 or 5 months since Phil reportedly contacted nVidia. Sometimes nvidia makes me want to ram my head into the wall. Or maybe it's a vista specific problem? Maybe I should start a thread in the hardware forum to ellicit users experiences and system specs's. But I shouldn't have to do that, Phil said it was a driver issue? :-newburn

>>AIM, I haven't tried hard at all. I'm sure there's a way to get Vsync working.<

Hi, FWIW, I've tried the preview with 3 different Ati adapters till now and none of them showed those artefacts in the DX10 preview. What I dislike most about the preview to date, is running with AC shadows on (a must do for me). It drags perf down the drain much more compared to the 10-15% hit in DX9. At least over here. Waiting for Cat 8.4 for the next DX10 try... :-) Kind regards Jaap

Hi Sargeski, so all those who say it's working fine for them are out of sync with their V? Fair enough if so, then I'm glad I never bothered. :-) Kind regards Jaap