Today I started a flight from Lima SPIM to Madrid LEMD with NOTAMS checked as I had to pass over the Andes after the take off.Although Level-d 767 is climbing normally to altitude FL340 RC gives me a message for incorrect altitude and keeps giving me the same message every 15 seconds.When RC askes me to contact Lima control and Otto responds the actual altitude that ke is giving is wrong and unclear something between 5 and 6, I cannot really understand.It is clear though that RC has totally incorrect perception about my altitude.What is going wrong?Is FSUIPC giving information about the aircraft's altitude to RC?The only thing I changed in my system during the last days was the new version of FSUIPC.

First, you must use the altitude ATC commands, not what the FMC commands.Second Otto can do comms for you in that model but not control the aircraft via the MCP/AP.Third in that area you must use the transition altitude for that area. You can preview you departure and arrival transition altitude on the controller tab of RC preflight after your flight plan is loaded.In the RC manual read the section on transition altitude and how to set the altimeter when climbing above and descending below it. If RC commands an altitude in feet then your altimeter must be set to local pressure as that means you are below the transition altitude. If RC give it to you as an FL it must be set to a standard pressure of 29.92in or 1013mb. Do not use the FS 'B' key as that does not work outside of FAA areas. If you hear your copilot (in any RC mode) state altimeter check it is a reminder to switch altimeter modes to standard or local.In the similar 737 MCP and FMC in a climb the MCP altitude sets the limit as it does in a descent. When you reach a limit when ATC changes to an altitude outside of this limit just adjust the MCP altitude and push it or do a LVLCHG to start the aircraft to the next limit. This is handy for ATC commanded step climbs. In addition on your panel you may find a STD/LCL switch at your baro control. On the 737 you If I recall correctly push (click) the center knob to toggle standard or set pressure.Try doing a flight commanding the aircraft and comms yourself to allow a slower pace for checking things out. You handling the comms without pilot autoreply alllows you to request a repeat if you do not undertstand it. The best test is to do this without running a weather add-on to insure the correct pressure is being reported when you are below the transition level. By handling the comms yourself allows you also to delay an ack slightly to allow the aircraft to start changing its altitude. Don't delay an ack however if getting near a checkpoint as RC will not catch your flyby if it is waiting for an ack.http://forum.simflight.com/topic/66139-updated-modules/ is the latest FSUIPC modules interim and full versions. Today it is 3.998t or 4.761. If everything was OK before then check this forum to see if other FSUIPC users are having tech problems.

I reistalled FSX and all add-ons and now everything is working Ok.This was a mulfunction of RC that had nothing to do with my flying.

Recheck your versions of FSUIPC and makerwys.exe to insure you did not lose the latest versions. If your altitude problem occurs with an FSUIPC update then on their forum they need to be notified.

They sent me back to RC forum.Anyway, everything works fine now.

They sent me back to RC forum.Anyway, everything works fine now.

If you mean me by "they", you are wrong. I asked you for details, you provided them, and I gave you the most plausible explanation asking you to confirm one other fact. Which request you ignored and instead reinstalled FSX and all your add-ons.There has never been a version of FSUIPC, ever, which has lied to applications like RC about the aircraft's altitude, which was the suspicion you appeared to have which apparently led you to my support forum in the first place.RegardsPete

I mean that from RC they told me to check FSUIPC if any problems are reported.You have made clear that FSUIPC is not responsible so the next step is to go back to RC forum.That;s what I mean by "they sent",of course you didn't tell me to go back and you provided all the help needed, I said "they sent" in order to express what was the next step to do, I never wanted to insult you, I apologise, you are doing a great job and please keep up on doing it with the same enthusiasm and professionalism.

Hi been using RC for a week now, but all of a sudden "Keep gettng -Watch your altitude warnings"So when I check what RC say's is the pressure and compare it to what ASv6.5 say's it is, there is a difference.Question what reference is RC using for the pressure?This is occuring with ASKy and RC on a network using WideFS reg Version and Reg version of FSUIPCJohnT

Edited February 8, 201214 yr by j1o2h3n4

