John Dowson

You posted in the FAQ sub-forum, where it explicitly states NOT for support requests. I have moved your post for you. Can you attach your FSUIPC5.ini file please, together with the name of your new macro file (or a listing of the contents of your FSUIPC5 installation folder) and I'll take a look. John

Yes, please do.

We match on the aircraft name received from simconnect, which I presume is the vehicle title, but just take a look in your FSUIPC log file and see whats logged there as the 'user object', e.g. 50547 ### The user object is 'A2A Piper Pa-28-180 Cherokee N3572T'

If it works with one mod and not the other then it looks like a problem with that mod that should be reported to FBW.

It probably is.... Just download and install FSUIPC7. add that key file to your FSUIPC7 installation folder and then run FSUIPC7 (no need to run MSFS) and check you log to see if recognised, then open the button assignments panel and see if the buttons/rotaries are recognised when you activate them. John

As with all other FSUIPC versions, FSUIPC7 will recognise your device if it is a HID joystick type device. If its a non-joystick HID device, it won't be assignable directly, but should be assignable via Lua. I can provide a time-limited license for FSUIPC7 if you would like to try it. John Later: attached is the currently available time-limited license, but this expires on 01/02/2020. I can extend if needed: FSUIPC7.key

Its not possible at the moment. This is the comment I added when this was added: But a user then reported that those (MSFS-only) controls weren't working. Here's the post: I would first try if those events mentioned work in MSFS. If they do, then it should be possible to assign to a key press, which you could also send via an offset if needed (i.e. the general control offset at 3110 with FSUIPC added control 1010 for key press and release). Other than that, you could see if the additional controls provided by MobiFlight can handle FLC/LVLCHG, either in the MobiFlight topic in this forum (see below) or on the MobiFlight channels. For MobiFlight controls, see this topic (there are also other topics on installing and using MobiFlight with FSUIPC7): John

It seems that LVLCHG and FLCH (Flight Level Change) are the same thing but different names (for different aircraft), so maybe try offset 0x0B49. First, check to see if this is populate correctly (i.e. read). This offset is based upon the following simvar (although is not documented as simvar available via SimConnect) - from the MSFS SDK documentation: AUTOPILOT FLIGHT LEVEL CHANGE Boolean, toggles the autopilote Flight Level Change mode I added this as read only but I'm not sure why - I can't remember if I tested this for write access (as this is not defined in the SimConnect documentation). I could maybe try adding write access to this simvar to see if that works. Otherwise, you may have to wait until there is access to lvars to see if its available via that route. John

But I don't use or know about SIOC, and am not sure what LVLCHG is. It would help if you could answer my questions...: ? ?

Is that the Autopilot Flight Level Change? Thats readable at offset 0x0B49 (but nor writeable). What sort of script was that - lua? How does that control the 'LVLCHG' - or doesn't it and you want to add this functionality? John

The syntax is also wrong, so I'm surprised anything is working! The format should be: n=CP(+j2,b2)j,b, .... so those extra P's are redundant... John

This is not correct. It should be: 13=CP(+64,20)P64,12,CM10:13,0 -{Macro LearJet35A: AltInc2}- 14=CP(+64,20)P64,13,CM10:14,0 -{Macro LearJet35A: AltDecr2}- and should be 16=IASDecr2=RX400000fb,3

But this is different from the macro when using the compound assignment (and the macro is using a different mouse rectangle): 13=CP(+64,20)P64,12,CRX4000010c,1 -{Macro LearJet35A: AltInc2}- Can you try with using the same macro, just to be sure? Sorry, forget that - the macros are the same.... If it doesn't work, then it would suggest that the rotary buttons for Altitude and IAS are momentary (i.e. press and release rather then press and hold until next rotary turn/button press), which would be rather strange. You can also try with logging for Buttons & Switches activated. The log should show you what buttons are pressed/released when you turn your rotary, and if your macro is being called (and doing nothing) or not when you press the assigned buttons.

Two posts and no relevant information! Which version? Have you tried looking at www.fsuipc.com or on the Download Links -> Updated modules section of this forum? If you've found the links but can't download for some reason, try temporarily disabling any anti-virus software. John

Could you ask in that forum post - the author does say: But you can remove the hidBravpButtons.lua script (and [Auuto] entry) if you are not using a Bravo.

Yes, that's fine. You just can't run FSUIPC7 and FSX/FSUIPC4 at the same time (as they share a windows class name), but then why would you?!! John

Hi Emile, I won't be adding these offsets for the time being. Apart from there not being any sim vars available for this, when you activate the switches in the UI you don't see the master avionics 1/2 events, but various other events (i.e. ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE & LIGHT_POTENTIOMETER_SET). And thats just for the C172 - may be different in other a/c with dual avionics switches. Probably best to wait for lvar functionality for this, and to see if any lvars are available that hold the state of the 1/2 avionics switches. John

Hi Dave, Thanks for the update. Note also that there is a user contributed lua script for the Bravo lights. See John

Only if the PFD is taking traffic data from the FSUIPC traffic tables, which I doubt. It should only affect any 3rd party programs that rely on FSUIPC for traffic data. It has been reported (on the Asobo forums) that it is also improved for some folks when disabling both live and AI traffic in MSFS. You could also try that, but that would affect the AI traffic on the PFD. John

As Al has stated, this is already documented as not working. This is because that offset was populated from an lvar (was Ok-Lvar in previous versions of the offset status document), and lvars are currently not supported by FSUIPC7. I am currently looking in to providing lvar access in FSUIPC7. John

For the Xbox 360, the device will only be take affect when FSX has the focus, and the left and right trigger buttons act as a single button.

I think that those are the buttons outside of the 32 button limit (0-31). To access those, you currently need to use a Lua sctipt. See John

Nothing changed on your system. I changed the position and font size in a recent release as it didn't show completely on one of my screens, so it probably changed for you then. I'll remove the 'We Are' in the next release.

Yes, probably a better solution!

Current time-limited license attached, although its only valid until 01/02/2021. Drop it into your installation folder - no need to re-install or register. John FSUIPC7.key