John Dowson

Thanks Thomas - hadn't noticed the FSX version from the log! John

Thats your FSUIPC4.log file, not your installation log. That does show you have issues with SimConnect: 78 FATAL ERROR: FSUIPC4 cannot connect to any supported version of SimConnect but please show us your installation log file 'FSUIPC4 Install.log'.

Can you please show us your FSUIPC4 installation log. Note that you images show that you have file types for know files hidden in Windows Explorer - best to change this so that you can see the File extensions.

Yes, sorry - I still need to add the documentation for using hvars. To use hvars, you first have to let them be known by the FSUIPC WASM (and hence FSUIPC). You do this by adding a *.hvar file to the FSUIPC WASM module (under the modules folder). The current beta v7.1.0f only has 1 hvar file, for the A320, and this is quite old now and needs updating. I will do this at some point, and maybe provide some hvar files for other aircraft - I have asked users to supply these, when found, but have so far only received one for the DA40-NG, which I will add in the next release. Only one *.hvar file is loaded per aircraft, which will be the first one found on a substring match to the aircraft title. You can add hvars to the file when FSUIPC7 is running, and issue a Reload command (from the Add-ons->WASM-Reload option) which will reload hvar files and re-scan for lvars. To use hvars, you can either use macros, in the same way you would use an lvar, except only the Set command is available. Otherwise you can use the ipc.activateHvar function. I am planning to add some specific FSUIPC controls for lvars/hvars to make them easier to use, i.e. 'Lvar Set', 'Lvar Toggle', 'Lvar Increment', 'Lvar Decrement', 'Lvar Cycle', 'Hvar Activate'. There are a few complications with this (mainly that the IDs of lvars aren't consistent!) and I need to update the WASM /WAPI to enable callbacks, so this is going to take a while. I may also add a user facility to populate (user) offset with lvar values, to make them more accessible.

What 'undocked windows' are you referring to? It is nor possible to control the positioning of MSFS windows. There are also issues with the SimConnect text display facilities in MSFS. If you are using the lua Wnd library, these windows can be initially positioned and then moved/resized as needed. The size/coordinates are stored in your FSUIPC7.ini and will be re-used the next time the window is displayed.

Yes: You are using an unregistered version of FSUIPC5. If you have a registration code, you need to enter this at the end of the installation process. Note that a registration key for FSUIPC6 will not work with FSUIPC5 (or any other version of FSUIPC) and vica-versa.

How is your trim assigned? If its on an axis, check the calibration and your calibration slope setting, and adjust as needed. You can also activate logging for axes controls (if assigned to an axis) or to events, if using inc/dec controls, to see what is being sent to the FS - best to do this with the console open so you can see what is happening in rea-time.

Offset Mapping for PMDG 777X.pdf

Still a bit strange - not sure why you are still getting the DevCom thread termination messages... And looks like the 'Extras' logging is not logging the thread info....I thought I had already added that to FSUIPC6, but maybe its only in FSUIPC7. I'll check and add it to FSUIPC6. Helps a lot for this type of thing as there are various threads interacting with lua / devcomms. Once thats done, I'll do a few more tests here on killing/restarting luas that use coms, but it will probably take a while before I get time for this.... John

That activates an hvar - you can also do that via a simple macro file: and then assign your button/key to the hvar. But as I said earlier, to use hvars you need to make sure it is in the A320.hvar file (or add it and perform a WASM-> Reload) that is located in the FSUIPC WASM module folder.

Its the same as it previously was (i.e. in FSUIPC4/5). When I originally did the update, there was no structure packing specified so I updated to 1 byte packing. However, in a later iteration I reverted back to 4 byte packing. Ok, corrected. Yes, due to the 4-byte packing. I am still waiting someone to verify this is correct by checking the data for COMM_ReceiverSwitches[0] at offset 6C5A. If that has the correct data, everything else should be ok. John Offset Mapping for PMDG 777X.pdf

So it is - corrected: Offset Mapping for PMDG 777X.pdf

Hi Reinhard - thanks for the update.

Those lvars are Momentary - they should/probably perform some action and then revert back to its original value. Could that be what is happening?

So I did, sorry about that - here is the correct/latest version: Offset Mapping for PMDG 777X.pdf

Yes, there was another section of code that was killing the lua but only had a 100ms delay to wait for the termination procedure to complete. I've changed this to use the TimeForLuaClosing instead, when there is a termination function. Could you try this version please, v6.1.1f: FSUIPC6.dll

What is you TimeForLuaClosing set to? I'm not sure where the 'Poll loop stopped' message comes from (can I see your latest version of the lua script please?) I ask because there doesn't seem to be much of delay between these messages: Maybe there is another section of code that is killing in this situation and i need to add the delay there, I'll check,. But, please activate Extras logging before you show me any more log files. And if your script is changing, its helpful to see that.

We cannot possibly provide bespoke support for everyone using FSUIPC to configure their controls. That is why we provide User manuals - lots of them. Please read the documentation and try to configure for yourself. If you have any issues, search the support forum first (as most questions have already been asked), but if you still can't find a solution to your issue, then post, providing any required information, such as what you are trying to achieve (including a relevant topic title for your problem), what the problem is, and attached associated files, such as your settings (your FSUIPC6.ini file) and your log (FSUIPC6.log file). John

@aua668 Could you try the attach dll please. 6.1.1e: FSUIPC6.dll

Found another issue - FIRE_EngineHandleIlluminated and FIRE_APUHandleIsUnlocked are arrays of 2 bools not just single bools. Updated document attached, and the offset to check for COMM_ReceiverSwitches[0] is 0x6C5A. Offset Mapping for PMDG 777X.pdf

It is MSFS that starts FSUIPC7, not the other way around. Try starting FSUIPC7 manually (by double clicking the FSUIPC7.exe) to see if it runs. If so, show me your InstallFSUIPC7.log file. If it doesn't run, tell me what error you see. Its also in the system tray, not the task bar. When FSUIPC7 starts it displays a splash screen. If you see that, it should be in your system tray, if not, it has not been started.

Sorry, thats also wrong! Attached is hopefully correct, and COMM_ReceiverSwitches[0] should be at offset 0x6C58. Offset Mapping for PMDG 777X.pdf

This was reported as working a couple of weeks ago, after the last but one update. I haven't tried it with the latest version but should be ok - why don't you just try it (and report back!).

It shouldn't hang P3D. But you have errors in the script you should address first: Also, as I said, could you please activate logging for 'Extras' for such issues, as the thread id is useful. If you correct those errors and still have the same problem, show me the log again (with the Extras logging enabled) as well as the script.

Looks like OneDrive is screwing things up - this is strange: InstallDocumentsLocation=C:\Users\k7890\OneDrive\??\FSUIPC6 What is the '??'? You can try disabling OneDrive and re-install. Also you have installed FSUIPC in your Documents folder: Better to install in a directory outside of your Documents folder, somewhere like C:\FSUIPC6 or C:\P3Dv5 Add-ons\FSUIPC6. Re-run the installer (it will uninstall your current installation) and choose a different folder. If all else fails, I could help you to manually switch the the add-on.xml method, but there is not a problem if you just continue to use the DLL.xml method to auto-start FSUIPC6. If its installed via the add-on.xml method, you should be prompted to enable the first time you run P3D after installation, or ir can be activate/deactivated from the Options ->Add-ons menu. FSUIPC6 also appears there, but only when installed via the add-on.xml method. For issues getting GSX installed and running, you will need there support. I don't have GSX.