John Dowson

Ok. Please also set Debug logging in the WAPI (Log ->WAPI -> Debug) and show me your FSUIPC7.log, FSUIPC7.ini and FSUIPC_WASM.log file if/when this happens again, and attach after exiting FSUIPC7. Also worth checking the MSFS debug console (you need devmode activated to see this) to see if any errors (related to FSUIPC) are reported there, especially if there is a message relating to the FSUIPC WASM crashing.

Also change your profile aircraft names to use substrings - if you don't do this, your assignments will not load when you use an aircraft with a different livery. Change to and to and to etc. i.e. You should change the aircraft names added to a profile section to a substring that catches ALL variants. If you leave the name as it is, you will have to add the aircraft again when you use a different version/livery. You should get into the habit of doing this each time you add an aircraft to a profile.

Are you manually starting FSUIPC7 or is it auto-started? The log file you attached shows that FSUIPC7 was manually started. You tried to start using presets 5 seconds after starting FSUIPC7, which gave errors: However, FSUIPC7 only became ready for use after 11.422 seconds: Any assignments will not work until after the 'Starting everything now' line is logged, and presets are not available for use until the '[INFO]: Connected to MSFS' line is logged, and generally you should wait until initial lvars have been received and any lua autos have been loaded, which is after this line: 11422 Lvars/Hvars received - checking aircraft autos.... Your ini file also does not contain the DetectToConnectDelay or DetectToConnectDelayAuto ini parameter - did you remove these? Please add the following to the [General] section of your FSUIPC7.ini file: DetectToConnectDelayAuto=60 DetectToConnectDelay=1 StartUpTuningActive=Yes and change the following (currently set to 45): InitialStallTime=15 Well, it would have be useful to see your FSUIPC7.log file generated when FSUIPC7 was auto-started and you had this behavior - the log you attached was from when you manually started. Make the changes I mentioned above, then run MSFS, let FSUIPC7 get auto-started, and then exit MSFS. This will allow FSUIPC7 to auto-tune those start-up parameters. Then run MSFS again and let FSUIPC7 get auto-started. If you have any issues after this, exit FSUIPC7 and show me your FSUIPC7.log and FSUIPC7.ini files again.

Were you running any other FSUIPC clients (including WideClient) when you generated those logs? Better to not have anything else running (except WideClient, but only if running RC on a client machine). This also includes lua scripts, as it looks like these are also logged. A single log file containing RC reads/writes would be the most useful, and it doesn't have tpo be that big. Once RC is running and working but has the incorrect altitude, exit FSUIPC7 and then attach the file. I don't think you will need to spoof everything that RC is reading, only what is necessary. For example, probably not necessary to spoof cloud info (and this is not available anyway!). If the main issue is with the altitude, then this is what needs to be read correctly. You can also just spoof them with dummy values for now - they don't have to be accurate for the time being. Thats okay though, as those offsets are populated correctly, no? That is interesting....how did you determine what those offsets are holding? The problem with the area at CC00-CFFF is that this is weather at 'the requested location', i.e. I would expect to see writes to offsets C800-C8FF to specify the location before these offsets are read, but I see no writes at all for this area. However, I do see writes to the 'weather at requested location; read area CC00-CFFF: Not sure where those are coming from - are they being spoofed (via lua)?

@BJHawk When you lose connection during flight, does the PMDG VC still respond? I ask because I see there is a report on avsim about the loss of controls in the PMDG 777 during flight: https://www.avsim.com/forums/topic/646210-pmdg-777-does-not-work-anymore-in-flight-cant-do-anythin/ So there could be an issue with the 777. John

@dutchkip Can you try the following ini file please, attached below. I have corrected your ini and removed the duplicate device letters. Some assignments have changed and I have tried to keep the latest assignments. These are the ones I removed: On B737COL: removed as replaced with assignment to SET_THROTTLE1_REVERSE_THRUST_ON 4=RC,0,K82,11 -{Key press: lctl+lshift+R}- 29=RC,0,K113,8 -{Key press: F2}- removed as replaced with assignment to SET_THROTTLE2_REVERSE_THRUST_ON 37=PC,3,K113,8 -{Key press: F2}- On Flight Yoke System: removed as replaced with assignment to Key press: Home 8=PA,6,K32,10 -{Key press: lctl+Space}- Note also that you have two assignments to button 7 on your Flight Yoke System: 9=PA,7,K45,8 -{Key press: Ins}- 10=PA,7,K35,8 -{Key press: End}- so both key presses will be sent when you press this button. This may be ok, if this is what you intended. And you have the same controls assigned to buttons 6 and 7 of your B737COL: 0=PC,7,C66587,68801 -{ROTOR_BRAKE}- 1=PC,6,C66587,68801 -{ROTOR_BRAKE}- and also the same control assigned to buttons 8 and 9: 2=PC,9,C66587,68901 -{ROTOR_BRAKE}- 3=PC,8,C66587,68901 -{ROTOR_BRAKE}- If you get further issues with your assignments now working on start-up, please exit FSUIPC7 and show me your FSUIPC7.log, FSUIPC7.ini and FSUIPC7.JoyScan.csv files again BEFORE doing anything else. Your loss of controls is another / separate issue. When this happens, exit FSUIPC7 and show me the log file. You can also then re-start FSUIPC7 to see if your controllers work after a restart (when you do this, your previous log file will be renamed to FSUIPC7_prev.log) - if not, show me / attach those 3 files again, John FSUIPC7.ini

