John Dowson

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

I have added the steering tiller axis to keys Numpad7 and Numpad9 in the attached script. These work slightly different from the other keys as there is no simvar for the steering tiller position - what this means is that when you press one of those key, the initial start value would be 0 (i.e. centered). Try it an see if that helps. Maybe I should add a call to set the steering tiller axis back to 0 (centered) on key release... Numpad5 will also centre the steering axis. I have also added a max limit on the delta value, currently set at 512. Just the one limit for all the axis at the moment - you can update if you want separate limits for each axis. I checked the centering (Numpad5) in the PMDG 737 and that seems to work as expected. I don't understand how that is not working for you in the Twin Otter - is it working in other aircraft? John nmpadFltCntrls.lua

Your log and ini files show that you have never had the FFB yoke assigned in FSUIPC, so your issue is not related to an MSFS or FSUIPC update - unless you had previously assigned in MSFS and calibrated in FSUIPC7 (which is no longer possible at the moment). You do have one controller assigned that is now missing: Your FFB yoke is not supported by FSUIPC, you will have to assign in the sim. Previously it was also possible to calibrate in FSUIPC7 when assigned in the sim, but since SU10 this is no longer possible, sorry. John

The problem is here: The lvar will be updated, but if you read the lvar directly after the update, you will be reading the old value as the new value will not yet have been received back from the WASM. The lvar gets updated in the FS, but lvar value updates are only sent back to FSUIPC7 6 times per second (by default, can be changed via a WASM ini parameter). So you would need to wait for a short period after updating an lvar before reading, i,e, ipc.execCalcCode(" 1 (>L:AE_FD, Bool) ") -- update Lvar ipc.sleep(200) -- wait for lvar update to be received fd_val = ipc.readLvar("L:AE_FD") Maybe, but better to use the provided function to create the lvar, and then the new lvar will automatically be pushed to any WASM/WAPI client. So, try: ipc.createLvar("AE_FD", 0) -- create Lvar while (ipc.getLvarId("AE_FD") == nil) do ipc.sleep(50) end -- wait for lvar to be received ipc.execCalcCode("1 (>L:AE_FD, Bool)") -- update Lvar ipc.sleep(200) -- wait for updated value to be received fd_val = ipc.readLvar("L:AE_FD") if fd_val == 1 then ipc.control(66288) -- toggle FD end John

That message signifies WideServer is active and waiting for connections (in FSUIPC7). If you start WideClient, it should connect one you have an aircraft loaded and ready-to-fly. If its not connecting, see the WideFS User guide section Configure your Network IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS! And also consult the Technical guide for further issues. If your server and client PCs are in the same workgroup and it still won't connect, try temporarily disabling all firewalls (i.e. client PC, server PC, router) to see if that helps, and if so the issue will be a firewall problem that you need to resolve. Otherwise, if all else fails, show me your log and ini files - FSUIPC7.log, FSUIPC7.ini, WideServer.log, WideClient.log and WideClient.ini. Do not post the files without reading the manuals and trying what is suggested there first. John

👍 Maybe you could add the Rotor Brake parameters you used so that if others come across this post they can find them rather than having to calculate them. I can also create a preset for these and submit to the MF HubHop resource for others to use. John

No - line continuation characters are not supported, sorry. John

And you could see the FFB yoke axis in FSUIPC previously? There really should be no change in controller/axes recognition as nothing has changed in this area - FSUIPC reads hardware devices directly and not via the sim. So I think something else must be going on. Can you show me/attach your FSUIPC7.ini and FSUIPC7.log files please. John

Since the release of SU10 / SDK 0.9.3.0, there are issues with masking events for calibration purposes. I am still investigating these issues and will file a bug report with Asobo, but for the time being I have had to remove the ability to calibrate an axis if not assigned with 'Send direct to FSUIPC Calibration'. Therefore if you want to use FSUIPC's calibration facilities, you must assign in this manner. Note you can still scale (and reverse) an axis assigned with 'Send to FS as normal axis', but such assigned axis will no longer be calibrated by FSUIPC. John

You only need that to restart the lua script if you change it, i.e. while tuning it. Once you have set it up to your liking, no need to restart it again so you can remove that assignment. That is what your 'End' key assignment is for - to restart the script when you change it... I don't understand this either - this is using the same controls that move the elevator/aileron/rudder, so if the other keys are working, so should this. Did you try in the C172 - it works in that aircraft here. I can't see how any if this relates to reversers - that only affects thrust/throttle. Ground steering for airliners is done in combination with the steering tiller axis, and the rudder only takes affect as the speed increases. You could maybe use the '7' and '9' keys to control the steering tiller. There is also a new nosewheel steering control, but unfortunately this is not yet available for 3rd party apps as it isn't exposed by the SDK. I don't have the PMDG 738m but I have the 737-700 - I can take a look at this, but it will be over the weekend. I can also check the Num5/centering in this aircraft. John

No...that will start the script when you press the End key, and then kill it and start it again when you release. Remove the control sent on release - you don't need that. And you only need this to restart the script to reload the changes made when tuning. If always using the script, it should be started automatically using the FSUIPC7.ini [Auto] section. That is strange as the other keys are working. Also no point keeping it pressed as the '5' key is only assigned to a press, and not a repeat press. Is anything centered (rudder, elevator or ailerons)? You can add trim centering as well if that is the issue. Maybe also check with a default aircraft, e.g. the C172. John

You need to provide more information - what aircraft? What switches? Can you show me your FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & Keys and Events activated, load an aircraft, press one or two of your assigned switches (that are not working) and then exit FSUIPC7 before attaching the log file. John

I will provide a new license later this evening or tomorrow.