John Dowson

FSUIPC just uses the AP Alt Var Set English control/event. No idea why this has changed. Are you using the stick G1000NXi or a mod? Btw, just release FSUIPC7 v7.2.13, which has been recompiled against the latest MSFS SDK for SU7 (0.16.0.0), as well as containing a few bug-fixes + additional offsets/features. John

You need to install the x64 ones, and make sure its the combined package (2015, 2017, 2019 and also now 2022 I think...). And its the IctallFSUIPC7.log file I need to see about the install problems, if you still have them after installing the VC++ restribs. John

One thing you can do to try and track this down is to activate logging for IPC Reads and IPC Writes, using the FSUIPC7 Log menu. Also Open the logging console (from the same menu). When you get that error, take a note of the timestamp of the last message logged, then acknowledge the message and then exit FSUIPC7, and show me your FSUIPC7.log file. John

So you not have your original lua anywhere that you can use? I'm sorry but I cannot help you with this. If you did this before, surely you can do it again, if you can't find your original script. As well as not being sure what you want to achieve, I have never looked into voice commands in lua... Not sure what you mean by this. If you found the information that you needed previously, it will still be there... John

@kingm56 I can maybe add these to some FSUIPC offsets - possibly the same ones if its an either/or situation. I could possibly also make them writeable by triggering the Fuel System Pump Toggle event when written to. I will put this on my list to investigate, hopefully later this week. I have now added these. The 747 has 16 pumps, so I have added 16 indexed variables for each of these, so 32 new offsets in total. I am not sure how useful the FUELSYSTEM PUMP ACTIVE simvar is - seems to be used in the 747 bit not in the 787. I have added it anyway as rad-only. The FUELSYSTEM PUMP SWITCH simvar has been made writable, and will trigger the FUELSYSTEM_PUMP_ON/OFF controls. I have teted this in both the 747 and 787 and you can control all pumps writing to these offsets. The new offsets are (not not all contiguous!) the following, all 1 byte: 0x0B02 FUELSYSTEM PUMP ACTIVE:1 0x0B03 FUELSYSTEM PUMP SWITCH:1 0x0B04 FUELSYSTEM PUMP ACTIVE:2 0x0B05 FUELSYSTEM PUMP SWITCH:2 0x0B06 FUELSYSTEM PUMP ACTIVE:3 0x0B07 FUELSYSTEM PUMP SWITCH:3 0x0B08 FUELSYSTEM PUMP ACTIVE:4 0x0B09 FUELSYSTEM PUMP SWITCH:4 0x0B0A FUELSYSTEM PUMP ACTIVE:5 0x0B0B FUELSYSTEM PUMP SWITCH:5 0x0B10 FUELSYSTEM PUMP ACTIVE:6 0x0B11 FUELSYSTEM PUMP SWITCH:6 0x0B12 FUELSYSTEM PUMP ACTIVE:7 0x0B13 FUELSYSTEM PUMP SWITCH:7 0x0B14 FUELSYSTEM PUMP ACTIVE:8 0x0B15 FUELSYSTEM PUMP SWITCH:8 0x0B16 FUELSYSTEM PUMP ACTIVE:9 0x0B17 FUELSYSTEM PUMP SWITCH:9 0x0AEE FUELSYSTEM PUMP ACTIVE:10 0x0AEF FUELSYSTEM PUMP SWITCH:10 0x0AF0 FUELSYSTEM PUMP ACTIVE:11 0x0AF1 FUELSYSTEM PUMP SWITCH:11 0x0AF2 FUELSYSTEM PUMP ACTIVE:12 0x0AF3 FUELSYSTEM PUMP SWITCH:12 0x0AF6 FUELSYSTEM PUMP ACTIVE:13 0x0AF7 FUELSYSTEM PUMP SWITCH:13 0x0AFA FUELSYSTEM PUMP ACTIVE:14 0x0AFB FUELSYSTEM PUMP SWITCH:14 0x0AFC FUELSYSTEM PUMP ACTIVE:15 0x0AFD FUELSYSTEM PUMP SWITCH:15 0x0AFE FUELSYSTEM PUMP ACTIVE:16 0x0AFF FUELSYSTEM PUMP SWITCH:16 I have also added the new indexed simvar FUELSYSTEM ENGINE PRESSURE to the same offset as the GENERAL ENG FUEL PRESSURE simvar, with units kpa (not psf, as the original simvar for this offset). These new offsets are available in the attached version, v7.2.13e, if you would like to try them. After I release this I will revise the MSFS SDK documentation to document the newly available simvars in the FSUIPC offset documentation. I won't be adding these to offsets unless requested - I will add them to the end of the document as 'available upon request'. Regards, John FSUIPC7.exe