@dutchkip Also, there are a few issues with your ini file. First, please hcange your profile sections. Change this: to this: This will then catch ALL variants with of the PMFG 737-800 via substring matching. Secondly, your devices keep getting assigned new letters for some reason (looks like your device names and GUIDs have changed), and rather than correcting this you are adding more assignments to the new device letters. I can clean your ini for this, but I need to see your FSUIPC7.JoyScan.csv file. John

Sorry, but the FSUIPC7.log file you attached ends after half a second and shows that FSUIPC7 was still running and not even yet connected to MSFS. I need to se the FSUIPC7.log file from when you experience the issue. Also, please attach your FSUIPC_WASM.log file, from when you experience this issue. Why was this - did MSFS hang? Couldn't you kill it? Is there anything (i.e. an error or warning in the Windows Event viewer related to this? John

The limitation is that FSUIPC7 does not work / cannot be installed on an xbox console. It works on a PC in all versions, including an xbox-pass license. If you want to try FSUIPC7 first, with full functionality, please see John

This is a known issue with the TBM930 and has been reported several times. Please check for existing posts before creating a new one on the same issue. See the following: In summary, the throttle animation was working in earlier versions but seems to be broken since 2022, You can get some movement in the throttle (see first link above), but it doesn't seem possible to have it assigned externally and have the animation correct for all movement. However, I think the throttle IS working, it is just the animation that is broken. So if you want the animation, I think you need to assign in MSFS. John

When it becomes unusual, can you please exit FSUIPC7 and then show me / attach your FSUIPC7.log and FSUIPC7.ini files please. If you get a CTD, please check the windows Event viewer for further information, and show me that and also the FSUIPC7.log file at the time of the CTD.

I need to see your files. The next time the presets stop working, please exit FSUIPC7 and show me / attach your FSUIPC7.log and FSUIPC7.ini files. Also, please make sure that you are using the latest version of FSUIPC7, v7.4.14. There was a bug in the previous versions that could cause the WASM to crash on occasion, which would prevent presets working. The latest version also has the specific offsets for the PMDG 777 activated. John

I think you should be able to use the following area 7C40 - 7EFF: 604 bytes This area is designated as 'Free for general use' in FSUIPC5 and later, so it should be ok for use in FSUIPC4. Let me know if there are issues using this area and I will double check it. John

What do you mean by this? Presets are loaded when you start FSUIPC7, and it was not possible to reload presets until I added this option in the latest release, 7.4.14, so it was not possible for you to reload the MF presets before this. So, please explain your issue, and show me / attach your FSUIPC7.log file generated when you have your issue (and please exit FSUIPC7 before attaching the file). John

You do not have to disconnect it. I asked as it seems that sometimes the steam version of MSFS can create a phantom xbox controller during start-up, which can confuse things. Is you xbox controller assigned in MSFS or in FSUIPC7? It is usually better to assign this controller in MSFS (I use the default assignments) as there are issues with using XINPUT controllers with FSUIPC - you have to use an additional program otherwise input is only detected when FSUIPC7 has the focus. If you are not assigning this in FSUIPC7, maybe better to set this controller to be ignored. I don't think it shows a version on SimMarket does it? I generally release a new version every 4-6 weeks, and all download links point to the latest version. You can download the latest version from the Download section on this site, or use https://fsuipc.com/. Please update. I still need to see your FSUIPC7.JoyScan.csv file so I can correct your FSUIPC7.ini. Please attach this file. John

As I said, the link is fine, so the problem IS with the browser. It must be cached if it is still downloading 7.4.13, as that doesn't exist any more, so double-check you have cleared ALL caches, including the download cache, Also try a hard reload of the page, or right-clicking and select 'Save as...', or another browser.

Strange, as that page has no-cache headers set. What browser are you using? Is it ok after clearing cache? If not, try right-clicking and Save as.

Which link are you using? Both links (in downloads setion of this forum, and on fsuipc.com) point to the same installer, and it is definitely version 7.4.14. If you are getting version 7.4.13, then it is because your browser has cached the previous download. You need to clear your browsers cache, or try another browser.

License sent.

If it says 7.4.13, you are still running 7.4.13. Did it say 7.4.14 in the installer? I expect not, and it may be that you downloaded the previous version as it was cached by your browser. This can happen if you download from the download sections on this forum - either try clearing your browser cache and downloading again, or download from https://fsuipc.com/ which has a no cache directive set.

Your ini is in a bit of a mess - looks like your device GUIDs changed and new letters have been assigned - several times. Can you attach your FSUIPC7.JoyScan.csv file please and I will see if I can sort it out for you. Are you using an Xbox one game controller? Do you knowwhat this device coukd be: ? You are also using a very old and unsupported version of FSUIPC7 - 7.3.21. The latest and only supported version is 7.4.14 - please update.

There shouldn't be any difference between running on Windows 10 or Windows 11. Maybe your USB hub preferences have changed - check the Power Management settings on your USB Hubs and make sure "Allow the computer to turn off this device to save power" is unchecked. Otherwise, please show me/attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look to see if anything is amiss.

Well, never say never... I think first we need to determine exactly what offsets RC4 is reading, and once we know that we can see if we can spoof the values. Could you activate logging for IPC Reads and Writes, and generate a FSUIPC7.log file when using RC4. If you could show me that, that would tell me what offsets its using. Hopefully its only reading and not writing.

From the FSUIPC Lua Plugins document:

Looks good to me!