John Dowson

Yes, intriguing - but I can't see how it can be WideClient itself doing this, as it does nothing at all with displays/windows, unless using the button screen facility, which you are not. Did you check the task bar, as suggested, to see if the WideClient window is still available (i.e. hover over the icon with a mouse) and if it can be brought to the front? Or when WideClient is started, move it to the part if the screen still visible before it connects to FSUIPC7 - if you do this, fo you still see the WideClient main window? ( it is very difficult to see what is actually happening as the image you attached is so small!) Ah, so you are using WideVieW...I would certainly look into this as a cause...can you test again with no trace of this running in either the server or clients? Maybe also see if you can figure out what is creating that window, using either the Task Manager or maybe Process Explorer. John

First, your FSUIPC is version 7.3.11 - the latest version is 7.3.15 - please update. I am not sure what is causing that... is the WideClient still visible/available - i.e. can you see the WideClient window by using the task bar icon? Your WideClient.log file shows that you have one client application running/connected: Could it be that application that is causing this? Could you try without running SPAD to see if that is the cause? Btw, FYI you can also run FSUIPC7 on your client machine - see the Appendix in the Advanced User Guide for details in how to do this. This doesn't provide the exactly same functionality as WideClient, or as running FSUIPC7 on the server machine, but is an alternative solution to using a client PC with MSFS. John

Please see https://appuals.com/nsis-error-error-launching-installer/ ot https://pupuweb.com/solved-fix-nsis-launching-installer-error-windows/ (or google) for this issue. John

Just taken a look at the available lvars and found these lvars for the landing light position switches: L:switch_111_73X - retractable left L:switch_112_73X - retractable right L:switch_113_73X - fixed left L:switch_114_73X - fixed right They hold 0 when the corresponding light is off, 50 when set to pulse, and 100 when on. You can therefore use those to determine the switch positions. You can add those lvars to free FSUIPC offsets using the Lvars-to-offsets facility. Also lvar L:LandingLightOptions holds the landing light configuration, John

Ah, ok. I will enable in the FMS and take a look... Yep, and that would be good, thanks, John,

The current license is still valid. And as you have been using FSUIPC7 since the beginning of October, why are you requesting a new trial license? Surely you must have decided to either use the registered facilities (and therefore purchase a license) by not or not... The trial license is not provided so that it can be continually used, which is why I leave a day or two between the expiry of one license before I generate a new one.

Ok - are the pulse landing lights something you configure for the aircraft in the equipment options in the FMS? If so, then aren't they either always set to pulse or not, whether the lights are on or off, and the only way of changing this is to reconfigure the aircraft (i.e. there is no standard switch or button for this)? I don't think there is a way to access the aircraft configuration/set-up options via the PMDG SDK. But again, this would be a question for PMDG. John

Yes - otherwise you would have the axes assigned in two places, and both would be trying to control the aircraft. You can just delete the assignments in MSFS for those that you want to assign in FSUIPC, but I would recommend you start with an empty profile in MSFS for your controller/device if assigning everything (or almost) in FSUIPC. If you create a new profile for your device/controller in MSFS, it will be empty by default, so start with that. John

I have noticed an issue when using the 'Control to repeat whilst in range' option when sending key press and releases. This results in multiple key downs being continually sent when not needed. This seems to be related to how I handle key repeats - I will look into this. Even though this does not cause issues (these down key presses are ignored), it may be better to send single key presses (i.e. no repeat) but do this on several different ranges. Anyway, try playing around with this technique and see if you can come up with assignments that work for you. John

No! Hitting the clear button will clear the currently displayed assignment, i.e. delete it. You should hit the Ignore Axis button, which will ignore the input from that axis for the remaining time the dialog is open - or until you press the Clr Ignores button. Or you hit the Rescan button, which will again wait for the first axis input to be detected and show that. If you hit the Rescan button and it keeps showing an axis other than you want to assign (or check), then you hit the Ignore Axis button and try again. That is probably because you cleared that assignment. It is the Joy# and Axis# boxes you need to be looking at to determine what axis is detected. That is because they are controlled by the same equipment (your foot pedals) and when you activate the rudder you will also be applying pressure to the toe brakes, and FSUIPC/Windows is seeing the toe brake axis change first. This is entirely normal and is exactly the situation in which you should be using the Ignore Axis button. So, I suggest that you try again, now that you understand whet the Ignore, Clear & Rescan buttons do. Note that this is also described in the User Guide. John

Just tested this by assigning my aileron axis also to drone left/right using the following assignments: Seems to work well. I will do the same for drone forward/back but using the Elevator axis. John

You cannot do this as the Translate Drone ... are not axis controls but standard events (not taking any parameters). Also, as previously stated, these controls (Translate Drone ...) are not available via the SDK for external applications. They do however have default MSFS key bindings - A=left, D=right, S=back, W=forward. You can assign your axis to send these key strokes on the right hand side of the axes assignment dialog using the control Key Press & Release. To send the A key (translate drone left), for example, the parameter would be 65+8 (where 65 is the VK code for the A key, and 8 indicates a normal key press - see pages 18/19 of the Advanced User guide for a list of VK codes). You could either try setting up different ranges to send the same additional key press the further you move the axis, or you could try sending on repeat in an axis range (or a combination of both). Up to 10 distinct axis ranges can be used. If you need further assistance, let me know and I could assign here and show you how they look. John

This is possible. Any simvar can be added to an FSUIPC7 offset for read or read/write using the myOffsets.txt file. See page 34 of the Advanced User guide for details. Once a simvar is held in an offset, that offset can then be used as any other offset, i.e. can be read and written to. John