Are you saying that offset 0x3366 is correctly showing the engines on fire, but PM cannot detect it? If so, then, as FSUIPC is working as expected, and you need PM support. Or is the offset not correctly showing which engines are currently on fire? If you are not sure, try logging the value in that offset (as a UB in hex) to see if they change as expected. John

Answering my questions would help... Ok, so FSUIPC7 has definitely crashed, but there is no related windows event. Very strange... Can you please try try-installing your VC++ redistributables, as I have now advised several times. Have you extracted the installer from the zip file before running? If so, I need to see your InstallFSUIPC7.log file. But not before you have updated your VC++ redistibutables, as advised, so do that first and try again.

Then the error is with that program, which I don't know and cannot help with. You need to contact the support for that program.

Ok. I'll check this and see if I can automatically reload on USB device reconnections if/when in a flight. However, better to try and stop the re-connection if possible. Is the trim wheel connected to this hub? If so try moving it. In fact, try changing it regardless of the hub you are currently using. John

Don't be so sure! The same thing happens to the support requests/bugs I raise - they just seem to disappear into the Asobo systems with no way to track. But at least it will be in there systems, although I doubt very much they will fix this. Asobo doesn't seem that interested in fixing things for external control, they seem to prioritize the visuals and the xbox controls... John

Not sure... Try the FSX HUD controls to see if they have any affect, but they seem to be just for next/previous and not on/off. If not, you can check the PMDG SDK to see if they provide any custom controls for this. Otherwise, if the HUD on/off switch has a keyboard shortcut, you can assign a button to those keys. If none of that works, you could try with a mouse macro. John

Ok, but sorry to hear this. But it really shouldn't be that complicated to set up basic functions, such as primary controls or the POV hat. Just try the following: 1. Delete your FSUIPC4.ini - best to start afresh. 2. Start FSX and load a default GA aircraft. Best to initially set-up your default profile with a simple aircraft. 3. Go into the FSX Control settings and make sure controllers are not enabled 4. Open the FSUIPC main window and select the Axis Assignment tab 5. Move your POV button (in any direction). You should see a 'P' (for POV) as the Axis#. 7. Select 'Sent to FS as Normal Axis 8. Enable the first selection drop-down and select Pan View 9. Click Ok Thats it. Your POV should be assigned. Then assign your primary axis - when you do this choose the action 'Send direct to FSUIPC calibration. Once you have assigned an axis, you then go to the calibration tab to calibrate that axis. Instructions on how to do this are provided in the User guide. If it helps, there is some documentation available in French, although rather old. See: John

Sorry, no luck with this - I can only turn both on or off, not individually. I'm afraid it looks like this is not currently possible. I will raise a support request for this with Asobo. John

Done.

Sure, I will update later today...

You can try that - check in both axes and buttons. If you don't see it there, you can try the HIDScanner program (available from the downloads section of this forum). If that can see it, you can try with the lua com library. Btw, can you maybe give a more descriptive title the next time you raise a support requet. You now have two support requests with the title 'Flight Illusion', with nothing to distinguish them. John

