John Dowson

Looking at the P3D SDK, the sim vars associated to COM and NAV failures: PARTIAL PANEL COMM PARTIAL PANEL NAV should be settable. I will look into this further, but will take a few days before I have time to look into this. John

From the documentation for 0B68: Fail mode: 0 ok, COM radio gauges inoperable = 1 See also 3BD6 ?-SimC No-SimC+ i.e. that offset is not writeable. For 3BD6, the documentation says: Panel failure modes (FS2002 and FS2004 only). i.e. this offset is not working in P3D. Some flags may work in P3D, but maybe not all, and for COM and NAV the documentation does say : 3BDA COM (both COM1/2 in FSX) (Not writable – SimC?) 3BE1 NAV (both NAV1/2 in FSX) (Not writable – SimC?) 3BE2 NAV (ditto) (Not writable – SimC?) So, it seems that it is not possible to set these via offsets (or lua). John

So there is no issue, no? Your log shows that FSUIPC exited normally due to MSFS exiting, which I presume you did... Your log is slightly strange though, as it looks like FSUIPC crashed as it was exiting - the "FSUIPC Log file closed" log message was never reached... But what problem do you think I am investigating? As I have said, I am not (and cannot) going to investigate the lua crash when exiting a flight if this isn't causing any issues, such as hanging FSUIPC. Please only report back if you are having any actual issues - if the lua is crashing on exit, but not causing issues, I don't see any need to investigate. Of course, it would be nice to know the cause, but this is very difficult to investigate from here when i cannot reproduce. If it does actually cause you issues, I could look into providing you with a debug-enabled version, and get you to configure and generate a crash dump file which I can use to debug, but I don't see a need to do this at the moment. John

It will be the name of the aircraft as supplied to FSUIPC via SimConnect, which will be logged in your FSUIPC7 log file - for the default G36, it is the following: 157250 Aircraft="Bonanza G36 Asobo" Not sure of the name with the mod - load it and check your log file. No, FSUIPC7 does not scan for hvars - there is no way of doing this as far as I'm aware. The whole purpose of the *.hvar files is to make the hvars for an aircraft known to FSUIPC7. FSUIPC7 only knows about hvars that you provide using these *.hvar files. Please see the Advanced User guide. John

If MSFS crashed, you need to report to Asobo. Check the Windows Event viewer - you should attach the crash event if/when reporting to Asobo. It won't, if MSFS crashed. Only if you think there is an issue with FSUIPC. If MSFS is crashing, I cant help. John

Btw, I won't be looking into this again until you have corrected those issues and reported back. John

Hi Leo, can you try the attached version please. The only change in this from the released version is updated multi-threading protection added aroung the reception of lvar/hvar names, but hopefully this should prevent the crash when receiving lvars/hvars. I haven't had time to fully test but it should be ok.... Of course, it won't help if your crashes are still related to lua coms. John FSUIPC7.exe

Yes! Its a stand-alone program and doesn't register itself for uninstall via windows app management. John

Once you have clicked somewhere, thats the box you get to name the macro. Did you do this? Once you haver named it, if you have finished creating mouse macros (it is designed so that you can create multiple mouse macros pers session, in one mouse macro file) you then go to the assignments dialog to finish the macro creation. Then click the Reload all buttons button, and you should see the macro you created for assignment. That doesn't sound like a good use of a macro....macro's are for activating aircraft controls when no other method (e.g. standard controls or lvars) are available. They cannot be used to control P3D (menu) functions. I think the standard method to achieve this would be to use the view controls - take a look at those. John

Ah, good! So it looks like it was an issue due to permissions on the Documents folder. Thanks for reporting back. John

That is strange. I have seen a similar issue with VoiceAttack, but only when trying to start using a shortcut not the exe itself. Is LINDA now started through an exe, rather than via a lua script? Guess I'm going to have to download and install... I will look into this tomottow/next week. John

By the way, you have two [Auto] sections: This will cause issues - maybe the Rotaries.lua isn't running because of this duplication. And you don't need the hidBravoButtons.lua script any more - all buttons are now handled natively. So, remove that 2nd [Auto] section (and the hidBravoButtons.lua script) and try again. John P.S. You also have two [LuaFiles] sections. Did you create these manually? You should never touch these sections, they are managed by FSUIPC. Please also delete this: And please do not manually change this section. I suggest you read the User manuals.

I am sorry but re-reading through the above it is clear that FSUIPC7 doesn't support your devices so they must be handled by ProSim or Cocklpitsonic software, so you probably need their support. Or maybe some other of these device owners can help.... John

It is not red or green anymore, but you should see a simconnect text window once you have clicked somewhere. Note that the sim will initially be paused when you exit FSUIPC, so you first have to un-pause (press the 'P' key). You should then be able to click on the control that you wish to create the mouse macro for, and then see the simconnect text window to name the mouse macro. I have just checked this in P3D and it seems to be working as expected. John

Could you also maybe try with FSUIPC (and the linda.exe) installed outside of the Documents (add-ons) folder. This should really only be used for the add-on.xml. I have seen various strange issues when FSUIPC is installed under Documents. John

None at all - don't any of your assignments work for the CRJ? The first thing to try is to activate the function that you want to assign in the UI, with Event logging activated in FSUIPC7 (and also open the logging console). You can then, hopefully, see what control the aircraft is using and assign to that. Otherwise, you will have to look into the available lvars and hvars (or calculator code), and use those. I good resource to see what is available is the MobiFlight Hubhop site: https://hubhop.mobiflight.com/#/list I cannot help you assign all your functions, but I could maybe help to get one or two working for you, and then you can try the rest yourself. I do have the CRJ, although its not a plane I fly or am familiar with, so I can take a look, maybe later but probably tomorrow now. John

Could you show me the FSUIPC6.log file please - it should show an error if unable to start a program. The previous log file posted showed LINDA being started via ipcReady.lua, and not via an exe from the [Programs] section: John

Ok, that is very strange - I will take a look and get back to you. John

So it is MSFS that is CTDing, not FSUIPC7. Your logs show that FSUIPC7 is exiting normally as it has lost its connection to MSFS, and so exits. Check your windows Event log - you should see a crash event for MSFS, and after there may be a failure event for FSUIPC7, but this is caused by the MSFS crash. You can try PACX support, but usually MSFS crashes should be reported directly to Asobo, including the windows crash event. John

This is used (by FSUIPC) to map the joystick IDs to the device letters, or JoyLetters, as they are referred to in FSUIPC. No. P means 'Press', as in a button press. The format is described in the Advanced User guide. 'F' will be the JoyLetter, 3 the button number, etc... Please see the documentation. FSUIPC re-writes the numeric assignment when it scans your devices and registry to determine the id of each device, then maps this to the letter used on the GUID and name. John

No, WideFS7 is the version of WideFS that is compatible with MSFS2020, not WideFS6. John

Please see the provided README.txt, under Problems running FSUIPC7: If that does not solve your issue, please show me your FSUIPC7.log file. John

Please show me your FSUIPC7.log file, located in your FSUIPC7 installation folder. John

Sort of...but its a substring match, so will match any aircraft containing the string "Cessna Grand Caravan" - can be at the start of the string but diesn't have to. As I said, please see the User manual! John

It is not included, it is a separate (licensed) product. You only need a license if you plan to run WideClient on a 2nd/slave PC, to support FSUIPC applications there. John