John Dowson

Is this just on client/remote, or also on the server/FS machine? If just on the client, it may be because SLC cannot access lvars when running on the client (at the moment), so you will need to wait for an SLC update. If its also on the server/FS machine, then ask about this on the SLC forums. Yes - you added this to the client FSUIPC7.ini so that FSUIPC7 can talk to the remote WASM, and as instructed in the Appendix that shows you how to configure FSUIPC7 for remote access. Your logs also showed that this was working fine.

Please see the README.txt file (section Problems installing or registering FSUIPC7) and/or the Installation and Registration guide (section Invalid Key Problems) and follow the advice given there. Only once you have tried everything mentioned there and it still doesn't work, then let me know your FSUIPC7 order number and I will check your details here. Note that in all cases where this is reported this is down to either user error, not having the latest combined VC++ redistributables installed, or due to anti-virus software.

Note that you can always use FSUIPC's offset logging facilities to check/verify the contents of an offset. The aircraft title offset 0x3D00 is certainly populated/available, but may not when MSFS is in the main menu. John

Your remote log looks good, thanks. Your MSFS machine log does show some re-connection attempts at start-up. Looks like your DetectToConnectDelayAuto ini parameter is set too low: the current value is 115, you should change this to around 170.

What sort of problems? I doubt very much this is anything to do with the latest version - there were very few changes in this update and nothing that should cause any issues... I don't usually provide older versions as any issues with a new version should be rectified in that version, However I gave attached the previous version, 7.4.16, below for you to try. Rename your current exe (e.g. to FSUIPC7.exe.7417) and save the attached version to your FSUIPC7 installation folder and try that. If your issues are no longer present, could you then go back to the latest version and try again. If you still get issues, let me know what they are and attach your FSUIPC7.log file, as well as your FSUIPC7_prev.log file from the working version so that I can compare them. John FSUIPC7.exe

FSUIPC only holds a small subset of available simvars (or a-type variables) in its offsets. If you want to use (i.e. read and write) the value of a simvar via offsets, you can add it to a spare/free FSUIPC offset - see the section Adding Simulator variables (simvars) to FSUIPC offsets on page 35 of the Advanced User guide, If you just want to update the value of the simvar, you could define a preset for this, instead of adding it to an offset. But if not familiar with calculator code or RPN, may be easier to add it to an offset and use that, John

Which is why I said to refer to the documentation! it is an ini parameter that changes the default location where the lua files should be located.

Note also that macros are also an easy solution to toggle or set lvars and hvars, but if you also need to read the values of an lvar better to add to an offset and use that. See the Advanced User Guide for details on macro use. I can also see now that the documentation also needs updating, as macros also handle presets and input events.

Thanks for the update. Note that this fix has now been released in the latest version of FSUIPC7, v7,4,17. John

You don't have to use macros - you can just overload the assignments if you prefer, as I showed. However, if you have many buttons with overloaded assignments, and you are using more than 2 actions on a button press/release, it may be better to use macros, but its up to you really. Create a macro file - you would normally name it after the aircraft to which it applies, or maybe the the aircraft + subsystem. As this is for the PMDG777, create a macro file called PMDG777.mcro. and add the following contents: [Macros] 1=GearLandLights 1.1=C66079,0 1.2=C1152,2500 1.3=PPMDG_B777_Landing_Light_Nose_Off,0 Restart FSUIPC7 and you can then assign to the macro and then you would need to add the compound button condition to the assignment (compound and offset conditions always go on the assignment, not in the macro itself). John

Lua scripts should be placed in your FSUIPC installation folder, unless you have LuaPath set in which case they go in that folder - see the documentation. I don't have the fenix so can't help much, but you just need to look into replacing the lvar A32NX_AUTOPILOT_1_ACTIVE with something similar for the fenix, i.e. add an lvar (or something) to that offset which indicates when the AP is active. Maybe the OP @Adamski can help... John

That won't execute both actions as you have the same index number - should be: 19=CP(+A,23)A,10,C66079,0 -{GEAR_UP}- 20=CP(+A,23)A,10,CPPMDG_B777_Landing_Light_Nose_Off,0 -{Preset Control}- To insert a delay, you can add a pause control, e.g. 19=CP(+A,23)A,10,C66079,0 -{GEAR_UP}- 20=CP(+A,23)A,10,C1152,2500 21=CP(+A,23)A,10,CPPMDG_B777_Landing_Light_Nose_Off,0 -{Preset Control}- That will add a delay of 2.5 seconds (2500 milliseconds)., Note that you can also use macros to send multiple commands - see the user manual for details. John

