John Dowson

All offsets are documented in the FSUIPC7 Offsets Status document. If nothing was printed in the console, then you forgot to check the Normal log file checkbox - you have to select were you want the logging to go. Never going to happen, sorry. That would be far too much work for little benefit for a very few people. I am struggling to get new functionality in as it is due to the amount of time I am spending on support and just keeping up with MSFS and P3D releases. There are far more useful things for the majority of folks I am planning to implement at some point already. John

In the same places as always - either in the Download Links => Updated Modules page of this from, or from www.fsuipc.com.

Ok, that makes sense. Thanks for the update. John

👍

Files?

In the next release, FSUIPC7 will auto-start luas when FSUIPC7 is started/restarted when MSFS is running and has an aircraft loaded (i.e. it is out of the main menu system). You can also try the attached beta version (7.3.11a) that has this implemented. In this version, I have also delayed the starting of other threads, including WideServer, until and aircraft is loaded and ready-to-fly. John FSUIPC7.exe

But how is the yoke assigned in P3Dv5/FSUIPC6? Presumably in P3D, no? As I have said, it was previously possible to calibrate axes when assigned in MSFS or when assigned in FSUIPC to 'Send to FS as normal axis', but since the release of SU10 this is no longer possible. With P3D/FSUIPC6, this is still possible. John

Are you sure? The yoke isn't even recognised, and this will/should be the same in FSUIPC6... Maybe show me your FSUIPC6.log and FSUIPC6.ini files so that I can check...

Yes I know, that is what I said ('You do have one controller assigned that is now missing:'). Yes, I know, This yoke is not recognised or supported by FSUIPC. It is not an HID joystick type device. John

There is still a minor issue (now corrected, will be released in the next update) that prevents the WASM/WAPI being activated in certain situations. To correct for this, make sure that you have the WAPI explicitly enabled in your FSUIPC7.ini, i.e. make sure you it contains the following section - add or update as needed: John

You ran the installer from within the zip file: Running in folder 'C:\Users\blaur\AppData\Local\Temp\Rar$EXa23188.45475\Install_FSUIPC7' You should not do this - extract the files from the zip folder first before running the installer. Do that and try again. John

These are periods defined by the MSFS SIMCONNECT_PERIOD enumeration type: I know nothing more than that. Yes, you will need a delay, before you can read the value. However, as I said, rather than inserting a delay you should use the idiom: ipc.createLvar("AE_FD", 0) -- create Lvar while (ipc.getLvarId("AE_FD") == nil) do ipc.sleep(50) end -- wait for lvar to be received i.e. wait for the lvar to be available after creation. It is also better to use the event.Lvar function to perform actions when lvar values change rather that changing the value and then waiting for the updated value to be received back - or you could just assume that the value had been updated (depending in the use-case). John

Options->GPS Out... Try looking at the User manual.... John

The logging of IPC read/writes only logs for external applications (IPC = Inter Process Control). To log offsets, use FSUIPC's offset logging capabilities (Log->Offsets..) - see the User guide for details. No, I do not provide support via Discord. I spend a lot of time on support as it is - I don't want to open another support channel - I would never get anything else done....! John

How are you assigning? If you want to calibrate, then you have to assign to 'Send direct to FSUIPC Calibration'. If assigning with 'Send to FS as normal axis', then you cannot calibrate - you have to use FSUIPC's axis scaling functionality. To do this, you need to add ',*-1' to the axis assignment line in your FSUIPC7.ini. Either do this when FSUIPC7 is not running, ot if running make the changes when the axis assignment panel is open and once saved click the Reload button. See the Advanced user guide on axis scaling for more details. John

For the QNH, see offset 0x34A0 (Sea Level Pressure), or maybe its the Kohlsman setting you want at offset 0x0330 or maybe 0x0332? Take a look at the offset status document for a description of those offsets. Cheers, John

Then see that FAQ entry I referenced. Are you aware that, by default, when you start FSUIPC7 it displays the splash screen and then sits in your system tray? To open the main window, try Alt+F. I suggest you try reading the provided documentation if you do not know how FSUIPC7 operates - it is different to other versions of FSUIPC as it is a separate application/executable rather than an embedded dll. You should at least peruse the User guide. It will be in your FSUIPC7 installation folder. If you cannot see it, it will be due to your windows explorer settings. See the appendix in the Installation and registration guide on how to change this. John

For auto-start issues, please see What do you mean by this? Just saying 'does not work' does not really help me.... What happens when you double-click the FSUIPC7.exe in Windows explorer? Do you see the FSUIPC7 splash screen or a windows message? Is the FSUIPC7.log file updated? If so, show me that. Otherwise, show me your InstallFSUIPC7.log file. John

The license has been updated - sorry for the delay. John

Your device GUIDs have changed - I have corrected for this in the attached FSUIPC7.ini if you could try this. Your log/ini files also shows a missing controller (LEFT VPC Stick WarBRD), but there are no assignments to this controller. John FSUIPC7.ini

Yes, that is all correct. However, the times/delays you see are because you are using the default lvar refresh rate of 6Hz. You can speed things up by changing this to VisualFrame or Frame, using the WASM ini parameter LvarUpdateFrequency. See the Advanced User guide (WASM section) for details. John

That would be the Rudder Position offset, that the script already uses. There are other offsets available with other rudder stats, for example RUDDER DEFLECTION PCT at offset 0x0BBC. Take a look at the FSUIPC7 Offset Status document - this tells you what information/simvars are held in FSUIPC offsets. You can also add any other simvar defined in the MSFS SDK, any also any available lvar. Check the MSFS documentation for available simvars. Thanks, you too! John

This always works. BUT, it depend when you add this - if you do this with FSUIPC running, it will not be picked-up and will be overwritten when you exit or open an assignments panel. If you are configuring axes with 'Direct to FSUIPC Calibration' then you should reverse in the calibration panels. If not, add the ',*-1' to the axis assignment line. Any further issues, please attach your FSUIPC ini and log files. Would also be helpful if you had specified which version of FSUIPC and which FS you are using.... John

Yes, that is correct. This is because it is a client-server request. The requests are sent to the server and the direct response is 'request sent ok' (hopefully), then the actual update/changes are received once the server has processed the request and any response has been received in the client (FSUIPC7) from the server (MSFS) - and in another thread. No problem - a necessary feature with MSFS really.... Cheers, John

By the way, you also don't actually need to reload the WASM if using calculator code to update the lvar. You only need to do this if using the specific ipc lvar functions. Calculator code will be executed regardless of whether the lvars are known to FSUIPC or not. So your example could also be re-written as follows: ipc.execCalcCode(" 0 (>L:AE_FD, Bool) ") -- create Lvar ipc.execCalcCode(" 1 (>L:AE_FD, Bool) ") -- update Lvar ipc.reloadWASM() -- make Lvar known ipc.sleep(200) -- wait for updated lvar list to be received: -- can also use while loop and wait for the lvarId to be none-nil fd_val = ipc.readLvar("L:AE_FD") if fd_val == 1 then ipc.control(66288) -- toggle FD end John