John Dowson

As part of the process to find out what is causing this issue, you need to remove add-ons and add them back one at a time. But it is not possible for FSUIPC yo cause MSFS to CTD. FSUIPC is a separate application and only communicates with MSFS via the SimConnect API.; I have had hundreds of reports claiming that FSUIPC is causing MSFS to CTD, all false/incorrect. There are already quite a few similar reports on the Asobo forums, so you should check those out. For example: https://forums.flightsimulator.com/t/sim-still-crashes-ctd-when-changing-checking-control-options/653525 https://forums.flightsimulator.com/t/ctd-when-saving-control-profiles/679884 https://forums.flightsimulator.com/t/changing-control-presets-causes-ctd/678112 https://forums.flightsimulator.com/t/ctd-by-adding-controller-or-other-device/487164/3 If you find what is causing this issue, please update here - it may help others and save me some time.... John

Hi Luke, I don't have any aircraft that use the [VARIATION] section (with a relative path), so cannot really check this. As you have done this, maybe you could add this information to this bug report: https://devsupport.flightsimulator.com/t/simconnect-requestsystemstate-aircraftloaded-returns-partial-path-of-aircraft-cfg/9041/6 Better to not mention offsets or FSUIPC - just refer to this as the data returned from the AircraftLoaded event. You can use the attached version (and enable logging for Extras) which will log the actual parameter received. Or you can attach the log file here. John FSUIPC7.exe

How do you know that this was due to a WASM crash? And if you think that this is a WASM crash, you should attach your FSUIPC_WASM.log file, preferably generated with Debug logging enabled. There really isn't any point posting to complain about something if you are not going to back this up with information so that I can investigate. Have you disabled continual scanning for lvars, as this is the cause of the WASM crash as documented in the FAQ entry for this. If you have not read that entry, please do so now and disable lvar scanning. If you have already done that, then I need to see your FSUIPC_WASM.log file. And if you don't know where that is, consult the documentation.

Just checked this and I see the same in those offsets with 7.4.17 and 7.5.1: i.e. there is no change, I don't understand why the first airport at offset 0x0640 is EGLL though and not EGTF, the first airport at offset 0x0658 (the plane was in a runway at EGLL). Have you tried monitoring those offsets to see what has changed? Also check that you have the GetNearestAirports ini parameter set to Yes,

7.5.1 is 7.5.0.1 - I combine the last 2 digits for the text version (so 7.4.18 is 7.4.1.8) %USERPROFILE%\Document But what is the value of the Personal key under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders? That is what FSUIPC uses, and if that is not set correctly it will not install correctly.

Your log shows the flaps lever is sending the correct controls when you move it through its range: So FSUIPC is sending the controls as expected, but if it is not going into the 0 or 40 position, then it looks like those controls are not working as expected (although they are being sent and applied in the FS). I am not sure why. To test this, can you assign a spare button or key (or key combination) to the flaps 0 and flaps 40 custom controls (76773 and 76781) to see if they actually work. If not, then it should be reported to PMDG, You could also try assigning the flaps 0 and flaps 40 range positions to the EVT_CONTROL_STAND_FLAPS_LEVER custom control instead (70346). I am unsure of the parameter needed though - try either 0 or -16384 for flaps 0, and either 16383 or 32767 for flaps 40. And you could also try assigning the 0 and 40 ranges to the Axis Flaps Set control, with a parameter of -16384 for flaps 0 and +16383 for flaps 40.

You should consult the user manual for such basic information... The FSUIPC6.log file will be located in your FSUIPC6 installation folder. Did you try FSLabs support? As the issues started after an update to this aircraft, you should really be talking to them, not me. John

No. For MSFS CTDs, please use the Asobo forums - this is nothing to do with FSUIPC and I can't really help with this, sorry You could start here: https://forums.flightsimulator.com/t/how-to-troubleshoot-ctds-on-pc/591659 John

I only support the latest version of each product. 7.5.x is not just an update for MSFS2024 - it also contains changes for MSFS2020. You can continue to use 7.4.18 if you like, but it is unsupported and I will not look into anything reported with old versions. John

There have been no changes to FSUIPC in this area, but I will take a look when I get a chance - this may take a couple of days as I am quite busy,,. In the mean-time, could you try the attached version, 7.4.17, to see if they still function in this version, FSUIPC7.exe

You are using an old version of FSUIPC (7.4.18), Only the latest version, currently 7.5.1, is supported. Please update., John

