To me the patch went as smooth as it can get , in less than 2 min I was ready to test it, and I noticed an efective increase in FPS, and fuid as it was before. Is the efect of disablig the xml at the same level of performance as the previous one? I can't tell a diference but to anyone who tryed, what where the results?

Hi,I've tried it with and without. But I haven't seen the difference. My upgrade went also very good. Also within two minutes.Maybe there are others who can tell something about the xml file.

I didn't disable the '.xml' file after the patch but I noticed that autogen still can drag framerates on approach when coming in for a landing after along flight (at least that's how it was doing a KDFW KLAX flight last night). I'm still not ready to give up my extra autogen objects by disableing the '.xml' file but tried lowering the 'Extreme' level setting to 'Very Dense' to see what happens.

I'm also going to give the autogen a fair chance. Last night I did 3 circuits around Seattle in the C182 at about 6 thousand feet with he autogen set full right. The FPS remained steady and if I remember correctly, with the old implementation the FPS would have started to drag by that time.

Well, the old bug certainly seems fixed, and using the default.xml patched seems to work fine. There will of course be frame-rate issues if flying over a densly populated area, but once clear, the fps will rise accordingly. I've tried this over a 'very dense' London city, flying low to check out the new bridges across the Thames. London will always bring fps down..mine averaged at 19fps whillst flying out of Heathrow and leveling at 2500ft. Nice detail, and I like the new bridges, and once I'd cleared London, and was heading out towards the North Sea, the fps rose nicely to, and stayed at around 33fps (locked at 34). Going back to Heathrow, the fps only started to drop dramaticaly as I approached Heathrow...a busy airport at 90% traffic WILL play havoc with your fps!!So, is there really any point in disabling the default.xml file? It's a little extra detail that we can now see when flying low, for no added performance cost!

I noticed that also. As soon as you turn away from a very dense area the FPS quickly climbs back up.And many thanks to some very dilligent people on this, and other, forums for researching the problem. In fact, the wording in the MS fix blurb is almost exactly as the problem was described here about 9 or 10 months ago.