John Dowson

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

No - for FSX, you need FSUIPC4, not FSUIPC3 (again, assuming by FSU you mean FSUIPC). As Pete advised, you will need to try this to see if works (with FSUIPC4).

Hi Stefan, I don't know! FSUIPC doesn't really support force feedback directly - from the user manual: However, it is possible that some FFB systems are driven by the FSUIPC offsets. You need to check with the software provider if this is the case. If it does use FSUIPC offsets, then whether it works or not in MSFS would depend on which offsets are used and whether they are populated in FSUIPC7/MSFS. John

Hi Joe, no, sorry - there is no offset for GPU memory. You could also try the "game bar" performance meter - windows key + G (Widget menu -> Performance) John

It's a bit more involved than that. I can't really say anymore due to the NDA. I'll post an announcement on MSFS/FSUIPC on the 18th, and try and include information on what we know isn't currently working, either due to facilities now working or currently not available in MSFS, or due to not yet being implemented in FSUIPC7. John

The increment and decrement controls for aileron/rudder trim are still available, its just the axes controls that are (currently) not available for assignment. What makes you think this? Saitek device compatibility for MSFS/FSUIPC7 is the same as for FSUIPC6/5/4, i.e. yoke and throttle should be recognised and assignable but you would need SPAD or SPAD.next (or maybe lua) for radio panels, multi-switch boxes, etc. John

The reason for this is that there are currently no facilities to access lvars in the MSFS SDK (i.e. no panels access). We have requested such facilities, and if/when provided, the relevant lvar functions will be re-instated.

The LUA interface will be available. Some functions will no longer work and will be removed (e.g. lvar access) , but the majority should be ok. I don't know about LINDA. John

Its currently only available to MSFS third party developers due to restrictions on SDK access.If you are an MSFS third party developer, check the MSFS forum for details on how to access.

Your registration details work here, although I have not tried to register via the installer. I've PM'ed you a key file. Please try that. If you have a WideFS license that you wish to add (using the same name/email), then you can add another line with your WideFS key as follows: WideFS=your 12 digit WideFS key John

It will not be possible to add menu items to the sim. I will add a facility to add a menu item (possibly with submenus) to the FSUIPC7 menu bar (via the dll mechanism and offset 2FE0), but this functionality may not be available upon initial release. John

Generally yes, but with a few changes: - no ALT modifier for key assignments, no masking of key assignments (due to SDK issues) so you need to ensure the key is not assigned in the sim - key assignments function when MSFS has focus AND when FSUIPC7 has focus - the following axes are no longer available: KEY_AILERON_TRIM_SET, KEY_RUDDER_TRIM_SET John

Yes. I will post again with updated information when we hear anything.

No. That doesn't use a 64-bit SimConnect.dll. It uses the old 32-bit SimConnect.lib. We can't go back to 32-bit. John

Please see FSUIPC460Francais John

I think they are actually parameters to the Rotor Brake control, which has been re-purposed in the FSLabs A3xx aircraft.

How have you assigned your axes? In FSUIPC or in FSX? If the former, please show your FSUIPC4.ini file. Have you changed your "default assignments? Are you not using "profiles"? Strange. That screenshot (pretty useless as it is) just says that your axis aren't being processed by FSUIPC. I'm sure you haven't. Don't worry, it's probably something simple that you've missed. But, before we can help, you need to provide further information: - your FSUIPC4.ini and FSUIPC4.log files - more information on what you actually did. I'm sure that you didn't just install the aircraft and then try and calibrate. Did you assign? Are you using profiles (again) [and if not, why not?]? And if you uninstall, and your FSUIPC.ini file hasn't change, it can't possibly affect other aircraft. Have you changed the "default" (i.e. valid for ALL aircraft) assignment profile? John

Please see the link in the post previous to yours. I am locking this topic. John

I don't know. Really, everything should just work when using OneDrive. I have used OneDrive for FSUIPC before without issues. I started to get issues as I use FSUIPC on multiple PCs, sharing the OneDrive account, and I did not want these different installations to share the same add-on.xml. They don't. They select your Documents folder. The location for this is determined by the registry. I'm not sure how OneDrive works, whether it updates this location. or if it acts 'under-the-covers' and silently keeps your docs in sync to OneDrive. Either way, I think there are some issues with your OneDrive set-up, as it really shouldn't interfere with the installation process. No problem. Glad its now sorted. Happy flying! John