John Dowson

I have now updated FSUIPC7 to recognise the MSFS AI traffic state strings, version available here: John

This has been corrected in the attached version, v7.1.1a. There are couple of new states that I have had to map to existing states: STATE_TAXI_FOR_TAKEOFF mapped to STATE_TAXI_HOLDSHORT (was taxi-out) STATE_TAXI_TO_REFUEL mapped to STATE_PRE_TAXI_FOR_TAKEOFF (was pre taxi out) STATE_WAIT_FOR_ENGINE_SHUTDOWN mapped to STATE_ENGINE_SHUTDOWN (was shutdown) STATE_WAIT_INIT_CONFIRM mapped to STATE_WAIT_FOR_ENGINE_START FSUIPC7.exe

Please use the attached key file, valid until 17th May 2021: FSUIPC7.key

Ok, this looks to be an issue with FSUIPC7, not Asobo. FSUIPC7 is receiving the AI state strings, it is just that these have now changed and so are not being recognised by FSUIPC7. I am looking into it and will update. I will let you know when fixed.

Ok, this looks to be an issue with FSUIPC7, not Asobo. FSUIPC7 is receiving the AI state strings, it is just that these have now changed and so are not being recognised by FSUIPC7. I am looking into it and will update. I will let you know when fixed.

Just took a look and yes, it looks like the state still isn't being populated correctly. It shows 'Enroute' for all airborne traffic and is empty for all ground traffic. I'm going to check the code, but this looks to still be an issue with the data received, so if this is the case I will raise again with Asobo. John

Just taken a look at this and the 'On Ground' AI traffic flag seems to be working as expected. I sat on a ramp at EGLL (Heathrow) and monitored ground/air traffic (using TrafficLook) and could see aircraft taking off (switching from ground to air) and landing (switching from air to ground), so I take this as to imply that the On Ground flag is being update properly. The only data that seems not to be populated is the 'state'. This seems to show 'Enroute' for all airborne traffic and is blank for ground traffic. I will look into this further and raise another ticket with Asobo (if needed). John

Turn off logging for IPC Writes/Reads. If you want to log a specific offset, use the offset logging function (menu option Log -> Offsets...). You may also want to activate Event logging, which would show the controls being sent (although you will also get some events that are continually logged - these are different for different aircraft, and can be ignored using the DontLogThese ini parameter). Maybe, I don't know. I don't use Prosim or MobiFlight, sorry. So MobiFlight with FSUIPC works ok, its just when you use Prosim with MF + FSUIPC that you have issues? If that's the case, maybe its Prosim support that you need? I'll add ProSim to the title of this topic and it may attract other Prosim users who may be able to help. I thought the latest version of ProSim has direct assignments and doesn't use FSUIPC, but I may be mistaken on this....

First, please update to the latest version of FSUIPC7, v7.1.0. Then please do as advised, i.e. activate logging for Axes (and also for Buttons & Keys as well as Events, as you also have buttons assigned to both throttle and prop pitch controls), then produce a log file showing your issue. DO NOT start a continuation log file - I need to see the complete log.

Ok. But your install log looks good, installing ther latest version. But your FSUIPC6.log and FSUIPC6.ini still show toy using an out-of-date version: Are those old files? Anyway, glad your problem seems to have gone away. Regards, John

Ah, this seems to be the issue: It looks like two different Documents folders were returned. Were you prompted for an admin username and/or password when you installed? This usually occurs when the user under which you are installing doesn't have admin privileges. If this is the case, then I suggest you first uninstall (by running the provided installer or from the Windows App management panel) and then (temporarily) give your user account admin privileges, and then re-run the installer. Other than that, you can try two other methods: 1. manually move your add-on.xml file from D:\Documents\Prepar3D v4 Add-ons\FSUIPC6\add-on.xml to C:\Users\Ian Oak-Rhind\Documents\Prepar3D v4 Add-ons\FSUIPC6\add-on.xml. 2. Re-install, but this time deselect the 'add-on.xml' checkbox. Doing this, the old method of using the DLL.xml file will be used to auto-start FSUIPC6 with P3d.

Looks like it was installed ok. Go to the Options -> Add-ons... menu option in P3D and see if its registered, and if so you can activate it there.

What is this? Can you attach your files please, or at least paste them quoted, so I know what is what....

First, you posted your FSUIPC key. Please, NEVER do this. I have removed it, but if you do this again your key will be black-listed. Can you please show me your InstallFSUIPC6.log file.

Sorry, but I have no idea what you are talking about. The axes assignment window, as all others, are model, and you shouldn't be able to minimise when open. You have to close it first (via Ok or Cancel). The only window you can minimise is the main window. Please explain your issue further so I can understand what you are talking about, or maybe provide a short video.

Just allow it, or add an exception to trust. That is just a splash screen displayed while MSFS is starting, which takes 30-45 seconds, depending on your system.

Remove assignments (or, better, create a new empty profile for your devices in MSFS). For your keyboatd, you should use the defualt keyboard assignment in MSFS, unless assigning your keys in FSUIPC, in which case check that you have no duplicated assignments. Otherwise, activate Axes logging in FSUIPC, load an aircraft and move your throttle showing youe issue, then close down and show me your FSUIPC.log and FSUIPC.ini files.

Please do so, but with the latest version, v6.1.1, released earlier today.

Yes, but I don't know why your EXE.xml is not working. Does FSUIPC7 actually run - have you tried running it manually? I have also just released v7.1.0, so you should download and update.

Are you sating that having FSUIPC installed (and running, presumably) when P3D runs, this gives you problems with P3D recognising your keyboards, as wel las other strange issues, but uninstalling FSUIPC6 and this issue goes away? Could you also show me your FSUIPC6.ini and .log files (from your configuration where things hang or you have issues). Can you also check your windows event viewer, to see if there are any crash (or other strange) events logged there at the time this occurred, and if so, please show them to me. As I said, FSUIPC does nothing special with keyboards, and only receives the key presses/release via standard windows messages. Does everything work ok for you, in FSUIPC and P3D, when using just one keyboard? Cheers, John

No need to. Your installation log looks fine, as does your EXE.xml. Ah, then maybe you are now using an early version of MSFS that does not have this facility (EXE.xml) yet enabled. What version are you using? Will you be updating to the latest version? If that is the case, and you are not updating (or if it still doesn't auto-start via the EXE.xml), you could re-activate the older method of doing this, via the desktop link. To do this, open the desktop link MSFS.lnk in an editor and fine these lines (should be from line 32): Remove those two double colons (highlighted) before the timeout... and start... commands and save.

The FSUIPC WASM and support for lvars/hvars has now been released as FSUIPC7 v7.1.0. This topic is now closed. For any further issues, please raise a new topic (or use an existing appropriate topic). Thanks. John

The implementation of the support for up to 128 buttons is now complete, and has been released as FSUIPC7 v7.1.0. This topic is now closed.

The implementation for up to 128 buttons has now been completed with the release of FSUIPC6 v6.1.1. This topic is now closed.

Sorry, but no time today as I need to release both FSUIPC6 and FSUIPC7. I will look into the traffic information provided tomorrow...