Thanks very much for this-I added those lines to my FSUIPC6.ini file and the values work perfectly. Attention Your ePaper is waiting for publication By publishing your document, the content will be optimally indexed by Google via AI and sorted into the right category for over 500 million ePaper readers on YUMPU. I also adjusted my PollInterval and Button Repeat as follows:Ģ8=CR(+0,13)0,15,C70032,16384. I recommend looking at the 'FSUIPC for Advanced Users' for more details. Here's some examples using the event codes for the PMDG 737 and the Boeing Thrustmaster throttle quadrant - note your quadrant may be assigned a different joystick number then mine. I will consider this request again once I have done this.You can do these compound switches in FSUIPC but you need to configure them directly in the INI. I am planning on going through the MSFS documentation on available simvars (and events) this week (hopefully!), to see what new simvars and events are available.

The same or a similar lvar may also be available in the SR22, although I haven't checked this. If the lvar is writeable, you can then also write to the offset to switch the standby battery on and off. You could add this lvar to a free FSUIPC offset (using the lvarst-to-offsets functionality) and read the state of the standby battery from that. For example, in the C172 there is a lvar XMLVAR_BatterySTBY_SwitchState. However, there may be an alternative solution.

Not sure what to do about this at the moment - I will have a think about this. This applies to all aircraft, so it is not an ideal solution, but there is no way that I know of to determine the actual number of pumps available, and for this update there would be no way to know the number of batteries available, and so there is a similar issue. To get around this, I added a new ini parameter NumberOfPumps that controls how many indices of these simvars are requested.

This was an issue when I recently added offsets for FUELSYSTEM PUMP ACTIVE and FUELSYSTEM PUMP SWITCH for indices up to 16. The problem is that if I request the ELECTRICAL MASTER BATTERY simvar for indices > 1 and only one battery is available, this will not produce an error but will flood the MSFS logging console with error messages, making the logging console impossible to use. However, I could add a new bitwise offset that would hold and change the state of the different indexed batteries. I am reluctant to change the functionality of the existing master battery offset, 0x3102.

Fsuipc master battery alternator set