Jump to content
The simFlight Network Forums

Pliskin

new Members
  • Posts

    2
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    France

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Pliskin's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thank you for your answer. The issue regarding the AP Altitude on A320 is here Some other topics are refering to the same issue We can find a few discussions like this on other forums: https://forums.flightsimulator.com/t/a320-fcu-variable-autopilot-altitude-lock-var-vs-displayed-altitude/307093/3 In fact, the A320 FCU altitude 7-segment display is mapped to [AUTOPILOT ALTITUDE LOCK VAR:3] and not to [AUTOPILOT ALTITUDE LOCK VAR] I guess when we push or pull the altitude knob, then the value is copied from [AUTOPILOT ALTITUDE LOCK VAR:3] to [AUTOPILOT ALTITUDE LOCK VAR] I understand a FSUIPC Lua script will not solve the issue by itself. A new offset has to be published in any case. I feel a bit a bad to ask to implement new offsets just because this plane is not working like the others. Is it not too "dirty" to add "official" offsets just for this plane ? I mean, this is not a bug from FSUIPC. The issue is on the A320 by design (and I think there is a legit reason for Asobo to have implemented things like this). Perhaps a better solution would be to add new functions to the lua API in order to allow it to query SimVar by their name directly. Or better, perhaps FSUIPC could give us the possibilitity to publish our own custom offset by providing the name of the SimVar (and mandatory parameters). The case of the battery push button requires a macro, because it depends on 2 SimVars. Anyway, thank you for your answer.
  2. Hi all, I have a few technical questions before buying FSUIPC7 because I'm not sure about what I can acheive from FSUIPC7/LUA scripts regarding the SimConnect Indexed variables. As example, I take the Asobo Airbus A320 . Someone has already reported that Offset 07D4 [AP ALTITUDE VALUE] is not working. He gave up thinking it was a bug. I found that Offset 281C or 3102 [Master Battery Switch] are not working neither. After having looked into Microsoft SDK and SimConnect, I found that the A320 FCU AP Altitude is linked to an indexed SimVar [AUTOPILOT ALTITUDE LOCK VAR:3] It seems that FSUIPC7 is not natively looking at this SimVar. Both A320 Battery Push Buttons are a bit more tricky: For the left battery Push button: First, set SimVar BUS LOOKUP INDEX to value 10 Then the state of the left battery can be read at indexed SimVar BUS CONNECTION ON:6 For the right battery Push button: First, set SimVar BUS LOOKUP INDEX to value 11 Then the state of the right battery can be read at indexed SimVar BUS CONNECTION ON:6 So here are my questions : Q1. Is it possible from FSUIPC7 (I guess with Lua Scripts) to access the Indexed SimVars and map them to a free FSUIPC7 offset ? I know it *was* possible to access Local SimVars with Lua scripts, but I want to be sure that we can query the indexed variables, for instance like this : ipc.writeXXX("A:BUS LOOKUP INDEX", 10) LeftBattery = ipc.readXXX("A:BUS CONNECTION ON:6") ipc.writeXXX("A:BUS LOOKUP INDEX", 11) RightBattery = ipc.readXXX("A:BUS CONNECTION ON:6") Q2. Is it possible from FSUIPC7 to log all SimVars and Indexed SimVars ? (in order to identify which one is changing after a few clicks in the virtual cockpit) Oh god, the BUS LOOKUP UP thing is not going to help with this kind of feature... --- Regarding the Local SimVar, I understand that FSUIPC7 has no way to access them. And in fact, Microsoft SimConnect SDK does not provide a way to do this. The only workaround for now is to create a fake gauge and put the local SimVar in the Client Data Area. Then FSUIPC7 would be able to read/write the Local SimVar through the SimConnect SDK.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.