Captains-We have placed a temporary Interim update release in our download files Service Updates section.This is NOT considered a full Service Release, however since we have determined that a complete update will take longer to produce due the the complexity of the task at hand (especially with the electrical system), we consider an interim solution something of interest.The "Temporary Update" fixes (we hope!) some important issues that have been reported:1) V1/80kt engine failures not called for in the PMDG menu.2) Electrical/Battery Drain failure.3) manual WT selection in the PFD/ND configuration.4) localizer backcourse needle not working properly.5) V-speeds for some -900 weights6) G/A could be engaged before approach phase, causing havocWe are aware that not all of you experience this problem, but we've noticed that for those who do, this tends to be quite annoying, so we hope this will help you until such time when we're ready with the complete Service Update release.We would like to note that we're constantly monitoring this forum (and your support emails) for issues that you may have, so we're aiming to fix most problems (or at least note workarounds) for the proper Service Update release.You can find this temporary service update here (if you're too lazy to check our downloads section):http://www.precisionmanuals.com/downloads/...le=423&iType=23

Thank you!As you are monitoring this forum there are others monitoring your homepage. There were over 60 downloads BEFORE you posted this.:-lol Could you tell us what the problem was with the engine failures?CheersThomas

Dear PMDG-Team: As always outstanding performance in customer service! Thank you very muchBenjaminLSZH/Zurich Switzerland

Gentlemen thanks a lot!As expected, once again first-class service. Looking forward to the official update.Best regards,Nikos Oikonomidis

Thank you PMDG :)Finally fixed my Radio problem! did a 700NM flight, and no probs! yay :DI can enjoy PMDG now more then I used to:)

Thank you PMDG.

Thanks guys :) Your support puts others to shame.

Chris

Hey PMDG,Ignore my last reply, my Radio issue still doesn't work good...I did today a flight that was like 440NM, and my Radio died, what is funny, how come yesterday I did a fligth that was over 600NM and today 440NM and it got locked today and not yesterday.........So if you could please still look at the issue ...Thank you.

The radio problem just doesn't seem to cure! Maybe it was because the flight was a multi Royi? I don't know, but PMDG, what CAN POSSILBY BE WRONG after installing the Patch??All the Best,Robin Bilgil!http://www.precisionmanuals.com/images/forum/800driver.jpg

I'm not sure, but I don't think this patch was supposed to fix the radio problem. This fix was just temporary to fix the engine failure and battery issue. Chris

Hi,I realize this update was not supposed to address the radio problem, so I am not really complaining that it is still broke... but I have been silently browsing the forums for some time and thought it was time to add my input:Persionally, I have always suspected my radio lockups were due to either A) time compression or :( changing modes on my saitek x45 controller. These possibilities don't seem to be directly mentioned anywhere, so perhaps I am just crazy, but every single one of the ~10 radio locks I have experienced seems to have come after switching from time compression back to realtime, then switching modes on my saitek controller. Granted, the radios could have actually locked sooner and I just didn't notice, but it seems to be becoming too many times to be a coincidence. One thing I know for sure-- I have never had my radios lock on flights where I don't use time compression (then again, I don't personally have time or patience to make flights > 1 hour without time compression so this might not be a helpful observation)As far as my suspicions of switching modes on my saitek controller-- I have noticed that sometimes when I switch the x45 mode switch the autopilot disengages. The mode switch itself shouldn't send any command to the PC and I have become very careful recently to be sure I am not touching any other buttons when I switch modes, yet it still happens from time to time. So it seems to me perhaps my controller is sending some kind of noise to the PC which is interpreted as the command to disengaging the auto-pilot... and also somehow locking the radios other times? Any chance everyone with the radio problem has a saitek x45? You probably are a lot further along tracking the cause, but since I've seen no other mention of these theories, I thought I'd throw them out there.A couple of other (possibly misplaced observations):I am somewhat amazed at the level of support offered in these forums. I do enjoy your software (up until the point the radios lock), but geez, when any other company releases software with such disabilitating bugs, you rarely see such an outpouring of support for their "first class" customer service. Rather, you get a deluge of angry messages that the bug existed in the first place. And this is a product (NG + 800/900) we've paid a rather hefty amount for, too (IMHO). Programming is my profession-- It's not that I don't appreciate your effort and understand the difficulty of fixing bugs you can't consistenly reproduce, but I sure wish our customers reacted the same way yours do!In a somewhat related note, I find it annoying that your support page pretends as if the "realism" setting is the ultimate solution to the radio lockup when it has be reported in these forums time and again that it is not. I have no problem with you suggesting the realism setting change, but to claim outright "Any setting other than full will prevent this problem from effecting your flight." when you should know otherwise kind of grates on me.Finally, for my most misplaced complaint: Regarding the AVSim forums... I guess I can understand banning certain email systems (though I found this rather inconventient) but I sure wish it would suggest email systems it will allow rather than forcing you to guess new ones by trial and error.k, rant over.peace.

You know, sometimes to enjoy the priviledge of offering criticism, you need to be careful to actually abide by the rules offered by the one offering the hospitality as well.As such, even though I'd be inclined to do so, I am not going to delete your post, but would really like you to read our forum rules (it has been mentioned a thousand times) that specify that you need to sign your REAL NAME when you post something in our forum.Thanks,

>You know, sometimes to enjoy the priviledge of offering>criticism, you need to be careful to actually abide by the>rules offered by the one offering the hospitality as well.I thought I earned that priviledge when I paid you $60 ;)>As such, even though I'd be inclined to do so, I am not going>to delete your post, but would really like you to read our>forum rules (it has been mentioned a thousand times) that>specify that you need to sign your REAL NAME when you post>something in our forum.I am sorry for not following the rules. I have included my real name. And aside from my fascination with the overwhelmingly positive posts, I was honestly trying to be as constructive as possible. Please don't interpret my post as useless denigration.peace.Steve Kurth

Hi guysI know this may sound like a dumb question, but I am in the lucky position (so far) not to have any of the problems associated with the interim fix.Is it recommended that all users install it, or just the users effected?My instinct is to leave it alone i.e if it ain't broken, don't fix it.CheersGraham Laing