John Dowson

But which is the lua script that is not working? Can you attach this script please. You are starting 11 luas with auto-start (6 general and 5 profile-specific), and one twice - you are starting the lua script Nav1FreqInit in both your general section and your profile section. If you remove the scripts that are working and just run the one that isn't, does that then work or not?

I need to see your ini file for your AsoftA3xx profile, but it looks like you have assigned a button to start the lua script. As the script is already running, this will just kill the script and run it again. Looking at te script, it looks like you need to assign to set a flag in the script, so you need to assign to LuaSet (not Lua) for the script, and with a parameter of either 1 (for AB_EXT_ExtPwrGPU_toggle) or 2 (for AB_EXT_ExtPwr_toggle). John

How/where have you done this? The only assignment I can see for the TWCS throttle is this one: If that is the assignment you are using, then maybe its the calibration thats causing the issue. You can try removing the calibration and assigning with 'Send to FS as normal axis' instead. I need to see the FSUIPC4.log file (not the installation log). Activate logging for axes controls and move your throttle through its full range and back again, then exit and show me/attach the log file. John

How are you setting the frequency? Have you tried writing the frequency to offset 05C4? Does the aircraft support 8.33KHz spacing? You can check this in offset 0B47. I have no idea what this is.... If its the IOCmodules that are setting the frequency, you need to see how it is doing this as the problem probably lies there... John

What do you mean? If you click Yes to trust, does FSX run with FSUIPC or not? What did you do?

When you go back to the world map, the lua script should be killed. I am not sure what you mean by 'looses connection'. Can you please show me/attach your FSUIPC7.log file showing this issue, and also attach your FSUIPC7.ini file and the lua script and I will take a look. John

