John Dowson

You should never modify the [LuaFiles] section - that section is maintained by FSUIPC. But ipc.control does not have an offset parameter, only one for the control number and one for the parameter to the control. John

As I said, I will renew the trial license next week, on Monday 9th...

Please see this post/comment: If the UserCfg.opt file cannot be installed, you can try and correct this, but this only means that the WASM module isn't installed. You can extract the WASM module by unzipping the following file: C:\FSUIPC7\SDK\FSUIPC-WASM.zip, then unzip fsuipc-lvar-module.zip and copy the folder fsuipc-lvar-module to your MSFS Community folder. John

Neither is fail! I will generate a new trial license next week. John

compress/zip it and then attach.

I think these things can depend on the shell being used....e.g. command prompt vs windows terminal vs power shell....

The FSUIPC4.log file you posted is a continuation log, and so useless. Please only attach full log files for support - don't ever start a new log file. Well, you did say ' I've hardcoded the address inside the wideclient.ini file to specifiy 192.16.1.3.' (should be 192.168.1.3) but the WideClient.ini does not show this, and the logs you are posting show it is trying with the address 192.168.1.100. And as I stated in the previous post, your log showed an initial successful connection to the 192.168.1.3 address. I don't understand this....the log files are created on start-up, although some buffering (by the OS/Windows) may occur before they are actually written to disk, So, can you please set the ServerIPAddr in your WideClient.ini and try again, Reboot both server and client machines before you re-test. And if it still fails then show me all the necessary files (complete, not continuation) which are your FSUIPC log and ini files, your WideServer.log file, and your WideClient log and ini files - all from the same session. Also, please check your Windows Event viewer to see if any network events/failures are reported. Maybe also try running the windows network diagnostics tool(s) to see if they report anything. Your issue is related to your network set-up, not FSUIPC or WideFS. Check the installation of the network cards and your cable(s), and maybe any network logs if you have any/can find them. John

For you, no! You asked for an update of the trial license on 31st May 2022, so you have been using the (trial) licensed version for over 6 months. I provide a trial license for users to see if FSUIPC7 is suitable for their needs. If you are still using FSUIPC7, you should buy a license, not continually use the trial license provided. As people are now doing this, I will be leaving longer periods where a trial license isn't available, to prevent such practices. John

What is PF3? I do not have the time or knowledge required for this. Another million? No where near making the first one....! I will look into using RC4 with MSFS at some point, but I am afraid that this is low priority. I am currently spending most of my time on support issues, and find it difficult finding time to add new functionality to the existing products I support.... John

By the way, you posted in the main support forum. There is a specific sub-forum for FSUIPC7 / MSFS - I will move this topic there. Please use that forum for all FSUIPC7/MSFS issues. John

No, but it sounds like a timing issue - you have to wait a 20-30 seconds (or longer for complex aircraft) for everything to initialise and start-up. Everything will be ready once the message in the FSUIPC7 main window changes to indicate the number of lvars, hvars and presets available. If that is not the issue, then I will need to see you FSUIPC7.ini and FSUIPC7.log files, the latter generated with logging for Buttons & Keys as well as Events activated, Load an aircraft, reproduce the issue, exit FSUIPC7 and then attach those files. Note that there are some changes to key handling in the next version of FSUIPC7, which will be released once I have had time to update the documentation. I have attached it below if you would like to try this version. John FSUIPC7.exe

Attached is the latest beta, 7.3.16b, which is basically the version I will be releasing once I have time to update the documentation and installer. You can try this if you like - just download and drop it into your FSUIPC7 installation folder: FSUIPC7.exe John

The problem is usually caused by the previous aircraft loaded. When you load a new aircraft, many lvars from the previous aircraft are still present, To get around this problem, when you change aircraft it is better to restart MSFS. This also applies when you initially start MSFS, as the last aircraft used will be loaded automatically, so if you are not going to use that, load the aircraft you want to use and then restart MSFS. John