As I have said, you have to choose between the GF software and FSUIPC. If you want to use FSUIPC to control your GF device, then follow the instructions for FSUIPC. I have told you what to do several times now, and there is plenty of documentation which you seem to be ignoring. Again, then read my posts and the provided documentation and try things. If you think this then you have not read the documentation correctly and have not tried to assign anything to your GF devices yet. Why don't you try this? Once FSUIPC is registered, you will have visibility of the buttons/switches assignment panel, which is the UI you used to assign your buttons/switches, and is described in the user manual. No programming is required, although some advanced features may require manual editing of the FSUIPC ini file, which is also described in the user manual). Because there is nothing specific or special about a GF device - it is just another controller. You assign the buttons/switches/rotaries as you would with any other controller. The FSUIPC GF driver (GFDev.dll) just makes the GF device visible to FSUIPC, where it is then treated like any other controller. There is no distinction between any other standard USB controller and a GF device, except that the additional driver is needed for GF devices. I don't understand why you keep posting the same questions, which I have answered many times, and don't just go ahead and try things...at least register your FSUIPC3, install the GF driver and go to the button assignments panel and try and assign to your GF devices. Please do not post again until you have at least tried that. Once you have some hands-on experience, things will hopefully make more sense....

You are trying to install FSUIPC5 or FSUIPC6 - this is NOT compatible with FSX/FSX-SE. You need FSUIPC4, which requires a separate license. John P.S. You posted in the FAQ sub-forum where it states NOT for support requests, I have moved your post.

I have just taken a look at the GFDisplay documentation, and in the first pages, under Installation and Configuration, it says: Did you not see this? i.e. nothing is going to work if you are using an unregistered/unlicensed version of FSUIPC3, which you seem to be doing for some reason, even though the license is freely available. I repeat, READ THE DOCUMENTATION. John

Ok, but there are no issues having both v5 and v6 installed - they are completely separate applications as far as windows is concerned. I think this is the best way to proceed - providing of course that you have enough disk space (just for the P3D installation - most add-ons can be shared), Also then easier to switch between the two, and diagnose any issues with add-ons om v6. Just my 2c. John

But why are you doing this? You can use the same FSUIPC6.ini with P3Dv5 and P3Dv6 - they should be the same as far as FSUIPC is concerned... As I said, there is no difference when running FSUIPC6 with P3Dv6 or P3Dv5. If there is an issue with your programs not starting, you need to look at the FSUIPC6.log file to see what the error code is - this is a windows error code, and look up that to see what the issue is - usually it is either a 'file-not-found' or 'permission denied' error code. Take appropriate action depending on what the error is. Why not have both P3Dv5 and P3Dv6 installed, and use the same FSUIPC6 installation for both. You can then use the add-ons that work in both, and for the ones that do not currently function correctly in v6, leave them out or look for solutions to get them working...or wait for an update. John