No Pete retired over 5 years ago and no longer provides support. Sorry but I cannot understand this... I do not support SIOC, so cannot help with that. Is WideClient connecting to WideServer? From your logs, I suspect not. If WideClient is not connecting, please see the documentation and follow the 'Configure your Network' section in the User guide. Check your WorkGroup name is the same in both PCs, try with firewalls disabled (client, server and router)m and try adding the ServerName (or ServerIPAddr) and Protocol WideClinet ini parameters, See the documentation. I get hundreds of reports of wideclient connection issues after a windows update. All such issues are due to the update causing changes to the network configuration which you need to identify and correct. All issues that can cause such issues are documented, so please check the documentation, and maybe one of the many threads here from others who have the same issue.

You can download all versions of FSUIPC from https://fsuipc.com/. Your license details will be available from your SimMarket account - there is no need to re-purchase.

Of course you can move your Community folder anywhere, The FS Installation location in MSFS2020 (and MSFS2024) held in offset 0x3E00 is the InstalledPackagesPath value from the usercfg.opt file. Why don't you just take a look at it?

Well, that thread is this thread, and that post is for setting the trim on keys, not buttons. But you can assign your buttons to those controls - that is basically the same assignments you are using for the trim wheel (virtual) buttons).

It is not confusing FSUIPC7. it is confusing MSFS. Offset 0x3C00 is populated from the path received in the 'AircraftLoaded' system event, If it is wrong for variants, then it should be reported to MSFS. I can take a look next week to see if I see the same issue and if so will report this, but I don't think there is much else I can do. Cheers, John

The Community folder should be under 'Flight Simulator installation' folder held in offset 0x3E00,

But I just don't understand why you are posting at all... There ini file is there - you attached it, and it is the one with the type 'Configuration Settings'. The log file is there, and with the type 'Text Document'. You cannot see the extension because you have Explorer set to 'Hide extensions of known file types', If you want to see the extensions, then uncheck this option. This is all documented. This topic of this post is 'Shouldn't I have an .ini file?'. The answer is yes - and you do. It is first created when you run FSUIPC7. I really have nothing more to say on this topic so I am closing/locking it now. Please consult both the documentation and these user forums for any issues before posting,

You have controllers set to on in P3D: If assigning in P3D, you should disable controllers in P3D. Your log file only shows FLAPS_SET and AXIS_FLAPS_SET controls (and custom control 85637) - it does not show any of the PMDG flaps custom controls. And the parameters to these controls look to be setting different positions.... So, please disable controllers in P3D (or at least remove any assignments to your flaps lever/axis) and try again, and attach the new log as well as your latest FSUIPC5.ini file. The one you posted before doesn't look quite right - most of the JoystickCalibration ini parameters are missing for some reason.... Can you also please set logging for Buttons & Keys - maybe be necessary to see the range controls being sent...

Does FSUIPC7 run ok? Can you add assignments, and when you run FSUIPC7 the next time are they still available (i.e. have been preserved/saved)? If so, you have no issues and there must be a FSUIPC7.ini and FSUIPC7.log file. If you have any issues, please report them and show me / attach your InstallFSUIPC7.log. If the log and ini files are generated, you can also attach them (if you have issues). If they are not generated, then try running as admin. If they are then generated, it will be a permissions issue on the folder that you installed into.

Did you read the documentation? I am sorry but I provide documentation so that I don't have to answer such questions - I even told you where to look... From the documentation: Your image shows that this is still checked. Before you post here, please: - check the documentation, - search these forums to see if your question has already been answered

See https://devsupport.flightsimulator.com/t/simconnect-requestsystemstate-aircraftloaded-returns-partial-path-of-aircraft-cfg/9041/6 John

Do you mean in offset 0x3C00? What is the value in that offset, and which aircraft are you using? Could you add logging for that offset and show me the FSUIPC7.log file. Note that this should be the full path name but sometimes its a relative path (reported to Asobo several years ago, but I haven't checked this for a while). This also may not ne available/correct for encrypted aircraft, Yes, as the documentation says for this offset: ICAO Designator: Read from aircraft.cfg file (only available when 0x3C00 contains the full path to this file) So it looks like MSFS is just not returning the full path of the aircraft,cfg file for the aircraft you are using. Its even worder in MSFS2024 now aircraft are streamed... Cheers, John

No - is there a simvar (or anything else) that holds this information?

No - it is the same application for both versions. This is created the first time you run FSUIPC7. You have no FSUIPC7.log file either, so it looks like it hasn't been ran yet. But you also need to change your Explorer settings to see the extensions of these files - please see the Addendum on the last page of the Installation and Registration guide.