RC reads the pressure from FS which is controlled by AS65. In what stage of flight are you getting the errors. Is it ATIS that is off when approaching the airport outside of 50 nm.? Be sure in AS65 that the global weather switch is in auto. Is your departure ATIS correct? In AS65 after your weather is loaded - I always use an archive to avoid real time changes and the archive I grab is the flight time for departure. I do not use system time but the time set for the flight. now in AS65 load and process the .pln file (make sure the convert .pln option is off) and then print all. This way you'll get from the weather snapshot METARS and winds aloft (with temperatures) along your route at major points in the printed AS navlog. AS will dynamically control your pressure as you fly and at your descent you'll get a pressure slightly different as you progress toward destination. In your last stages of landing your last altimeter reading should match the destination METAR as delivered by the controller and ATIS.Don't use the 'B' key in FS to set altimeter pressure as it can be incorrect when not in FAA territories. AS65 and RC both use FSUIPC for communications with FS so be sure these these and widefs are updated just to be sure after any installation that uses them. Links at the forum top for FSUIPC.Have you read the section on transition levels and transition altitudes in the manual? If RC commands an altitude in feet, set the altimeter to local pressure usually delivered by the controller at appropriate times. If RC commands you to go to a flight level (FL) then be sure your altimeter is set to the standard pressure of 29.92 inches or 1013 mb.AS65 does not know about flight level standard pressure. It always delivers QNH or local pressures at the surface if you are using AS's flight watch (which can also interfere with RC's audio).Depending on where you are FS will display the wrong pressure setting as it only shows QNH.FSUIPC is probably not the culprit as stated by Pete Dowson as that never has been a problem. Since you are using WideFS, is there anything that is slowing down communications between the client and FS host?Have you installed or reinstalled any add-on in the last few days? What has changed. Always test with a default aircraft to insure it is not a gauge problem.If the problem persists please submit a log as detailed in the forum top.In addition it is a good idea unless you are very near a checkpoint to delay acking an altitude change until the aircraft is starting the climb without any dips as some do.

Hi Ron,Thanks for the explicit reply.As it turns out the problem is due to several factors, some of which you mention above.The main one, though, we discovered , was, wrong installation AS65. It seems that over the years of multiple installations of FS, due to upgrading Computers.The mate and I, had got crossed wires, and AS65 was installed on the same machine as FS. But as we could start AS from the client and the AS windows opened up on the client, we didn't spot the error."...............climb without any dips as some do" .Yes, get this using ATR72/Dash when switching AP on and using IAS if plane speed is below IAS setting."Don't use the 'B' key in FS to set altimeter pressure as it can be incorrect when not in FAA territories" Can you explain this a little bit more - do you mean that if the transition level for where you are is e.g 6000ft and you press "B" you will not automatically get 29.92 but from AS65 the actual Baro pressure at 6000ft? If so then I get it. Most payware comes with a baro button press to goto STD. This is a problem with Quality sim 757 in that it is virtually impossible to see the Baro pressure.In answer to your first query, memory say's it was the decent stage for most of the time, ie more than 50 miles to destination. One thing I couldn't understand was, a large discrepency between, what alt- shift Z/FS was showing and the planes Altimeter. This after pressing B.I think we are getting there, but will probably be back for more help - particularly regarding how you do it.Just a quickie to say how impressed I am with this software in comparison to the other offering in this genre.Many Regards and thanks .JohnT

The 'B' key in FS is hard coded for a transition altitude of 18000 feet. If your TA is at 6,000 feet (in RC you can see what it is on the controller page preflight) and you are at 7,000 feet the 'B' will incorrectly set your altimeter to QNH, not standard pressure. Above 18,000 feet it will set standard pressure.The FS alt-shift-z command I think always shows QNH regardless of your altitude AFAIK.At 50 nm out RC should be reading the current pressure at your destination if you are getting ATIS. If ATIS is not present you'll get it from a flight information service (FFS in the US). Page 46 in the manual. Listen carefully to the report to get where the report is for.Regarding the quality wings 757, you might try making a pop-up window for the standby altimeter and set your pressure there. On the PMDG there is a restricted larger panel view where the PFD is larger and you can see the pressure there since the baro control area on the main panel is still accessible.I use FS Panel Studio to edit panels and create additional panel views if the number is available for another window.

Edited February 9, 201214 yr by ronzie