It is nice that ACES kept us informed. It will be nice to see FSX run better for all.Some of you posting here, there maybe no hope for you. A few must just have it in for either ACES or FSX no matter what happens. Why do you even have to post remarks when ACES has bent over backwards to keep us updated even singled out this AVSIM Forum by name on blog.When they say we will get a patch you whine no we want or when its been 30 secounds after thanksgiving. Then when Phil post back or it want be the right patch we know it want be FSX will never run well we know it all.:-roll ACES has been a class act comparied to some of the posters here. I'm glad Phil is going to blog a lot of info its a shame he had to do this because of a few posters that will not back off and give them some respect and time.

Hi Phil,Thanks, this is most encouraging! Also, I enjoyed reading your very informative blog. Regards,Mike

Let me add my thanks to the growing list.It is good to see that the team cares enough to try and come up with a solution rather than blindly defending the product. I look forward to whatever may be released that could enhance our experienceBill

Phil,Thank you for providing this information. Openness in these issues is appreciated a lot! :)rgds,Tero

Correct me if wrong. I read the blog to say that no decision about what needed fixing would be made until sometime in January. It did not say the update would be released in January.So all we really know is they are studying the issues and we will see a update sometime next year. Specific time period unknown. Also, there will be a second update for Vista/DX10.Here is my concern. From reading posts and what I have emailed, there are probably many small issues that could be corrected and released very quickly. Why wait and package every fix into one update sometime next year? Flight Sim software developers do releases almost every day and we seem to manage downloading and installing them just fine. I'm not sure why some think ACES is doing us a favor fixing problems. MS and every other software developer fix problems and release updates. It's just part of the sale and part of business.Am I thankful to hear that updates will happen? Yes I am! I just don't agree with placing them all in one or two packages. SD

I understood from the blog that the update will come After January. Not in January.MS has long history of "withholding" patches and corrections... I doubt they're gonna change that now.Tero

This is the most important quote (to me) form Phil's Blog:In the long run, it

The decision to create and ship a release has been made. As with every release, we have a set of things that we "must have" and a set that is "nice to have" and until we are closer to release I just cant comment on what is in/out since some of that depends on progress made.True, the release wont be available in January, that is just my self imposed deadline to return and discuss further. We do have a timeliness issue, though, and are aware of it.Given each release exacts a test and release management cost, which delays other work, it really is a good thing to batch these up and pay 1 set of test costs and 1 set of release costs. If there was another major issue that blocked the 3rd party community like the Aerial Imagery bug, we would take steps to expedite that sort of fix. But that sort of thing is really different in kind than this "SP1" style release. hth Phil

Phil I only listen to and read you now...:-) If you need a fresh guinea pig to do any testing just let me know :-waveThanks for staying in touch with us, and no need to rush it!Bill

A true "patch", or perhaps change to source data (texture adjustment) could be done quickly, but anything that requires a recompile is going to take time to build and test, unless you want a likely disaster.scott s..