John Dowson

'A' variables are standard simvars and can only be read via offsets. John

Please see And please see the provided documentation, the Installation and Registration guide as well as the README.txt. You need to install the VC++ redistributables. Instructions and download link are in the README.txt. John

Yes, as the newly created window will grab the focus (temporarily I think, but not sure without checking). No, I'm sorry but this is not possible. You need to redesign your script to keep the window open and update on relevant events. According to the documentation, that should be possible, and yes, you can use any variable name - its the value of the variable that matters. Have you tried logging the handle when you create/set it, and again when you retrieve it, to make sure it has the same value? I haven't tried updating a wnd window created in one lua thread from another - if you can't get this to work then let me know and I will take a look. Just to clear the reference. It doesn't make much difference in that script, as the event is cancelled anyway so the script will exit and the thread will be killed, but its generally good practice to clear the reference to any handle once the handle has been closed. John

No, not the registry, but the last line in the UserCfg.Opt file, found within the MSFS setup. For example, in my case the last line reads: InstalledPackagesPath "C:\Users\Pete\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages" That's what MakeRwys looks for to get the path. It is normally set when you install MSFS according to the location you choose at the time. I expect you could edit that to point to the link instead, but I've never tried it. Yes, this is what you should try. Create the link as a 'junction' and then update your UserCfg.opt to use this instead of the original full path. John

Hi Thierry, your log shows that MSFS crashed and FSUIPC7 then exited: The TransmitClientEvent errors are logged as MSFS is no longer available but the process that monitors this only checks every second and so you get a few of these logged before it detects MSFS has gone. If you check your event log again, you should see an MSFS crash event before the FSUIPC failure. As this is an MSFS issue, you should check the Asobo forums for CTDs related to SU6 and maybe also raise a ticket with Asobo. John

Can you please show me your FSUIPC7.log and FSUIPC7.ini - always needed (especially the log) if you have issues. John

Sorry about that - not sure what happened. I have let SimMarket know and they should send you a registration key, otherwise I will PM you one later. John

I'm not too sure either as I've never had a call to use them. John knows about them, so I'll ask if he can h To create links, the easiest method is to install the Link Shell extension, which will enable you to create links using windows Explorer. See https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html John

@Knox1423 Thanks for the update.

Check the log file and you will most probably find that it is MSFS that is crashing an FSUIPC7 is exiting normally due to MSFS no longer being detected. Also check the windows event viewer, and you will almost certainly see a crash event relating to MSFS. If this is the case, there is nothing I can do about this and you need to check the Asobo forums and/or raise a CTD bug report with them, including any relevant information (event viewer report + any crash dump files). John

a CTD with FSUIPC7 or MSFS? Please make sure that you are using the latest version of FSUIPC7, v7.2.10, and show me your FSUIPC7.log file after the crash. Also check the windows event viewer from crash/error reports. John

There are currently some known problems with altitude hold in MSFS since the SU5 update- see https://forums.flightsimulator.com/t/altimeter-problems-altitude-hold-and-atc-altitude/433209 https://forums.flightsimulator.com/t/help-with-incorrect-high-altitude-altimeter-setting/429439/4 This has been reported several times, e.g. see John

Necesita instalar los redistribuibles de VC ++ desde: https://support.microsoft.com/en-in/help/2977003/the-latest-supported-visual-c-downloads Primero desinstale si ya está instalado (del 2015, 2017 & 2019), luego instale las versiones x86 y x64. Consulte la documentación. He validado sus dos claves y están bien.

Do you mean 0xc0000022? If so, please see Try installing (or uninstalling then re-installing) the VC++ redistibutables, as explained on the provided README.txt: John

Did you read the section Invalid Key Problems from the Installing and Registering FSUIPC7.pdf and follow the advise there? If not, please do that, otherwise please let me know your order number and I will check your details here. John

Ah, ok - that makes sense. It doesn't surprise me that a SimConnect.cfg configured for P3D causes issues with MSFS. Thanks for the update. John

A couple of more things about your ini: - you are using the lua scripts for the Alpha/Bravo buttons > 32. You no longer need these as FSUIPC now supports up to 128 buttons natively, so these can be removed - you have assigned your hat to the PAN controls - do these now work? I haven't checked in a while, but previously the PAN controls were not working via SimConnect/FSUIPC. To assign the hat to control panning, you can assign to the keys assigned in MSFS to control the views. John

First, you are using an old version of FSUIPC7. Please download the latest (and only supported) version, v6.2.9. Also, looks like your device GUIDs have changed at some point, and you have assignments to the letter assigned to the old GUID as well as the new ones. I have tried to correct this in the attached FSUIPC7.ini, so please try this once you have updated and let me know how it goes. John FSUIPC7.ini

Yes, this offset area is free for general use and many users use this area for lvars. Yes - if you let me know what your software does, I'll let you know an area you can use. I am also planning to update the offset status document with info on that the reserved areas are reserved for, and if they can also be used as 'free user offsets' if the user isn't using the 3rd party app that the area was reserved for. John

Did you click the Register button after entering your details? If not re-install and do that, If you did that, what did the pop-up say? John

What was the issue?

See the User guide, P36: Alternatively, you could try manually editing the ini, removing the raw specifier and changing the delta back to 256 (from1) - see the Advanced User guide for the format of the axis assignment lines in your .ini, P41: John

You need to check the available lvars and hvars. You can list available lvars from the Add-ons->WASM->List lvars menu option. For hvars, you need to make them known to FSUIPC7 by adding a hvar file (for the A320 or FBW A320) to the WASM. Instructions are provided in the Advanced User manual, and a hvar file for the FBW A320 is provided in the FSUIPC7 HvarFiles folder (although it will be out of date, it should be ok to get you going). Alternatively, if using the FBW A320, you could install the MobiFlight WASM module and use the MobiFlight events - check the EventFiles folder for various event files (although they will also be out-of-date). The following link is a good (MF) resource for the MF presets. Even if you don't install the MF WASM, you can still use this to see what lvars/hvars and calculator code their presets use: https://hubhop.mobiflight.com/#/list Also quite a bit of information in this forum on using lvars/hvars/MF for the A320.

Could you please activate: - logging for Buttons & Keys and Lua Plugins in FSUIPC7 (from FSUIPC7 Log menu) - WAPI debug logging (from FSUIPC7.ini file) - WASM debug logging (from FSUIPC_WASM.ini) Then generate an FSUIPC7.log and FSUIPC_WASM.log showing your issue. Also send the calc code from the WASM menu so that is also logged. Please remember to close/exit FSUIPC7 before attaching your log - the one you attached is useless as you don't even have an a/c loaded or get to the ready-to-fly state. If you can then attach the 2 log files I will take a look - but tomorrow, finishing for the day now. John

Please see Appendix 3 in the Advanced User guide: Handling VRInsight serial devices in FSUIPC. Also take a look at the document Lua Plugins for VRInsight Devices.pdf. John