John Dowson

No, nothing like this is planned. However, if SmartCars is calculating this using information from FSUIPC, then it should be possible to do this yourself (either via the SDK or using lua) Really - which version of FSUIPC was this? How can this calculation be picked up from the sim itself? That is correct, as far as I am aware! John

I am looking into providing an WASM module to handle lvars at the moment. I will also add access to the h variables, but at a later stage. John

Sure, You just can't run them both at the same time.

As I say EVERY TIME, if you have an issue and you are using a mod, you should also try the vanilla version. And whenever you report an issue, you should always specify if its with a mod version or the vanilla. And, of course, if something is working in the vanilla A320Neo but not the mod version, then you need to report to the mod developers. John

Hi Fragtality, which version of FSUIPC and which Flight Sim are you using? Focus handling is different in FSUIPC7 to other versions, as FSUIPC7 is a stand-alone application, so I need to know this before I can take a look. If you can let me know, I will look into this and report back. However, I'm pretty busy at the moment, so it will take me a few days to get around to this.... John

Vanilla A320Neo or a mod version? What has changed since you reported this as working?

Does this wheel use an axis or buttons? If the latter, it could be that the button number are outside of the 0-31 range. If thats the case, you would need to use a lua script (e.g. the hidDemoi.lua script provided in the example lua files). This is quite a way away. I am looking into adding lvars first. Once that is done, I'll see if mouse macros are possible. MobiFlight has a bunch of controls/events for the G3000. Try installing the mobiflighrt WASM module and the MobiFlight/FSUIPC7 event files. See

Is that for all versions, i.e. the vanilla and the mods? There has been no change with this in the latest release (v7.0.4). There has been no MSFS update either, so I'm not sure what could have caused this...

It should be possible to do that in FSUIPC, so should also be possible in Linda. First, you need to add the events to FSUIPC7 using event files. Then, you need to determine what control number FSUIPC7 has assigned to the events. You can do this either by temporarily assigning the event to a button, activate event logging and then press the button to see what event number is logged. You can also work it out by the the number of evt files you have and the index number - the control number will be: 32768 + (256*fileIndex) + controlIndex where fileIndex is the order the file is loaded (starting with 0) and controlIndex is the index number of the event in the file. If you are only using one event file, this is then just: 32768 + controlIndex John

Yes, I see the same behavior. I'm not sure if it was always like this, or if its related to a fix added to v6.0.12 to correct a CTD due to a missing device (XBOX 360 controller) mainly on a surface pro. I'll take a look in more detail when I get time, byt probably not for 2-3 weeks. For the time being, you should follow Roman's advice and re-load you assignments if/when you attach a device after FSUIPC6 has started. John

Hi Hans. Ok, thanks for the update. John

Hi Andrew, it looks like you went into the assignments panel BEFORE the lua file was auto-started. Could you try again please, but don't open the assignments panel until after you see this line in the log (or load an aircraft first): -------------------- Starting everything now ---------------------- If it still doesn't work, show me your new log, and we can try adding some extra logging to the lua script to see whats happening. John

Appreciated, thanks.

Sorry, but what does this mean? When do you get that - when running the installer or FSUIPC? Please try uninstalling and re-installing the VC++ redistributables, as detailed in the README.txt

I don't think they do as the simconnect_text TEXT_TYPE_MENU is broken, so no menu display functionality as of yet.

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