John Dowson

Well, there is no point me looking if there is no longer an issue....! From the first error, sounds like a file somewhere was left hanging around (probably a system file for the socket) that prevented the connection, that was eventually cleaned-up. Cheers, John

There is a beta release available here:

The log shows a couple of issues: That should be self explanatory - take a look at line 1 of that lua. That one is probably due to an lvar not being available, but look at line 24 and that should tell you. Writing to an lvar is working ok here, but it won't work if the lvar has not been loaded, which is what I suspect is your issue. Reloading should work now (was broken before) - do you see the lvar count increase when you reload? Did you adjust the LvarScanDelay WASM ini parameter, and if so to what value? You can try listing the lvars - do you see the ones you use? Then reload & list, and see if you see it then, and repeat until no further ones are found. Note that if the lvar is not available when the lua starts, it may not function correctly if later found on a rescan - that would depend in how the lua is written. That is why it is a good idea to set the LvarScanDelay to a reasonable level for the aircraft that you are using. I have plans to implement a feature to provide all lvars as available/created by implementing an auto-scan (for new lvars) functionality in the WASM, but that will be after the next release for SU10 compatibility. Try the above, and if you still have issues, please activate Debug level logging in the WASM/WAPI by adding the following to the [WAPI] section of your FSUIPC7.ini file and to the [General] section of your FSUIPC_WASM.ini file: LogLevel=Debug and then generate another FSUIPC7.log file and show me that, together with your FSUIPC_WASM.log file. You can also attach the luas if you want me to take a look at them.

But what behavior are you referring to? Why are you not showing me the information I need - your FSUIPC7.ini and FSUIPC7.log files? Have you updated to the latest beta (including the WASM update), 7.3.9f?

Can you please also show me your FSUIPC7.log and FSUIPC7.ini files, as well as your WideClient.ini, Your WideClient logs show a windows error 183, which is the following: But I am not sure what file that refers to at the moment (without checking). The second error (10061) means that there was nothing listening on the port you were trying yo connect to. This may be related to the first error, but can you confirm that WideServer was active and waiting for connections when you trued to connect (check the MSFS title bar). John

Ok. There are still issues, so it may not solve your issue. However, I have tested with the Axis Throttle<n> Set controls and they seem to be ok here, but please let me know. John

You have installed under your Windows Documents folder. This is not a good place to install FSUIPC6 due to windows access permissions on this folder. Re-run the installer and select a different non-windows protected folder for the installation. After you have re-installed, you can copy/move your FSUIPC6.ini and any *.lua, *.mcro, *.dll or any other files thar you use to the new location. John

Can you please try the latest beta, just released, which has been updated for SU10, available from Install FSUIPC7-7.3.9f. If you still get issues, please attach your FSUIPC7.log and FSUIPC7.ini files. There may be issues still with the *_EX1 controls which I am going to check now. However, your log extract mentions the standard controls, not the *_EX1 ones, which is strange... Thanks, John

Can you show me your FSUIPC6.log and InstallFSUIPC6.log files please. Do you see a key file FSUIPC6.key in your FSUIPC6 installation folder? Do not post that file! John

I have released a new beta for SU10, including an updated WASM. Full installer available from: Install FSUIPC7-7.3.9f This should fic your issue, but if not please let me know. John

I have released a new beta for SU10, including an updated WASM. Full installer available from: Install FSUIPC7-7.3.9f Any issues, especially with axis controls or using offsets, please report the aircraft and axis control or offset used. There may still be issues with the *_Ex1 axis controls - I have not tested these yet but will do so shortly. John

I have released a new beta for SU10, including an updated WASM. Full installer available from: Install FSUIPC7-7.3.9f John

Yes - since SU10, no gauge events are being received by the WASM. This affects hvar activation as well as setting lvars (except when setting as a double) and the WASM reload. I am looking into this at the moment... John

Please be patient. I am installing SU10 at the moment as well as the latest SDK and will be preparing a new release. I will look into specific issues once this is done. John

I suggest that you wait to see if there is an update to the Fenix, and also wait until I have released a new version of FSUIPC7 updated to the latest SDK. Then, if you still have issues, provide more information - including your .ini and .log files. I will be busy tomorrow reviewing the SDK changes and preparing a new FSUIPC7 release, I can look into specific issues once this is done and not before. Please be patient. John

