John Dowson

The registration is good up until 8th November. Did you actually try it? Note that, as with the previous key/installer, the installer will not validate a time limited licence. As you the installer installs the key file, you can Skip the registration.

The license expired. You need to download the latest release which contains a new key file (with a license valid for another week) and re-install from that. John

The key file you are using has expired. You need to download the latest release and re-install using that. John

Can you also attach your FSUIPC7.ini file please. What are you starting in your ipcInit.lua? Maybe try without that. Also, if you are still using AxisScanOnSimConnectOpen, then please try without that. John

I suspect that its the control that you are sending is not working in your selected aircraft. There are many controls that don't work, especially for the G1000. But as you are using LINDA, you need LINDA support. I don't use LINDA and can't help with that, sorry.

The price for FSUIPC7 will be 24.99euros (+ applicable tax) or equivalent. There will be an automatic discount of 10euros for FSUIPC5 and FSUIPC6 license holders. No discount for earlier/32bit versions I'm afraid.

The license/key file previously included expired yesterday. The latest installer extends the beta license until 8th November.

The image you posted shows you are using an unregistered version of FSUIPC7 (no Assignments menu entry). Did you install the the key file? Re-run the installer and make sure that you select to install the provided key file, and skip registration. John

You posted in the wrong forum - I have moved your post. No you haven' t as it currently not for sale. To use WideFS with FSUIPC7-beta, you have to use the instructions provided in the beta release note. Your question has also been asked before (yesterday) - please check the forum for similar questions before posting. See

Can you attach your .log and .ini files and I'll take a look. It you have upgraded to windows 10 it is more than likely that you joysticjk ids and/or GUIDs have changed. Should be easy to manually update them, especially if you are using the "JoyLetters" facility.

That will be the last release with a key file included, so wasn't worth updating the manual. The same text should have been in the provided README.txt file, but looks like I prematurely removed it.

You cannot currently use the installer to validate your widefs license as the time-limited FSUIPC7 license cant be validated. You have to follow the instructions in the announcement while still in beta:

Got it working now, after a few attempts. Seems like the cloud syncing was being turned on again and replacing the deleted files, causing the CTD. Looks like the files have now gone from the cloud now so no CTD. The MSFS controllers page shows my devices, but now with no profile assigned at all. My keyboard now also has no profile, and I only have the 'DEFAULT' profile for the mouse. And clicking on any device still shows the mouse assignments!

I found them under ...\Steam\userdata\<my steam id>\241100\remote following the advice in this post: https://forums.flightsimulator.com/t/ctd-after-latest-update-update-5/309576/260. I also disabled Steam Cloud synchronisation, as also advised in that post. However, this does not work for me and I still get a CTD if I have my devices connected or when I connect my devices.

I'm getting a CTD when starting with my devices connected, and also when re-connecting them. I only have "empty" "input profiles", except for keyboard and mouse. This is interesting. Could you let me know the location of these (and if you are using Steam or MS Store version) and I'll see if this works for me. Thanks, John

Hi Achoriham, ok, was just checking how you were reloading, as there are currently know issues with FLT files saved via SimConnect (i.e. autosave files). I just checked a few times saving/loading flights via MSFS, and haven't experienced any issues. Can you download the latest release and try again please, just to make sure that you are up-to-date. Then, if you still have the issue, can you try disconnecting and re-connecting to see if that helps. You could also try activating axes logging and moving your controls to see if these are being logged/sent.

First, you posted in the FAQ sub-forum, where it explicitly states 'Answers to Frequently Asked Questions.. NOT for support requests.'. I have moved your post to the FSUIPC7 as you are asking about FS2020 (or MSFS). FSUIPC7 has an optional add-on WebSocket server component, integrated and included in the installer, provided by Paul Henty, which uses his client dll for .net to communicate to FSUIPC. Details can be found here: http://fsuipcwebsockets.paulhenty.com/ This component will also work with other versions of FSUIPC and so with other sims (P3D, FSX, FSX-SE).

The log is a continuation log and shows nothing. Please send me a full log, do not start a new one. You also seem to be getting a lot of FUEL SELECTOR events for whatever aircraft you loaded. These aren't of interest - you can add this line to the [General] section of your FSUIPC7.ini to prevent these being logged: DontLogThese=65962,66523 Press some keys when FSUIPC7 has the focus first, then switch focus to MSFS and press some other keys. Try standard letters initially, to see if you are getting anything at all.

Hi Dave, no, not seen anything as of yet from Asobo regarding the weather, other than what has been said previously (they're looking into it). John

Different aircraft seem to continually log various events like this. This used to be a problem with add-on aircraft in P3D, where unused events are re-purposed for internal use. With MSFS, they seem to do this with many of the included aircraft. Those events are being used, but I do not know what the aircraft is using them for! If you don't want to see such events, you can use the DontLogThese ini parameter (in the [General] section) - please see the Advanced User guide for details. I think I need to allow this parameter to also be profile specific. I'll look into this. Well, that's because you can't see the events! Its not FSUIPC that's sending these, its only logging them. John

Can you go to Log -> Custom, and enter x400. Then generate a short log file where you reload and have your issue. Also try manually disconnecting and re-connecting after the reload. Attach you logs and I'll take a look when I have time, but even if there is an issue it is very minor with a simple workaround (ie. restarting FSUIPC7). John Later: Ah, sorry - misread your post. The problem is now with reloading a flight, not when you resync. What do you mean by 'reloading a flight' - how are you doing this?

You can use the offset directly. as Thomas has suggested, or you can use the Parking Brakes control, and then add an offset condition for offset 0x0BC8. Offset conditions are described in the Advanced User guide. John

I've just checked these and they should be fine. Are these assignments working for you when MSFS has the focus? They should work when both MSFS has the focus, and when FSUIPC7 has the focus (but not when neither have the focus). If not, enable logging for Buttons & Keys, then press those keys when MSFS has the focus and send me the log and I'll take a look. John

Ok Al, I'll keep in on my 'todo' list and let you know when I get a chance to look at this in detail. John

There are various issues with receiving keys via SimConnect when MSFS has the focus. Please check the MSFS SDK documentation if you want to see what keys are working (although even in this, the numpad keys don't work!). Looking at your assignments, the ones you have to normal keys (D, E, Z, Q, T) should work - have you tried these when MSFS has the focus? For numpad keys, MSFS only sends these when numlock is off (when it should send them when numlock is on). Please see this thread for this: I'm not sure why your F1-F7 aren't working - these should be ok according to the documentation. I'll take a look (when time permits), and look into it or raise with Asobo if this is an issue with MSFS. FYI, this is the current MSFS documentation on key inputs, upon which FSUIPC7 relies to receive these from MSFS: