I think this one man - ******* - has replaced the whole ACES Team! FSX is not dead! :(

Yes, these contributions are great, but there are others that we cant forget!! So many have contributed some incredible fix's and product and put in sooooo many hours and ask nothing in return.You have to admire the amount of time that must have gone into this. I am assuming these new cfg entries come from the ESP SDK or some form of source code. Not an easy task to take these entries and monitor cause and effect. The entries may or may not have adequate documentation, thus the experimentation phase of the effect these have on different system must have been grueling. The Aces team may or may not have known the finer details of upcoming/future hardware but apparently had some information and time for experimentation based on what they may have known at that time. Not having the hardware/systems in hand may explain the differences/outcomes with the tweaks between systems and even systems which appear to be very similar. It also may explain why other issues may surface that sometimes cannot be explained. Also, what may take considerable time to flush out is not so much the effect of one tweak, but what the effects one tweak may have on another tweak that is introduced. This can compound the testing effort. As a programmer for many years, I saw first hand issues that can surface when new code is introduced or removed, that interface with other modules in which the source code cannot be seen (black box so to speak). I certainly appreciate his time as this is alot of work to undertake for one guy! RegardsBob

No he isn't. Just look at his photo. He is a nice guy from Caracas, Venezuela. :(

That photo on *******' posts is DEFINITELY not *******, either the Altuve or the "of Nazareth" variety.It's Hugo "Mickey Mouse" Chavez! I do chuckle every time I see it.BTW, two thumbs up on this vSync setting with my 5870. With 2xAA in supersampling mode, it looks as good as my 285GTX ever did.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

it might be an idea to actually make a guide in the form of a PDF or something in the likes of ?

+1 Please a sticky post in the FSX forum to summarise all these tweaks, how/when to use them. :( Its all a bit confusing at the moment!

Is FORCEVSYNC (windowed mode) the same in that you need to use the numeric value '1'?

On my system (Win7+nVidia+DX9+FSX+XPack) [GRAPHICS]ForceWindowedVSync=1 (edited)EDIT:i made a booboo, see edited aboveEDIT3: Thank you *******

Hi, I have Nvidia and using nhancer with vSync On setting (I have to use nhancer because AA don't work for me even with 197.45). So shoud I use this new tweak? any advantage?Thanks

I tried that but unfortunately that doesn't work... I still get terrible tearing in windowed mode with my GTX285.But this is a very interesting tweak, because it makes buying a HD5870 a possibility...! I've been looking at the GTX480, but it's got too many disadvantages. I didn't want an ATI because of the Vsync problem. But that's solved now...!

Did you try TRUE instead of the 1?

Hi, I have Nvidia and using nhancer with vSync On setting (I have to use nhancer because AA don't work for me even with 197.45). So shoud I use this new tweak? any advantage?Thanks

It IS possible to set 'Application Contolled' for vSync with nHancer, but don't actually know if it's ok to use it.I'd like to know too please?Thanks

That photo on *******' posts is DEFINITELY not *******, either the Altuve or the "of Nazareth" variety.It's Hugo "Mickey Mouse" Chavez! I do chuckle every time I see it.BTW, two thumbs up on this vSync setting with my 5870. With 2xAA in supersampling mode, it looks as good as my 285GTX ever did.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

I have a chuckle as well! I was thinking of emailing him and suggest he find another picture with a different background. I don't think he realizes that the two black circles in the background blend in with his head and look like Mickey Mouse ears. Thanks ******* for all your hard work!Bill

I have a chuckle as well! I was thinking of emailing him and suggest he find another picture with a different background. I don't think he realizes that the two black circles in the background blend in with his head and look like Mickey Mouse ears. Thanks ******* for all your hard work!Bill

I'm fully aware of the Mickey mouse thing. No need to contact me because I'm not a supporter of comunism

OK, with this latest v-sync cure, is there any advantage to going to an ATI 5870 over a GTX285?

OK, with this latest v-sync cure, is there any advantage to going to an ATI 5870 over a GTX285?

The answer could quite possibly be...yes. We need some hard, objective testing. Stephen

On my system (Win7+nVidia+DX9+FSX+XPack) [GRAPHICS]ForceWindowedVSync=1 (edited)EDIT:i made a booboo, see edited aboveEDIT3: Thank you *******

Absolutely perfect!!! Works even in windowed on my GTX285. That is all I was really more missing from my FSX... except double performance! :(EDIT:Strike that. Windowed VSync somehow limits FPS to 30, and won't go a FPS over. Not that I need it, weird limit though.

The way I see it, Nvidia still might be the better choice due to the image quality difference. ATI cards can do multisample AA *or* supersample AA, there's no "third way" combined mode that uses both to obtain great image quality with high performance like there is in the Nvidia driver. Supersample alone is a better AA algorithm, but it comes at a huge performance hit at anything but the lowest levels. ATI has a feature called "Adaptive AA" that's supposed to AA the edges of alpha-test objects like the trees, power line pylons etc, but the last time I was able to check that on my old 4870 card, it didn't work at all in FSX. (This is equivalent to Nvidia's "Transparency AA" option)This fix eliminates one of the major issues with ATI cards though, yay!

Absolutely perfect!!! Works even in windowed on my GTX285. That is all I was really more missing from my FSX... except double performance! :(EDIT:Strike that. Windowed VSync somehow limits FPS to 30, and won't go a FPS over. Not that I need it, weird limit though.

Actually... is your system capable of producing 60 at all times? If not, then 30 is actually what you'll see - it's part of the way vsync works, it's going to drop down to your refresh rate divided by 2 (then the refresh divided by 3 and so on down the line) because you can't sync to fractions of frames. This is the downside to using vsync - if you can't maintain a framerate equal to the monitor's refresh rate, you're going to see a lot of large swings where the framerate gets cut down to half the refresh rate or more. A lot of gamers who play twitch first person shooter games leave vsync off and deal with the tearing because of this - you'd much rather have 55 FPS and tearing vs. 30FPS and no tearing in a game where the framerate matters hugely to the gameplay like that. Vsync absolutely does cause what would be small drops in framerate with vsync off to be much larger ones with it on.

OK, with this latest v-sync cure, is there any advantage to going to an ATI 5870 over a GTX285?

Not much. I have one of each, and performance and IQ in FSX are similar.If I were to have to choose between the two right now, it'd be a tough choice. I'd probably go with the 5870 for its stability, and its superior performance in most other 3D games (if that's important to you). Prior to the last few versions of ATI Catalyst drivers and the just-discovered misplaced vSync setting, I would have said the nVidia 285 had a clear edge in FSX. Now, not so much.The 285 churns out higher frame rates in FSX, especially with the eye candy cranked up (autogen, ultra-dense scenery complexity etc) but if you overdrive the frame buffer it'll black screen, lock up, or otherwise crash. The 5870, if overloaded (especially with hi-res clouds and detailed add-on scenery), will drop frame rates way down, but I have yet to make it crash on me. Neither the 285GTX or the 5870 is capable of running FSX without a moderate level of compromise--assuming that the rest of your system is sufficiently powerful to drive the cards to their potential, which with these two I would say is a quad-core CPU at ~4 GHz. With the nVidia, you have to tailor your autogen, scenery complexity, texture bandwidth and max frame rates--and if using BP=0, you have to make sure your CPU doesn't overrun the frame command buffer by pushing too much too fast to the video card or it *will* crash on you. With the ATI, you need to compromise by dialing back scenery complexity, weather and/or cloud resolution, raindrop effects, or by reducing IQ by selecting multisample AA mode instead of supersample--or accept a drop in frame rates.On Wednesday an eVGA superclocked 480GTX lands on my doorstep. Should be a lot less compromising going on around here once that beast is installed in the system, though I may end up having to do a bit of extra work to strap a water jacket on it.CheersBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Bob, Thanks for the reply. That helps a lot.