Hi,I have installed the temp update. I haven't done any flights over 2hrs since but the radio seems to work ok on flights up to 1hr. I have had a couple of instances, since the update, of radio lockup whilst on the ground, requesting taxi clerance etc. I had, also, experienced engine failure on takoff but this seems to be cured now. Many thanks.regards,Ian.__

I had followed PMDG's suggestion before of using "CTRL + A" to turn Avionics off/on to reset the radios, but this didn't work. I figured someone else's suggestion of "SHIFT + M" was just their own mapping of the same thing.... but I finally tried this and it reset my radios just fine. So the radios still lock on me, but I can reset them... not a big deal.I also think I figured out what was causing the A/P disengage when switching modes on my controller. It seems that when the trim is not set right to keep the plane in somewhat level flight on its own, it causes the A/P to disengage. Actually, as long as the trim value stays the same the A/P will work just fine, but when it is changed and the value isn't one the A/P likes, it craps out. So, I finally figured out that when entering a new mode on the controller, all the axis reasserted themselves, thus when my trim wheel was not set right it killed the A/P. The problem goes away when I adjust the trim correctly.yay.

Always nice to find solutions to your problems even when in the form of "work-arounds" until a real solution is provided. Glad to hear you managed to solve your problems Steve!

The avionics turning off on their own is a problem caused by some miswired electric system stuff. This will be fixed as part of the greater fix we're working on to rewire the entire electrics system.As for the A/P - if you have the A/P engaged, you should NEVER touch the trim, as it WILL disconnect the A/P and cause you to go into CWS mode.

Hi Ian,Have you tried pressing SHIFT-M? Works for me as a temporary solution and read someone else solved the problem that way too.

>As for the A/P - if you have the A/P engaged, you should NEVER>touch the trim, as it WILL disconnect the A/P and cause you to>go into CWS mode.Right, but you see I WASN'T touching the physical trim wheel. As I said, I'm pretty sure what happens is that when I switch modes on the controller, all the axis (x, y, throttle, rudders, trim) momentarily go offline then re-report once in the new mode. If the trim is set pretty close to properly, A/P continues to function normally. However, if my trim is too high or low, the process of switching modes and the assosiated re-assertion of the axis (at least as my theory goes) does cause the A/P to disengage.I'm not saying this is a bug. It seems to just be a side-effect of using the x45 controller. I was simply reporting what I found in the case that someone else runs into the same situation (or in case some of you thought I was nuts because I said my mode switch was disengaging the A/P)peace.

Hi Richard,I haven't tried the shift-M yet but I ceartainly will asap.many thanks,regards,Ian.__

Hi PMDG,thanks for the update, it solves the problem with the engine failure at v1.greetingsMarkus D LSFB

oh, why couldn't I leave well enough alone?After finding SHIFT+M reset my radios, I held off on installing the updated (which I didn't oringially think was supposed to address the radio issue). However, today I finally did the update. Now I've got worse problems. Please help!A/T switch: It doesn't work. It doesn't matter if I click it, use the hotkey I have mapped for it, try in 2D or VC.... it doesn't budge. If I hold it down, the idicator illuminates in the PFD, but only as long as I hold it down.... it doesn't actually control the throttle while holding down the swith, either. Later, I even tried setting AutoThrottleArm=True in my default flight file... when I started the flight it still came up off.When I first discovered this problem, I decided to keep on flying by manually throttling... and it was about halfway through the flight that I noticed problem #2-- the center tank fuel pumps weren't working... fuel was being drawn only off my wing tanks. Further, it didn't seem to matter what I did with the fuel pump switches-- whether I turned them all on or all off or anywhere in between, fuel would continue to draw off the wing tanks and never the center tank. I ended up running out of fuel in the wings and having engine shutdown just after I pulled off the runway after landing at KSEA. Classic!Anything obvious you can think that I might have done wrong or that would fix this situation easily?Anyway.... having found SHIFT+M reset my radios, I had been satisified before the update... what's the best way to get back to that point? Uninstall PMDG entirely and then reinstall the original file?... oh, but my radios haven't failed since the update, though...peace.

Hi Richard,Have tried SHIFT-M and it works OK,Many thanks for the tip.regards,Ian.

Glad to hear that Ian!Cheers,

Hi,I've got both 737 packages and have had a problem with CTD's even when I'm using other aircraft. I have uninstalled all the PMDG stuff and no longer have the problem. I've tried all the suggested solutions including reinstall of fs9 to no avail.Does the temp update address CTD's? I sure would like to use the 737's that I paid good money for!Thanks,Gaylord Berry

Must be something else than PMDG. I don't have any CTD's and I have both 737NG and the 1900D.

Haven't had a CTD since the temp update....Best RegardsBoone,[email protected]"Flying a plane is no different from riding a bicycle. It's just a lot harder to put baseball cards in the spokes."

I've temp interim release installed. In my case I get CTD ONLY with PMDG aircraft (737 and 1900D) in a very random way (may be 15-30min flight). This didn't happen before interim release. May be some directx related problem or known nvidia drivers problem ? I'm trying total reinstall now. Other planes no problem at all !Very strange, becouse PMDG aircraft neverd had problems ...CiaoDome