John Dowson

Can you please check existing topics where solutions can be found rather than repeatedly posting the same questions. I am closing this topic.

That's good to know! Shame about the FPS drop/SimConnect issue, hopefully it will be fixed soon. John

Which SimConnect.dll are you using - the one from the MSFS SDK? If so, are you sure that it is located in the installation folder, next to the FSUIPC7.exe? If you are using the correct dll, (and not a 32-bit version from another SimConnect SDK), then please see https://ugetfix.com/ask/how-to-fix-application-unable-to-start-error-0x000007b/

This seems to be a known problem with the released version of the SimConnect library, which wasn't present in the beta build. It affects all SimConnect clients, including FSUIPC7. It has been reported to MSFS/Asobo. I'll update when I have further information. John

Yes. First you have to activate developer mode and then download and install the SDK. You'll find the dll in the SDK installation. See https://forums.flightsimulator.com/t/how-to-getting-started-with-the-sdk-dev-mode/123241 John

See:

Sorry, I don't know. I don't have the released version yet. MSFS said that it would be included in the release version, but I don't know where or how to access. I assume there would be an msi installer file somewhere for the SDK. Hopefully somebody will post details when found.

Please see John

I am closing this topic now. I'll post in the Announcements later today. We'll also create a specific sub-forum for MSFS/FSUIPC7 questions and feedback. John

Sorry, but I'm not going to give details on specific functionality for the time being. Please see the provided documentation when released (later today). As this will be a beta release, we would like feedback to determine the actual status of a lot of functionality.

This has already been updated. John

You can zip it - it should compress pretty well.

Hi Vic, Most settings should be compatible, so you can rename an existing FSUIPC4/5/6.ini to FSUIPC7.ini to preserve your settings. However, this does not mean that everything will work, as many of the events/controls currently have no affect (and there is still not that much documentation on what is and isn't working in this area), and some offset functionality has been removed. For example, if you have a hat switch to control view panning and/or slewing, this will not work and would have to be assigned in MSFS. Also, masking of keys/events isn't working, so if you have these assigned in FSUIPC7 then you will need to ensure that these are not also assigned in MSFS. As for profiles, they should also work in the same way. You may need to re-assign your profiles to the MSFS aircraft though, if the strings/substrings you use don't match the MSFS aircraft names. John

No, it will be specific to MSFS. offset 3308: I'll set this to 13 offset 3124: 110 John

Sounds like a good work-around to me!

Initially it will be available from Download Links - Updated Modules section here, and also over on www.fsuipc.com. At some point it will also be available over on SimMarket, but not sure yet if this will be ready for the 18th.

This is still on my to-do list. Unfortunately, with the release of P3Dv5 and the upcoming MSFS release, I haven't had time to look at this yet, and don't expect to get around to this until the problems with MSFS/FSUIPC7 have been resolved. I will get around to this at some point though...!

You need access to the MSFS SDK to use FSUIPC7 (for the time being at least), so unless you have 'third party dev' privileges you won't be able to use FSUIPC7 until the 18th I'm afraid. Probably not worth requesting this at such a late stage. At some point, there will be an SDK update so that the dll is no longer required. John

Yes

As FSUIPC7 will initially be released as a beta version (with a free time-limited license), it won't include full documentation on what is and is not working. I'm currently looking at providing some documentation, based upon the current MSFS SDK documentation. For offsets, this will include what is the current read/write status (according to the MSFS SDK documentation of the related sim variable) of each offset, together with the previous status of that offset (from FSUIPC6), so that users can see what has changed. For events/controls its more complicated, as even though the latest SDK documentation includes a list of accepted events (which is what the event/controls list in FSUIPC7 will be based upon), many of these events currently have no affect. For example, so far I have not found any events for controlling views (including panning) that have any affect. There are various SDK updates planned for MSFS in August/September, after the official release on the 18th. Hopefully these will address some of the issues we have with the current state of the SimConnect API. However, I don't think I'll be able to release anything before the 18th. John

You can also change the behaviour of FSUIPC6 to not use Dialog Mode by adding the following to the [General] section of your FSUIPC6.ini file, although this is not recommended: UseDialogMode=No John

This is normal behaviour - looks like P3Dv4 blacks out the screen when in dialog mode. This looks like a recent(ish) change (in P3Dv4). This is not the case as you define the mouse macro once you have closed the FSUIPC UI. I can't think of any functionality (in FSUIPC) that this prevents you from using.... Its also the same behaviour as P3Dv5. John

I've no idea. The developers would need to test this with FSUIPC7. If they are not on the MSFS third-party developer list (i.e. they have access to the MSFS SDK), then they can't test until they get access to the SDK, which will be included with an MSFS license. John

Yes. I will release a beta version of FSUIPC7 for MSFS on the 18th. I'll post more details in the Announcements section before the 18th. John

You should update to 6.0.10. Can you take a look in the 'Event Viewer' (a standard Microsoft utility, should be installed)). Look under Windows Logs -> Applications, and see if there is an error report there for WideClient. If so, please post the details. Thanks, John