Did you check your USB Hun's device's power management settings? Make sure 'Allow computer to turn off the device ti save power' is unchecked. All devices will be scanned again when a new device is detected, which can take a few seconds. Do you not regain control? No problem - glad its now working. John

Hi Roland. Ok. I do have one more idea - to set the lvar and send the Landing Lights Set event together (via calculator code). I will try this later. John

Are you referring to what you see in the event viewer? So there is nothing there related to FSUIPC? It is very difficult for me to determining what is happening on your system without you responding to my questions. What actually happens when you run the FSUIPC7.exe file? Did you try pressing Alt + F to show the main window? If you start the Task manager, can you see the process running or not (labeled 'IPC Interface and More, for MSFS')?

These don't seem to work in the King Air either, sorry.

There is one other thing that you can try.... Check to see if any of the controls in MSFS itself work. The default key for Landing Lights Right is shift + Ctrl + Num6, and for left is shift + ctrl + num4. If they work, you can assign your buttons to the MSFS assigned key presses. John

No I am not 100% sure, and I did not try this. You should always try/test lvars/hvars/calculator code before using, as I said in my first post: Did you not do this? Have you installed the FSUIPC WASM module (that provides access to lvars/hvars)? Did you activate the WAPI? This needs to be done just the once if you want to use lvars/hvars. Then I suggest you keep the manuals open and check things before asking for support. For example, you said: which is obviously the wrong syntax which even a brief check against the documentation would have told you.... Well, obviously. But from your questions it seems to me that you are not even looking at the manual. I gave both the syntax and an example on the manuals, and you seem to have missed both... Anyway, I just checked those lvars in the King Air, which you should have done as suggested, and they are settable but have no affect. Even stranger, some of the standard landing light controls (Landing Lights Set, Landing Light Right, etc) get logged as completely different controls when sent to this a/c. Very strange. There is also no MobiFlight preset for the King Air landing (or any other) lights, just presets for the AutoPilot (see https://hubhop.mobiflight.com/#/list). So, in summary, I do not think this is currently possible. You could see if there is a mod available where this has been fixed, maybe try this one: https://uwajimaya.github.io/FS2020/ John

If this is the case, then did you not see this: ? And why isn't this clear from the example I give in the documentation: ? I am sorry but I fail to understand why you are asking these questions when it should be clear from the documentation.... So, your lvaroffsets section should look like this (for example - you can use any offsets that are free for general use): What that says is 'assign the lvar L:LIGHTING_LANDING_1 to offset 0xA000 as an unsigned byte, and also lvar L:LIGHTING_LANDING_2 to offset 0xA001 also as an unsigned byte. An then assign one button to the control Offset Byte Togglebits, giving A000 as the offset and 1 (or x1) as the parameter, and the other button to the same control, giving A001 as the offset and 1 (or x1) as the parameter. Exactly as the example given, except you are using 2 lvars and 2 offsets. Why is this not clear from the Advanced user guide and the example given? Maybe, if/when the penny finally drops, you can create a FAQ entry (or User Contribution) explaining how to do this in language you understand, that may help others who have difficulty understanding the manuals. John

Hi Peter, Good! Ah, ok, understood. Ok. Take a look at the examples provided - they should be in a zip file in your FSUIPC7 Documents folder. There are also several documents got using lua with FSUIPC7, but for general lua information you should consult google. Remember that a lua program needs to be started - if its event based, then you would usually start the lua from your [Auto] (or profile [Auto.xxx]) ini section. John

Why are you sending me log files? Please answer my question: What FSUIPC7 clients are you using? Error 13 IS NOT an error message from FSUIPC as far as I can tell... Your 'previous' log file shows that FSUIPC7 exited after about 4 minutes as MSFS was no longer running. The second log file shows FSUIPC7 still running (i.e. not closed down) after 2 minutes. Can you please answer my question and explain what your issue actually is (no pictures please!). i.e. what happens when you acknowledge the message? Is FSUIPC7 still running? If not, are there any events visible in the Windows Event Viewer? John