Take a look at the available presets (https://hubhop.mobiflight.com/presets/) - maybe try FNX320_FCU_ALTITUDE_KNOB_INC FNX320_FCU_ALTITUDE_KNOB_DEC You can assign to presets by checking Select for Preset. There are also presets to set the altitude scale. Many of he standard FS controls do not work in MSFS, especially for complex add-ons, and you have to use lvars/hvars/Input Events or presets instead. John

This doesn't make much sense as value is a string, and you cannot use the numeric comparison of '<=' on string values - this will NOT be doing what you think. What you can do is check if the 4th character is a period or not, e.g. function Distance1(offset,value) if (string.byte(value, 4) == 46) then -- is 4th character a period (46)? miles1 = string.sub(value, 1, 3) else miles1 = value end prevswitch = -1 -- updates Distance end event.offset(0x0C29,"STR",4,"Distance1") -- DME1 Distance John

I am not sure why its taking so long - I will take a look to see why, but I doubt very much there is anything that can be done to speed this up - its probably related to the gauges/panels dlls that are used to get the lvar values. You could try switching to using the event.lvar function instead, and only write the lvar value when it has changed. You can use the same handling function for all lvars, which will be passed the lvar name as well as the value, so you can have a conditional statement on the lvar name to determine the offset and then set the value. John

You will get a discount when purchasing FSUIPC7 if you have a license for FSUIPC6. John

No - something must be setting the weather, and something clearing it... That is very strange - I don't know what could cause that, but sounds like it may be a memory corruption somewhere. Maybe try installing the P3D client to see if that helps. Until next week... John

Active Sky does not use FSUIPC to inject weather. No - weather manipulation facilities were removed from FSUIPC a long time ago. However, I think there is still a hot-key that allows you to clear the weather, but you need to set this and use it (see the hot-keys tab). You can try logging weather changes (see the logging options) and look at the log to see what is happening - you can attach it here if you like and I can take a look, but I am now on holiday until Tuesday next week. You can also try adding NoWeatherAtAll=Yes to the [General] section of your FSUIPC6.ini. This will make FSUIPC avoid all weather reading and writing activities. Try this and see if you get the same issue. John

Try running with the logging console window open (Log-> Open Console) - you should see when the lua auto files are started. Check to see if this lua auto is started and then try to use it. Just show me your .ini and .log files, the latter generated with Lua Plugins logging enabled and showing your issue. I am now on holiday, back Tuesday, so I will review your files then. John

Ok, but I presume you are also using one of the FSUIPC PFC drivers with FSUIPC... Yes, I understand this. But how is this device assigned? Does it have its own drivers and/or software? is this assigned in MSFS or elsewhere? Does it function correctly in MSFS2020 when FSUIPC7 is not running? Ok. For the log file, can you please activate logging for Events and Buttons & Keys, load an appropriate aircraft and then press a couple of buttons on the GTN 500 that you are having problems/conflicts with, and remember to exit FSUIPC7 before attaching your FSUIPC7.log and FSUIPC7.ini files. Also attach your FSUIPC7.JoyScan.csv file just in-case I need to see that as well. Thanks - you as well, John

What PFC driver are you using? I am pretty sure the PFC driver for FSUIPC is not compatible with XPlane/XUIPC... The FSUIPC PFC HID driver has automatic assignments (i.e. you don't need to do anything) via macros, and for the COM driver you have to assign manually, so there are only assignments that you have created/added. Ok, then the PFC driver is not relevant, and I cannot see how FSUIPC can be doing anything - I need to see your files. Note also that I am finishing for the day soon, and I am away from tomorrow morning, back on Tuesday, so I will probably not be able to review your files until next week.

That ini file is very strange and completely empty, i.e. no assignments whatsoever, and no devices recognised. This cannot be the ini file form your previous installation if you had assignments. It also shows that you are using a very old version of FSUIPC7, 7.4.3 - please update to the latest version, 7.4.8. This is because no devices are recognised (no devices section in your ini file) and so no button press was detected. Try an located your FSYUPC7.ini that holds your assignments, update to the latest version and try again, and attach your files again (FSYUPC7.log and FSUIPC7.ini) if you have any issues. John

I still don't understand this - what exactly is grayed-out? If you have an Assignments menu option in the menu bar, then you should be able to open the assignments panels. Maybe attach a screen-shot so I can see what you mean here. Be aware that if an assignment is shown in the buttons assignment panel and it is grayed-out and you cannot change/edit it, this is because there are either multiple assignments to that button (the button assignment is overloaded), or you have added either a compound button or offset condition. With such assignments, you can only change by editing the FSUIPC7.ini file (as you did to add/create this condition). John

What exactly do you mean by this? If you have not assigned anything to the GTN500 in FSUIPC7, then it should not do anything at all. Maybe there is an id conflict (so it is picking up assignments for a different device)? Can you please attach your FSUIPC7.ini, FSUIPC7.log and FSUIPC7.JoyScan.csv files and I will take a look. But there should be no commands for this device unless you have added them. Or is it also a PFC device controlled by the PFC driver? Where is this device assigned? John

I still don't understand this - what exactly is grayed-out? If you have an Assignments menu option in the menu bar, then you should be able to open the assignments panels. Maybe attach a screen-shot so I can see what you mean here. Ok. John

Yes, just a "glitch"...if it happens again, try a system reboot - that usually sorts things out. Anyway, glad its all working again. John

That is very strange as that is related to FSUIPC7's monitoring of MSFS2020, and nothing to do with client applications connecting to FSUIPC7. Maybe it was something temporary...can you try removing that now and see if it connects or not. Note that option is set automatically if running under windows 11, which you seem to be using - from your log file: Therefore I cannot see how that can change anything... How about those other two apps - PACX and Self Loading Cargo?

When I start LRM, it connects straight away when FSUIPC7 is available/running, even without MSFS running, regardless of the order in starting. The usual reason for clients not connecting is that they are being ran at different priority levels - everything must be ran at the same priority level. Could you be running these clients with admin privileges but not FSUIPC? If you has set the previous versions .exe to run as admin, you will have to do this each time you update. John

Also, please note that your old FSUIPC7.ini may not work directly out-of-the-box with your new PC, as the GUIDs of your devices/controllers may have changed. If you run FSUIPC7 ince with your old ini, exit and then attach your updated FSUIPC7.ini file here, I can take a look and update it for you if needed. John

That log file shows that FSUIPC7 was still running when it was attached. Please ALWAYS exit FSUIPC7 before attaching log files. Can you also attach your FSUIPC7.ini file please. This is rather worrying: Do you not have any general button assignments? John P.S. Try attaching here now instead of file.io

No wonder the file is so large - you have a lot of unnecessary additional logging activated. Please disable all logging for the moment and show me a clean FSUIPC7.log file. Also please make sure that you exit FSUIPC7 before attaching the file. John