That will be future work Now that the default is set to feet etc it is all working very well. I have not added any of the other flavours yet. The aircraft is the default FSX 737-800 flavour. I then went into the setting on the main panel and set it to feet etc. I realised my error when I started CrgSim and discovered that the Altitude setting above the bar was correct. I have just about pulled all my hair out over this and have checked what FSUIPC is receiving against the values stored in FSX by the local MCP. I have pulled the calculation around all ways in an attempt to correct it. I can not see anywhere in FSUIPC where the value fed to FSX can be manipulated. There is something going on internally methinks. (ft * 3.28084) in the MCP produces that value but when it is fed via FSUIPC to the Sim it produces a value 0xC8. Am I right and FSX is wrong? I very much doubt that.Ī similar thing is occurring with the V/S (50ft shows up as 61ft in FSX). I have checked submitted values all the way up to 40,000 ft and using (val * 3.28084) / 65536) returns very nearly the right numbers but not on the FSX display. The SIM MCP shows 30 for 50ft input and then 91 for 150 (skips 100ft). The utility in FSUIPC shows the correct value being received and stored and validated via FS Interrogate is correct but the FSX MCP shows an entirely different value. The calculation in the MCP is ((height * 65536) / 3.28084) which produces the correct value which is fed to FSUIPC as a uint32. The problem I am having is that the altitude sent to offset 07D4 does not produce the correct value to FSX. The MCP is connected via CAN bus via our own interfaces to FSUIPC.
The module I am having a spot of bother with is the MCP and in particular the Altitude and V/S encoding. The project is a new set of units for the 737NG etc.
0 kommentar(er)
