READ BEFORE POSTING FSUIPC PROBLEM REPORT

[Pete Dowson 293]

Please always post support requests in the main support forum, not in one of the sub-forums, UNLESS your problem is related to the .NET client dll, in which case you should post in FSUIPC Client DLL for .NET sub-forum, or for issues with FSUIPC7-Beta (for MSFS) in which case you should post in FSUIPC7-Beta for MSFS.

We cannot help anyone without any information. Nor do I support old versions. So:

Please always install the currently supported one or later before asking for help. The ZIP package with the Installer available here in the Download Links sub-forum and also over at www.fsuipc.com is the earliest supported version, and there is often a later, interim, update also available in the Download Links sub-forum.

When you are sure you are using the supported version, if you still get a problem please provide the following information:

1. A full description of the problem. Just saying things like "stops", "crashes", "freezes", "stutters", and "unplayable" is no help whatsoever. You must describe what happens -- i.e. what you see on screen and how you detect there is a 'problem'.

2. If there is a crash, then I need to see the Windows crash details -- especially the Module name and offset and the error code. If you forget to read in in the crash message, or it isn't there, check in the Windows Application logs in the Event Viewer. (Search 'Event Viewer' in the Windows Start edit box).

3. If FSUIPC is indeed loading, then it will generate a log file telling you and us what it is doing. This is most important. it is called FSUIPC<version>.LOG (where <version> is the FSUIPC version number, either 4, 5, 6), and is found in your installation folder (which is the Modules folder for FSUIPC5 an earlier). It is a text file and you can attach it to your post.

Also, if the problem is related to joystick recognition or assignment, then attach the file FSUIPC<version>.Joyscan.csv as well.

(Note: Make sure you have turned off the annoying option in Windows Explorer which hides the full filenames from you. Otherwise distinguishing "LOG", "INI", "CFG" and "TXT" files is a pain.)

4. We also need to know if your FSUIPC is registered, and what other add-ons you are using. Also whether it's a default aircraft or an add-on aircraft.

6. Sometimes we may need to see your FSUIPC settings. Those are in the FSUIPC<version>.INI file, again in the installation folder, and yet again another text file.

But generally don't show or send the INI file initially unless you know it's a problem with settings.

 

Thanks,
Pete & John

Edited September 23, 2020 by John Dowson
Updated to cover FSUIPC7