John Dowson

So this is not correct, and the additional axis scanning I added for you to prevent this now makes no difference? If so, I'll remove this, as it shouldn't be needed anyway. And this is also no longer correct. Do you only get this issue when you restart after you have received the TransmitClientEvent errors and FSUIPC later crashes? If so, its that issue (i.e transmit client event failures) that needs to be resolved, and I wouldn't worry about this other problem for now. And as mentioned in the other post, you should clean your registry as it seems to be in quite a mess.

Yes. It may be easier to disconnect your devices, remove all entries (back-up your registry first), and then re-connect them to get the entries regenerated. Make sure you are using the "JoyLetters" facilities first. If you don't know what this is, just set: AutoAssignLetters=Yes in the [JoyNames] section of your FSUIPC7.ini file.

For the flight path angle, there is a lua script called 'HUD Parameters for FSX' over on avsim that calculates this - you could take a look to see how this is done: https://library.avsim.net/esearch.php?CatID=fsxutil&Name=&FileName=&Author=&DLID=&Sort=Author&ScanMode=0 Extracting the relevant parts from that script:

ROTATION VELOCITY BODY X is 30A8, i.e. Pitch Rate ROTATION VELOCITY BODY Y is 30B0, i.e. Roll Rate ROTATION VELOCITY BODY Z is 30B8, i.e. Yaw Rate 31A8 is STRUCT WORLD ROTATION VELOCITY X 31B0 is STRUCT WORLD ROTATION VELOCITY Y 31BB is STRUCT WORLD ROTATION VELOCITY Z The rest are correct. Not sure about this - I'll get back to you...

I've now reported this in the Asobo 3rd party devs forum.

Btw, which aircraft are you using? Is this a general problem or an issue with a specific aircraft? And have you tried the AP Vs Var Set English/Metric controls? Or offsets 0x07EC / 0x07F2? I was wondering if these have the same issue as the AP_ALT_VAR_SET_ENGLISH event / AUTOPILOT ALTITUDE LOCK VAR simulator variable that needs to be reported.

I believe LINDA is started via an entry it adds to the ipcReady.lua script, which is a different interface for Lua.

There are known issues trying to load .flt files via SimConnect at the moment. This has been reported to Asobo and we are awaiting a fix.

Correct. Yes. However, please check the provided guide, especially regarding windows workgroup names - you need to have both your main PC and client PC in the same windows workgroup. No. Registration is on the server side. You need to re-run the FSUIPC6 installer. This will uninstall and re-install FSUIPC6, but it won't change anything and all your files and settings will be preserved. Please download the latest version (6.0.10) before you do this if not using this version already. At the end of the installation process is the registration screen, where you register both your FSUIPC6 key (which will be pre-populated as you have already registered) and your WideFS key. Enter your details there (and remember to click the Register button) and your key file will be regenerated to include your WideFS license. John

I tried adding this simvar to FSUIPC7. It updates correctly when toggling the button in the UI for the aircraft, but changing this externally seems to have no affect (i.e. its ok for read but not for write). There are currently quite a few reports on autopilot functionality not working via simconnect (especially for the G1000), so i think we need to wait for a simconnect update to get these fixed.

I tried adding this simvar to FSUIPC7. It updates correctly when toggling the button in the UI for the aircraft, but changing this externally seems to have no affect (i.e. its ok for read but not for write). There are currently quite a few reports on autopilot functionality not working via simconnect (especially for the G1000), so i think we need to wait for a simconnect update to get these fixed.

Pushback left/right are behaving in the opposite way of how theywere previously working - this has been reported to Asobo. For the time being, I will swap the controls sent so that previous functionality is maintained. Could you try the attached build please: FSUIPC7.exe

You log shows that a PAUSE_SET control was sent (with parameter 1, i.e. on) as soon as you connected to MSFS: Controls (e.g. axes movements) will not be seen by the sim when this pause mode is set. I cant see where you unset this pause mode - maybe in the sim? Its also set later, sometime after you have closed the axes dialog panel: Next time you experience this issue, check that you have not inadvertently paused the sim. John

As Thomas says, you should try and correct your registry entries, but I don't think this is related to your problem. Your log shows an earlier failure from which it recovered: I've noticed TransmitClientEvent being used in another place on the same thread, so this could be interfering, but I would need to see you SimConnect.log to verify, For now, could you try the attached version and let me know how you get on. If you get the same error with this version, could you reactivate SimConnect logging (as explained earlier in this thread) and show me the SimConnect log file(s) when this issue occurs. Thanks. FSUIPC7.exe

Do you mean 'engine start'? Have you tried the Magneto controls - or do you mean something else? What 'commands'? Which aircraft?

Some work, some don't, and others have issues. We report the ones that we find problems with (that FSUIPC use) to Asobo and hopefully they will be fixed in a future update. I haven't tried the Flight Level Change sim variable yet though, as although its listed in the variable list, its not listed in the simconnect variable list. I'll check it tomorrow.

I'll update to handle the change in values - I'll post a version to test sometime tomorrow.

Yes, the VOR NAV1/NAV2 frequencies in 0x0350 and 0x0352 (for active, presume same issue with standby), aren't populated until the frequencies are changed or set. Most probably an MSFS issue, but I'll check and report to Asobo if needed.

Hi Enrico - which offset are you referring to?

Also see

Which aircraft are you using? Have you seen this thread - maybe it helps: For the A320, there are known issues with AP ALT LOCK VAR - see

You can create an empty profile. Click Preset Manager and then + (New). Give the profile a new and then you are done and have an empty profile.

It could be a corrupt weather file. Try adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC6.ini file. If that works, you have a corrupt weather (*.wx) file, or more usually the wxstationlist.bin file - try deleting that from your APP Data\Roaming P3D5 folder if it is there. It will be regenerated the next time you run P3Dv5.

There are no facilities in MSFS to start external programs at the moment, and its still not clear if such facilities will be provided. If/when they are, I will provide an installer to start FSUIPC7 automatically with MSFS. You could start the GFDevESP.exe automatically with FSUIPC7 - check the section Programs: facilities to load and run additional programs in the FSUIPC Advanced User Manual.

You also didn't mention the FSUIPC or sim version. If the question is about FSUIPC7-Beta / MSFS, then you should post in the specific sub-forum for that product: https://forum.simflight.com/forum/183-fsuipc7-beta-for-msfs/