f16jockey

Thanks again. Works great. At least after I learned how a null terminated string is handled in LUA :oops: . Wim

Thanks, sure can wait. Still enough work on the global script. Specific ones can wait. Wim

Hmm, I think the aircraft title will do as well. Guess I'll need to go through the aircraft.cfg files to make them consistent in a way. Thanks, Wim

Hi, still working on the Saitek LED stuff... For some payware it's (for example) not enough to read 0x0810 to know the Autopilot Master status. One needs to read an Lvar, which (of course) is different for different add-ons. I'm trying to avoid writing X times a (slightly) different script for each add-on. A more elegant way (IMHO) would be to write a unique script, which decides what Lvar to read, based on the active profile. Hence my question : is there a way of "reading" what FSUIPC profile is currently active ? Wim

I used the address I found in FS-Interrogate, and obviously that's not the correct one. That's a pity, as FS-interrogate is easier for finding things. I'll stick to the PDF in the future. Thanks, Wim

I'm having a go at programming the LEDs on my X52P. With already some success BTW. In that context, I came accross the above variable (in FS-Interrogate). But whatever aircraft I select, the variable remains stuck at 0 (I used FSUIPC Logging to check). Not that it's such a big drama, but I'd like to have the gear led "off" rather than "green" for a fixed gear aircraft. Any ideas ? Wim