espenoi

Hi Pete, I have discussed this with Philippe now and we have come to the conclusion that we need a total of 128bits, or 16 bytes. If is possible for you to allocate that much space for us, then that would be great. I understand I need a freeware type license for this. Please contact me at espen@coolsky.no about that. Best regards, Espen

Two bytes should be enough for the altitude. I'm not sure what the 90 indicators are. Maybe Philippe could elaborate on this. Regards, Espen

Hi Pete, I have been working with Philippe for some time now modifying and adding new features to my Fokker 50 panel for him to use in his home cockpit building project. My Fokker 50 panel is a freeware project (http://www.fokker50.com) which I have been working on since FS98. Now, what Philippe and I would like to do is pass the altitude variable in my panel/gauge (local variable) to his external program which deals with all the switches and LEDs in his home cockpit. The reason I have a second separate variable for the altitude is this: If you are in altitude hold mode and you change the FS altitude variable, the aircraft will immediately start climbing/descending. This is not desirable. I want the aircraft to stay on the initial altitude until I have selected a vertical mode (VS or IAS hold). Then the aircraft should start climbing/descending. And if/when I select Altitude Pre-/Select, the aircraft should level off at the new selected altitude. I have never done any coding with FSUIPC before, so I can't really comment on whether this is the best way to do this or not. Best regards, Espen Øijordsbakken