Sorry, but it seems that you have either not read my previous comments or have not understood them. I have no idea why you would want to put the GFDev.dll in the GF software folder - it goes in the FSUIPC installation folder (i.e. in the modules folder under your FS installation. And you have to choose between using FSUIPC doe your GF devices or the tools provided by GF. If using FSUIPC, you should NOT use any GF drivers - uninstall them and let windows install default drivers, And do not use/run any GF tools - you only need FSUIPC3 and the FSUIPC GF driver. Again, please see my previous comments. There is no point in even looking at GFDisplay until you have FSUIPC working with your GF devices. And you need to understand how to use FSUIPC3 before toy can start with GFDisplay. Gave toy read the documentation for FSUIPC3, as advised? Well, if its not registered then nothing is going to work, Details of the FSUIPC3 key are available on the fsuipc website (https://fsuipc.com/). I do NOT run the forum (that is SimMarket). I support FSUIPC, versions 4, 5 and 6, As I said, FSUIPC3 is unsupported, but I can help you where I can... But you haven't! You seem to have not even read my previous comments, let alone any of the required documentation, i.e. the documention that comes with FSUIPC3, NOT the GFDisplay documentation. And as I have already said, you proceed by installing AND registering FSUIPC3 (which you haven't done..), then you install the GFDev,dll in the correct place (which you haven't done), and then you test and program/assign your buttons/switches/rotaries. Only once that is done and you understand the basics if using GF devices with FSUIPC, then start looking at GFDisplay and/or lua scripts to control the displays. That is certainly not going to happen and is not necessary. Just read my comments and follow my advice, You seem to be ignoring almost everything I am saying, which is why you are having so many issues. Read my comments and follow my advice - if you can't do that, I cannot help you. John

Yes. If you have multiple versions of P3D installed, then you can either use a single FSUIPC6 installation for all P3D versions installed, or you can have separate installations for each P3D version - see the Installation and Registration guide for details. Why roll-back and not have both P3Dv5 and P3Dv6 installed? You can use the same installation for FSUIPC (and also for many add-ons, aircraft and scenery) for both installations (when using the add-ion xml method). If its on the PC clients, it should be started by WideClient, not FSUIPC, as FSYUPC only runs on the server/P3D PC, not the client. So why copy into FSUIPC.ini? A WideClient installation in a client PC will be exactly the same when using P3Dv5 as when using P3Dv6. Any issues with programs not starting, check your logs to see what the error message/code is - they will give you a hint as to why they are not started. John

No issues? You said: "after much research have failed to get them working in both FS9 and FSX"? Ok, but this is thew first time you have mentioned FS2004. As far as FSUIPC is concerned, FS2004 is the same as FS9 - you need FSUIPC3. Sorry, but this is not possible. The current/latest 32-bit GF driver is (file) version 2.2.2.1 (or product version 2.22, a bit confusing..) from January 2013 - what version are you using? And if using the FSUIPC GF driver (GFDev.dll), you do not need any other GF drivers or software - remove these. Of course! Once the GF driver is installed, this will make your GF buttons/switches visible to FSUIPC, where you then need to assign your buttons/switches, as you would with any other device/controller. The GFDisplay driver is another additional program that uses FSUIPC and the GoFlight driver (GFDev.dll) and is used for driving displays, Start with just FSUPC3 and the 32-bit GoFlight driver (GFDev.dll) and try and assign some buttons/switches. Once you have that working, then add in the GFDisplay program and read the manual to use this. Lua is a programming/scripting language. FSUIPC has a lua interface and additional lua libraries that allow you to write lua scripts that interface with the FS and FSUIPC, and allows further access to GF devices via is gf library. Please see the documentation provided by FSUIPC3. I don't understand why you are having so much difficulty... First, install FSUIPC3 and the 32-bit GFDriver and take a look at the documentation that comes with FSUIPC3. Read the Installation and Registration guide, which will tell you how to install and register, then the User guide, and also take a look at the Advanced User guide and the Lua Plug-Ins document. This should give you an overview of the functionality available and the knowledge to program/assign your GF buttons/switches/rotaries. Once you have that working, then look into adding GFDisplay to control your displays. And please note that: - FSUIPC3 is provided free-of-charge but is unsupported. This is very old now, I have never used it and have no access to the source - I do not have any GF display devices and have never used the GFDisplay program so cannot really help with this - I don't have and have never used FS9 or FS2004 What GF devices do you actually have? You can also try searching these forums for advice and possibly lua scripts for specific devices. But I really don't understand why you/anyone would want to continue using FS9 or FS2004. You should consider updating to either MSFS2020 or P3D (v5 or v6), or at least FSX (but this is also very old now!).

Yes - it is available as an FS Control, but it shouldn't really be needed...

No - I don't have anything configured/assigned for this aircraft. For aircraft that I have for support purposes, I only look into assignments on request (and when I have time!). This looks like quite a complicated aircraft and I would need to spend quite a bit of time to learn how to control this. For example, I don't know how to activate the Autopilot in the cockpit - I can't seem to move the AP engage switch in the VC, but I suspect this is something to do with the state of the aircraft (I can see/read that it needs turn knob in detent and one yaw damper powered, as well as main/essential power on - I would need to read/investigate on how to do this...!). However, there do seem to be quite a few lvars as well as input events available for the auto-pilot: Input Events: AUTOPILOT_PITCH_SELECTOR<>=2.000000 AUTOPILOT_KNOB_VERTICAL_SPEED<>=0.000000 AUTOPILOT_TURN_KNOB<>=50.000000 AUTOPILOT_HDG_SEL<>=0.000000 AUTOPILOT_ALT_SEL<>=0.000000 AUTOPILOT_ENGAGE_SWITCH<;FLOAT64>=0.000000 AUTOPILOT_NAV_SELECTOR<>=0.000000 Lvars: 417188 [INFO]: ID=529 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG_SW_IsDown = 0.000000 417188 [INFO]: ID=530 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG_SW_MinReleaseTime = 0.000000 417188 [INFO]: ID=531 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM_SW_IsDown = 0.000000 417188 [INFO]: ID=532 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM_SW_MinReleaseTime = 0.000000 417188 [INFO]: ID=533 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG_SW_IsDown = 0.000000 417188 [INFO]: ID=534 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG_SW_MinReleaseTime = 0.000000 417344 [INFO]: ID=1130 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG_SW = 0.000000 417359 [INFO]: ID=1131 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM_SW = 0.000000 417359 [INFO]: ID=1132 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG_SW = 0.000000 417406 [INFO]: ID=1322 FSS_B727_WASM_SET_AUTOPILOT_HEADING_LOCK_DIR = -999999.000000 417469 [INFO]: ID=1573 FSS_B727_PDSTL_AUTOPILOT_HDG_ENG = 0.000000 417469 [INFO]: ID=1574 FSS_B727_PDSTL_AUTOPILOT_ALT_ARM = 0.000000 417469 [INFO]: ID=1575 FSS_B727_PDSTL_AUTOPILOT_ALT_ENG = 0.000000 417609 [INFO]: ID=2044 PMS50_AUTOPILOT_INSTALLED = 1.000000 417609 [INFO]: ID=2045 PMS50_AUTOPILOT_VERSION = 3.000000 417609 [INFO]: ID=2046 PMS50_AUTOPILOT_TOGA_ACTIVE = 0.000000 417609 [INFO]: ID=2047 PMS50_AUTOPILOT_MANAGE_MANUAL_ARMING = 1.000000 417609 [INFO]: ID=2071 PMS50_AUTOPILOT_ALT_ARMING = 1.000000 417609 [INFO]: ID=2085 PMS50_AUTOPILOT_CAPTURED_ALTITUDE = 0.000000 417625 [INFO]: ID=2142 FSS_B727_AUDIO:autopilot_disconnect = 0.000000 So you should try those - you can see what values are needed by activating in the Virtual cockpit then re-listing the lvar/input event values and see how they change. If there are both input events and lvars available for a button/switch, I would try the input events first, although an lvar update may be sufficient. Let me know how you get on - any issues let me know and I can investigate further. John

Yes. This just means that any lvars detected after the initial scan will not be known to FSUIPC, i.e. if you try and list them or use them with an lvar function (e.g. adding to FSUIPC offsets, using directly in a macro or in a lua lvar function) then they will not be seen or updated. You can still use such lvars via presets/calculator code. This should not be an issue as any lvars you want to use should be loaded and available after the first scan. Note also that if you create lvars via the various mechanisms for this in FSUIPC, a scan will automatically be performed and the lvar will be available. You can also force a scan if/when required (via the Add-ons->WASM->Reload menu option, or via lua (ipc.reloadWASM()) or a specific add-on control Reload WASM). John

It is likely that your WASM module is crashing - see the following FAQ entry on how to confirm this and how to prevent this (or at least make this less likely to occur): John

FSUIPC3 is compatible with the FS9.1 update (which was made available on October 9th 2004) but not FS9. FSUIPC3 is now available for free - see https://fsuipc.com/. But be aware that FSUIPC3 is no longer supported. For Go Flight modules, you need to use the FSUIPC 32-bit GoFlight drivers, available from the same location - just copy the dll to your FSUIPC3 installation folder. Note that I have never used FSUIPC3 (before my time!) but I believe the GF driver should also work with this version. For FSX, you will need a registered copy of FSUIPC4, and also the 32-bit GF driver. There is certainly no issue running FSX/FSUIPC4 on Windows 11. If FS9.1 also runs on windows 11, then so should FSUIPC3 (as it is an embedded dll) and the GF drivers. John P.S. GF devices are also supported by FSUIPC's lua interface. Lua scripts will be needed to support any GF devices that have displays. See the User Contributions section of this forum for some lua scripts for GF devices.