This issue is very puzzling - FSUIPC behaves the same no matter when it i started. I have also taken a look at the 310 and cannot duplicate this behavior. The log file you attached shows that nothing was seen or sent by FSUIPC during the session, which only lasted just over a minute and a half. I see you are using an ipcReady.lua - what does this contain? Maybe you could show me that. That will be the only thing that is ran, but this also should run when FUIPC is already running when you load an aircraft, or if you start FSUIPC7 with an aircraft already loaded and ready-to-fly. Maybe you could take a short video showing this issue, and how it starts/stops when FSUIPC is ran/exited. Thanks, John Later: are you using the Airbus A310-300 Enhanced add-on?

What version of FSX is this? The latest version of FSX-SE should be 10.0.62615.0 (excluding the latest beta) - can you see if you need to update (but not to the beta!)? You need SimCommect for version 10.0.62607.0 - did you install that one (successfully)? This does look like a simconnect issue. After you have checked if there is an FSX-SE update, can you try re-installing FSUIPC4 and try again. If you get the same issue, please show me the InstallFSUIPC4.log file. John

Did you see anything registered in the Axis assignment page? Sometimes another axis may be detected first - if this happens, just click the Ignore Axis button and try again. If the rudder movement is detected in the calibration page, then it must be assigned somewhere, and if its not assigned in MSFS then it must be assigned in FSUIPC. I need to see a log file showing your issue, and with logging for Axes Controls activated. So, can you please start MSFS/FSUIPC7, load an aircraft and then activate logging for Axes Controls, move your rudder axis through its full range, then exit FSUIPC7 before attaching your FSUIPC7.log and FSUIPC7.ini files. John

The better/easier way to do this in MSFS is to use preset controls. For example. to move the Transponder Mode Selector to the TA/RA position you can assign to the preset PMDG B737 TCAS MODE TA RA. Please see the MF HubHob site (https://hubhop.mobiflight.com/presets/) for a list of available presets. and also the section on using presets in the Advanced User guide (WASM section). These are the available presets for the PMDG TCAS, all of which should be available through FSIOPC7: Offset 0x6596 is a 2-byte offset for LTS_LandingLtFixedSw, so offset 0x6596 will be 1-byte containing the state of the left light, and 0x6597 is 1 byte for that of the right light. You can read it as two bytes, as you seem to be doing, and doing that will give the values you show, For the lights option position switch, you could try reading offset 0x65A0 which is LTS_PositionSw, and has values 0: STEADY 1: OFF 2: STROBE & STEADY Otherwise, I would ask about this on the PMDG support forums. If you do post there, best just to mention the SDK variable names rather than FSUIPC offsets, and refer to the SDK rather than FSUIPC - otherwise they will just refer you back here! John

Can you please attach your FSUIPC7.ini and FSUIPC7.log files, the latter showing this issue (i.e. attached once you have shutdown MSFS and FSUIPC7 still running. I don't know...very strange... Are you running MSFS/FSUIPC7 with standard privileges or with Admin privileges? John

The FSUIPC7 documentation is installed with FSUIPC7, into your Windows Documents folder. There should also be a link to that folder under your FSUIPC7 installation folder. Note that the documentation for presets is in the Advanced User guide, under the WASM section. You don't need to do anything with the code (calculator code). You just assign as normal, but using the checkbox Select for Preset and not Select for FS control. Presets are a mechanism to send calculator code to the FS, and those provided are from the community effort, led by MobiFlight, and available from their HubHop server - see https://hubhop.mobiflight.com/presets/. Please see the Advanced User guide for details on using presets. John

Don't worry - it will (probably) take me a few days before I get a chance to look at this in detail anyway... John

No such version - the latest (and only supported) version is 7.3.15 (maybe a typo?). Auto-connect and auto-start are two distinct things... Auto-start is enabled when you install FSUIPC7, if you opt to install this component - it is installed by default and will only not be installed/enabled if you uncheck the auto-start box during installation. There are many support requests on auto-start, and I have summerized all possible causes and solutions in the following FAQ entry, so please refer to this: Please also see the README.txt file (included in the FSUIPC7 zip file you downloaded), which contains the following: John

Good news! I really wouldn't worry about that - it is only a warning. I also get these for a couple of my devices - it is not an issue. You could try the same procedure using the VID and PID for that device, but it is quite possible they will be added again when you re-connect. John

No, it will remove them - note the minus sign (-) in front of the entry. Double-click on the filename (in Windows Explorer) to run it.

Yes, probably either a registry or driver issue I would suspect... It will be an issue with the device, not FSUIPC. FSUIPC only stores version and installation location data in the registry, and this is removed when you run the uninstaller. You could try cleaning the registry of the device entries. Unplug the device, and uninstall any drivers (if you have manually installed any drivers. Then run the windows registry editor and first take a back-up of your registry and then exit. Then create a text file with extension .reg (e.g. removeZapBox.reg) with the following content: Windows Registry Editor Version 5.00 [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0483&PID_4444] [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0483&PID_4444] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_0483&PID_4444] [-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_0483&PID_4444] That should remove most entries, but you may also want to run regedit again after doing this and search for any entries with vendor/VID of 0483 and a product/PID of 4444 and remove them. Once done, reboot you machine and then re-connect the device, and let Windows install default drivers and then try again. John

You can assign an axis to multiple controls in FSUIPC. However, it is not possible to assign to "Translate Drone Forward" as this event is not exposed by the SDK, and so not available in FSUIPC for assignments. If there is a K event available, it may be possible to create an assign to a preset for this, but I'm not sure without investigating. I can take a look at this tomorrow 9or Monday), but for the time being it may be easier just to assign your Elevator in FSUIPC and assign to "Translate Drone Forward" in MSFS. John