It us not a substantial change - it is only that the aircraft is taking longer to load and therefore longer to make lvars available. However, if the lvar never becomes available then maybe the aircraft has been updated and the lvar name has changed or is no longer available. What aircraft and lvar are you missing? I am updating to SU10 at the moment. I am finishing for the evening and will look at the SU10 release tomorrow.

8 minutes? If the number of lvars loaded aren't changing, then all are loaded and no point continuing to reload. If the lvar isn't available, then it doesn't exist and no amount of reloading will make it available. FSUIPC can only use the lvars that are provided. There is not one there by default, and yes you should copy the one from your Community folder and then edit, as it says in the Advanced User guide: It is recommended to leave this file as is, and copy to your persistent storage area and modify as and when needed from there.

No need - it is just a timing issue, and it is taking longer (somewhere in loading the aircraft) before the lvars (being used) are available.. This has always been a recommendation when using complex aircraft. The default value for the LvarScanDelay parameter is 5 (seconds), but I recommend a value of 45-50 when using complex aircraft and/or airliners. There will be nothing in the next release, but I do have some ideas to make sure that all lvars are available without having to reload, but I will look into this after I have released an updated version for SU10, now that it has been released.. The WASM menu options are enabled once the lvars have been received, indicated by the number of lvars/hvars/presets available being logged in the FSUIPC7 main window. This only occurs one you have a plane loaded and ready-to-fly, and after LvarScanDelay seconds. If the issue is that the lvar isn't available, then you just need to reload until it is.... You can always have a simple lua script that auto-runs for each aircraft and checks that any lvars you are using are available in a loop, and if not then issue a reload, followed by a short pause/sleep, and exit the loop once the lvar is available. You only need to do this for the lvar you are using that has the highest id (as that will be created last), and you can use the lua function n = ipc.getLvarId(“name”) To see if the lvar is available - it will return nil if not available.

Ok, this will also be the issue for @bangaroo. If the lvars are available on a reload, then this indicates that the scan for lvars is being performed to early. To fix this, set or increase the value of the FSUIPC_WASM.ini parameter LvarScanDelay. It is recommended to do this in an FSUIPC_WASM.ini file in your WASM permanent storage area, not the one under your Community\fsuipc-lvar-module folder, as that will be overwritten when you update/re-install. See the Advanced User guide for further details. John

Ok, thanks. Someone else also reported that the PMDG 737-700 presets are also valid for the 737-800.

First, you posted in the FAQ sub-forum where it explicitly states NOT for support requests. Please take care to post in the correct forum for support, which is here or in the FSUIPC7 / MSFS sub-forum. I am not sure what your issue is, but sounds like the offset being read is empty. Why don't you try logging the value after it has been read, e.g. zzz = ipc.readSTR(0x0130, 256) ipc.log("String read from 0x0130: " .. zzz) xyz = string.sub (zzz, -22) ipc.log("Last 22 chars: " .. xyz) I don't know what you mean by this - you are not using any lua numbers...but if you want to use a string as an integer, you can use the lua tonumber(string) function.

Yes, sorry - thought you were using a serial port device. For the newer USB HID devices, you need the PFChid64.dll driver for use with MSFS / FSUIPC7.

Could you try the attached beta please, 7.3.9e. This should automatically re-write your ini to use the preset name when assigned to an axis, although you may have to go into the axis assignment dialog and click 'OK' to update. Thanks, John FSUIPC7.exe

Thanks @joeherwig. I thought I had removed axes assignments to presets as I wasn't sure if this was that useful and am uncertain about the performance when controlling an axis using calculator code. I added the preset checkbox to allow presets to be used in the right-hand side, but this also has the effect of allowing the preset to also be assigned to the axus input. This isn't an issue in itself, but I think there may be some issues when reviewing an axis assignment to a preset - I will check this and also update the documentation for this. Cheers, John

I don't have the SU10 beta installed so it is difficult for me to advise and this may have to wait until SU10 is released, which should be in the next few days... However, if you could attach your FSUIPC7.log and FSUIPC7.ini files, together with your FSUIPC_WASM.log file, then I will take a look. Has this been an issue with the SU10 beta since release or has this started in a recent beta update? Did you check the SU10 beta support forum to see if others were havung similar issues? John