How many lvars do you see? The current limit is 3066 lvars. If you have not reached the limit, you can issue a reload command to re-scan for lvars. If all lvars are not picked-up on the initial scan, you can set the WASM ini parameter LvarScanDelay to delay the initial scan until the lvars you want to use have been created. See the FSUIPC7 Advanced User Guide for details on the WASM ini parameters and how to use. John

Is there an FSUIPC6.log and FSUIPC6.ini file in your installation folder (C:\FSUIPC6\)? If so, please show them to me. If the menu entry is there but the FSUIPC main window isn't being displayed, I can only think that it is being displayed outside your screen coordinates. Can you see it if you hover over the P3D task-bar icon? If you have a size/position instruction in your FSUIPC6.ini, which will be the ini parameter Window under [General], then remove that and try again. John

Well, the FSUIPC documents folder, but you can ignore this, and you can ignore the registry. Really you should just make a copy of the FSUIPC7.exe of the 7.3.8 version, as well as the fsuipc-lvar-module folder in the Community folder (although the latest WASM may be compatible with 7.3.8, not sure...). Please do not ask for support if not using the latest version - the first thing I will ask you to do is update. John

It is not a problem, those messages can be ignored.

I have updated the title of this topic to something more appropriate to your issue. The WideClient.log file shows an initial successful connection: Although subsequent connection attempts seem to be failing, using both 192.168.1.3 and 192.168.1.100 (check your log!). I suggest you try re-starting WideClient if you start getting continual failures (again, check the log). Also, you could try setting the ServerName or ServerIPAddr WideClient ini partameter - and maybe the Protocol parameter, to see if that helps. See the WideFS User Guide for details. Also, as it looks like it is sometimes connecting, maybe check your cabled connection, and look for any windows network events/errors on both the client and server machines, to see if they indicate any problems.

No - profiles are difficult to share. People can share there assignments, or help you with specific buttons or axes. Aircraft, especially complex add-ons, are a lot more complex to control in MSFS. You should start by looking into the presets available for the aircraft you are configuring - and use profiles as the set-up will be different for each aircraft. See the MobiFlight HubHop website (https://hubhop.mobiflight.com/presets/) for a searchable list of available presets on vendor and aircraft. All (or most) presets should be available in FSUIPC7. Not sure what you mean by "the z axis isn't working" - do you mean the axis isn't registered in FSUIPC7, or the assignment to that axis isn't working? There are also many posts already for various issues with the PMDG 737s and the Fenix A320, so try searching this forum. Otherwise create a new post for any specific issues not already addressed. John

...and I won't be increasing this. Too many changes would be needed to support more, especially considering WideClient....I am afraid you will be limited to 9 virtual devices for external triggering. John

Ok, I have now looked into this. Offset area 0x7F00 is badly documented, and is for real joysticks not virtual ones. Basically it is a copy of the facilities provided at offset 0x03C0, but for joysticks with up to 128 buttons, not the facilities for virtual joystick buttons provided at 0x3340. I will correct the documentation. So, for your original question: For virtual device access via offsets, it is only 9 (64-72) and via offsets 0x3340 and 0x29F0. This provides access to 288 virtual buttons. Sorry for the confusion, and the time taken for me to look into this. Regards, John

Ok, I have now looked into this. Offset area 0x7F00 is badly documented, and is for real joysticks not virtual ones. Basically it is a copy of the facilities provided at offset 0x03C0, but for joysticks with up to 128 buttons, not the facilities for virtual joystick buttons provided at 0x3340. I will correct the documentation. John

This is that bgl from my installation which is up-to-date - it is only 516KB so zipping not required: APX46170.bgl John

Please attach your InstallFSUIPC7.log file. This is essential for all installation issues. John

@Luke Kolin Attached is the latest beta, 7.3.16b, if you would like to try with this: FSUIPC7.exe I checked offset 0x6C8E here and that looks to be holding the correct value for AircraftModel (3 for the 737-700 BW). John