Hi JD,Just thought you would like to know that 3.52 version is also causingprobems. Had to declare a medical emergency and return to ABQ. I did get heading assignment but then otto stopped responding to ATC andeventually the menu dissappeared. The only item left in the menu wasRwy 8 info. Also had control problems with the aircraft again. Steepturn to left when flying with FMC, overspeed, would not hold headingagain. Going back to 3.50 as I had 4 consecutive flights with no problems. Cheers

doubt it is 3.52were there pending questions that you needed to answer? there is a log of dialog after you declare an emergencyjd

Hi JD, yes there were times when Otto was told to contact so & so buthe never responded. I went to respond but the menu did not give that option. I was told to fly direct to ABQ and resume own nav. When I got near ABQ is when the menu ceased to function but it did give theinfo for RWY 8. I finally flew the approach and landed but nothing changed in the window as it still showed the RWY 8 info. lolGreat program. Works best with FSUIPC3.50. At least for me.

i think as soon as declare an emergency, otto stops handling comms. i could be complete wrong. i didn't see that in the code, but i only looked for about 90 seconds.this was enroute?did you ask for the closest? or a specific airport?it's possible that as neared abq you were still too high, so i kept you descending past abq, and would eventually have vectored (perfectly) back to kabq for a landing.there was a big enhancement with ai in 3.51, but 3.51 introduced a problem with course calculations when there were heavy crosswinds enroute, thus 3.52. then a problem with saving .rcd/.flt/.wx was introduced somewhere a long the way, and 3.521 seems to be the optimum version. we'll be flying with 3.521 going forward and find anything, if there is anything to find.jd

When the emergency was declared Otto still responded after I made thekey stroke. After Otto said the amount of fuel on board I looked forthe souls on board and could not find it. I requested to return tomy DP airport which was ABQ. AFter declaring the emergency and told to fly heading 135 is when the aircraft started behaving eratic. Trying to think here. I decended to FL180 and was instructed todecend to 9900, the aircraft would not decend in LV change and had todecend using VS mode. I arrived way to high and declared a MAP andthat is when the menu dissappeared. I reflew the flight with FSUIPC3.50 and the fligth went very nicely. 3.52 took care of the crosswindheading problems but something still seems amiss somewhere. Cheers

Hi there,If you declared a MAP I think RC waits for you to start climbing before it will do anything else (first thing expected of someone declaring a MAP which normally happens on final). If you kept descending or levelled off after declaring the MAP that would explain why you heard no more and the menus were blank.The number of souls on board is set preflight in the options so will mot appear on the menus.I'm a little confused about the control of the plane.If the plane has level change and vs mode then Otto can't fly it since it is not using the standard FS autopilot. Which plane is it?Presumably therefore you have Otto on comms and the plane's FMC/autopilot combination is flying it. Did you disengage LNAV and engage heading mode to take you back to ABQ or did you reprograsm the FMC to fly direct ABQ?All the best,John

After declaring emergency and requesting ABQ ATC gave me a heading of135, I then used heading mode and when on course I programmed the FMC. ATC gave me vectors to RWY 8 but I was too high to even attemptan approach so I requested a MAP and that was the end of any ATC contact. Since I have gone back to FSUIPC 3.50 I have not had any problems with A/C acting up or RC acting up. Before installing RC4 I upgraded to 3.51 and had problems with that and 3.52. Don't know why. Does Otto turn over comms after declaringa emergency? I can't recall if that happened or not. I know he didreport fuel onboard.

Hi there,I can't remember if Otto hands back comms or not when declaring an emergency to be honest but it wouldn't affect the menus.As I said the most likely reason for the menus going blank and no more atc communication would be a failure to climb after declaring a missed approach.I would encourage you to persevere with FSUIPC 3.52 - it does contain some important changes as far as we are concerned and RC is working fine with it.As far as the aircraft acting up; out of interest, which aircraft is it? Not directly related to RC but you may well find folks here flying the same plane who can say if they are having problems like this with fsuipc 3.52All the best,John

Sorry for the long delay John.The aircraft was PMDG 737. I did go back to 3.50 and have not had any problems again. I now have 3.53 and so far so good. Can't explain that problem but it did happen on 2 different flights. Allis hunky dory right now.CheersSkyhog