John Dowson

Hi Jim, Settings (and profiles) are never lost. When this occurs, it is usually due to one of three changes: 1. The aircraft you are using is not covered by the profile name. This occurs if you are using the full aircraft name rather than a relevant substring, so when the same aircraft but a different livery is loaded, the profile is not loaded. To get around this, you can attach the new aircraft to the existing profile, or, better, use substrings to identify which aircraft should use which profile. 2. The controller in question has been assigned a new ID. When this occurs, the current assignments to that device will not be recognised as FSUIPC detects it as a new device. To get around this problem, you should use the "JoyLettters" facility, which was designed to get around this issue. See the Uset guide for details. 3. Your device GUIDs have changed. This can occur, but usually on only windows upgrades. To get around this, you need to manually edit your FSUIPC .ini file, changing the GUIDs used to assign your devices. Is quite straightforward, but I can assist when this is needed. I suspect that you experienced issue 2, but I don't know without seeing your files. If you can attach both your FSUIPC .ini and .log files, I will take a look. Cheers, John

Updated - sorry for the delay. John

But that would be the same if not using WideFS. There is no difference between using RC directly with FSUIPC compared to using it with WideFS, which is what i thought was your question. Whether RC works with MSFS is a different question. If it relies on the SimConnect_Text API call (or the FSUIPC facilities that use these calls), then there will be issues. See John

Offset 0x3124: The specific version of the FS being used. Will contain 110 for MSFS2020. Set when connected to sim, and contains 0 when not connected, so can be used to determine connection status.

Yes, should be fine via WideFS.

Please see the provided README.txt. You need to re-install the VC++ redistributables. If you check this forum, the same issue has been reported many times.... John

No, you can mix and match. However, we usually recommend to create an empty profile in MSFS first, but you can still assign in MSDFS if you like. Well, many folks using PMDG assign in FSUIPC. However, best not to assign to FSUIPC calibration and NOT calibrate in FSUIPC. it is the calibration that causes issues. That is an issue in P3D, but not so much in MSFS. Just create a new (empty by default) profile in MSFS for the device and you should be fine. You can also assign in MSFS in that empty profile if required. John

Thanks for the contribution. However, isn't this what the Ap Hdg Hold control does (or Ap Hdg On)? The Ap Panel Heading Hold will hold to the AP setting.

Please see my previous comment: Topic closed. John

@rozelcThats great, thanks. Maybe you could create a topic in the User Contributions section, and attach the files there. I am sure they would be useful to many people. Thanks, John PS. If not, no problem - I'll move them there myself, when I get a chance....

This has been previously reported, and the fix was to re-install the VC++ redistributables. Please try that. If you don't know how to do this, instructions in the README.txt, although this has not yet been updated for Windows 11 {see previous comment}.

Requirements for FSUIPC7 are currently Windows 10. I am not looking into any issues reported on Windows 11 until I have upgraded and verified myself. Please be patient. John

Yes, but I think I removed the Alt modifier in FSUIPC7 due to other issues, but I'll check.

I haven't checked compatibility of FSUIPC7 with Win 11 yet. The current requirements of FSUIPC7 are windows 10. I will look into Windows 11 compatibility shortly. Until I do this, Windows 11 is not supported, and you are on your own. I cannot look into these issues until I have checked and approved Win11 compatibility. I hope you understand. Please be patient. I will inform when compatible. John

Btw, for the time being, you can just re-assign the keypress in MSFS and not use the right ctrl (or shift) keys.

You can do this but it will have to be manual, i.e. let the installer install the WASM in your Community folder, then move it manually and create your shortcut/link. However, you may be netter off using one of the free utilities that manages your add-ons, e.g MSFS AddOn Linker: see Note that only the FSUIPC WASM modue goes in the Community folder, you can already install FSUIPC7 itself in any location. John

Hi Al, yes, this is something I can look into for a future release. I'll take a look next week to see what is needed {currently away from home} and get back to you. Presume this also applies to key stroke assignments - I believe SimConnect already distinguishes between left/right keys, so it shouldn't be an issue. John

@StallSpinCrashNBurn Sorry for not updating the license as of yet - i completely forgot.... I'm travelling now and don't have access tohe keygen system at the moment, so I'm afraid that the earliest I can now provide a new trial license will be 11th/12th October. @izzizahari Sorry but you will also have to wait until Monday night/Tuesday morning as well.

You log shows that DSUIPC7 exited as MSFS closed down (probably CTD'ed): You should have a crash event in the Windows event kig, and maybe an MSFS crash dump file. You can report this to Asobo, attaching the crash event and dump log, it you have one. One thing you could try is to increase the number of SimConnect client connections, although I don't think it will solve your issue, but it doesn't do any harm. Increase the maxClients parameter in your SimConnect.xml file to 128. Idf you are nut sure how to do this, check this forum as there are several posts explaining this already. John

No idea what that could be - the link you pasted works fine here. You can try this one instead: Install FSUIPC7 John

Why are you running FSUIPC7 with administration rights? That is not necessary and shouldn't be needed. Where have you installed FSUIPC7? Make sure that it is not installed in a Windows protected folder, such as Program Files. Can you start MSFS (and also FSUIPC7 if not auto-started), let it load, select and aircraft and get ready-to-fly, and then exit, and show me your FSUIPC7.log and FSUIPC7.ini files. Thanks, John

How are you assigning these? Can you attach your FSUIPC7.ini file. Also, produce a short log with logging for Buttons & Keys as well as Events activated showing your issue and attach your FSUIPC7.log file. Also, if the issue started after the FBW A320 update (which version?), you may be better of asking on the FBW discord channel (https://discord.com/channels/738864299392630914/738864300818432023). John

I'm not sure, sorry. Its been many years since I messed around with camera views, although its something thats been pending on my flight system now for several months. I'll be looking at this shortly, but in P3Dv5 which I still need to configure correctly for my system. Maybe others more familiar with camera configuration could comment. John

Maybe they still need a unique GUI? Most tutorials on the web (e.g. http://www.ontheglideslope.net/2016/05/18/how-to-creating-custom-cameras-in-prepar3d-v3/ - for P3Dv3 but still valid): Also check that your button/key assignments to the views are still valid/active for the different a/c. John

Please attach your fsuipc.ini file, not a photo of the screen. Also please activate logging for events and axis events, and generate a log file where you move the lever to the armed position, then exit, and attach the log file as well.