John Dowson

Hi Tom, where does it say that it is a 'Beta copy'? There is no such thing! Version 5.121a is an interim version and is out-of-date (not supported) - please download and install version 5.15, which is the latest version of FSUIPC5. There are only registered and unregistered versions (and no expire date!). The 'About' tab in the FSUIPC5 main window will show if the copy is registered or not, and the FSUIPC5.log file will log the registration check (when you start P3D). What does this say? Cheers, John P.S. For future reference, could you please use a more useful topic....'FSUIPC' doesn't say much, 'FSUIPC registration query' would have been better! Thanks.

Hi Luke, I can confirm that 0628 does indeed remain zero. However, looking at the offsets document, this is defined as 'No' for both read and write, i.e. Not Supported. I guess it could be added, but I am not sure this is worth doing anymore now that offset 3402 contains the more detailed mode info. Cheers, John

WideClient is available from the 'Download Links'->'Updated Modules' page:

Hi Luke, I'll take a look at offset 0628, but I think you are better off switching to use 3402. You cannot disable the use of the PDK now, since version 5.14 (see note 18 of the 5.14 release note). Regards, John

The 'Miscellaneous' tab is one of the tabs in the FSUIPC main window. Are you using FSUIPC, or is this a general P3D question? This is the FSUIPC support forum. If your question is about P3D then best to post in their forums. Regards, John

Hi Don, you can connect your USB devices to your client computer and connect using WideFS. This will generally be fine for buttons/switches/toggles, etc, but for axis controls (throttle, elevators, ailerons, rudder, etc) you may find the added delay (due to the network) gives poor response times. Anyway, Pete will be back next week so please wait for his opinion before you splash the cash! Regards, John

Hi Luke, there were some changes in the way the sim mode is derived that were introduced in FSUIPC v5.15. See note 5 in the 5.15 history document. There were also some changes in the use of offset 3365 (which is the 'in-menu' or 'dialog' flag) in v5.14 (please also see History document for details) The sim mode is now taken from the PDK and stored in offset 3402 as a bitwise flag. Please check the offset status document for this offset. There is no change in offset 0628 - this should still be 1 when in instant replay mode and 0 when off. Cheers, John

Hi, if your original problem is fixed and this is a new problem, could you post a new topic please? Please also post your FSUIPC5.ini file for assignment issues. Are you using profiles? As mouse-macros are aircraft specific, they should really only be assigned to a profile. Cheers, John

Hi, unfortunately it is difficult to tell what is in the attached image, but yes - the 'Previous Flight' should be visible in the 'Load Scenario' dialog box. I am not sure why the 'Previous Flight' is not visible, if it is there and visible in the 'Save Flight' dialog box, it should also be in the 'Load Flight' one.... You could try activating the 'Provide menu entry for flight loading' option, in FSUIPC's 'Miscellaneous' tab. This will give you an extra 'Load Flight...' menu option in the 'Add-ons' drop-down. Use this to navigate to your saved flights directory (usually in the Documents/Prepar3D v4 Files directory of the user account - this should be the default) and see if you have the 'Previous Flight.fxml' file there and try and load that. Cheers, John

Hi Maksim, could you please also post your FSUIPC5.ini and FSUIPC5.JoyScan.csv files please, both also located in your Modules folder. Thanks, John

Just re-run the installer (or download the latest version first). Please cut and paste your registration details (name, email address, registration key) from your SimMarket license/registration email (you should be able to retrieve these from your SimMarket account if lost). What do you mean by 'I have key file data but FSUIPC does not accept it'?

You edit the file and add the [AUTO] section.

Hi, no attached pictures, only the install log. This shows one strange error: The attached install log shows you were installing 5.15 over 5.15, so it looks like you are re-installing the same version, no? Did you have the user guide open at the time by any chance, which prevented it being installed on this run? As to your registration problems, more info is needed. Have you previously registered (and have a valid key file in your Modules folder)? If so, you can skip the registration process and the existing key file will be picked-up when you start P3D/FSUIPC5. Otherwise, what happens when you try to register? Also please remember to copy and paste your registration details from you registration/purchase email. Regards, John P.S. For future reference, please try and use a more appropriate topic/subject for support requests. 'FSUIPC' doesn't really say much - 'FSUIPC registration problems' would have been better! Thanks.

As spokes2112 says, this is not an efficient way run such a large lua file. Each time you call this, it has to create the thread and compile the lua script before it runs. It would be more efficient to have the lua auto-started (and compiled!) and activated on an event flag. You can also consider breaking the script down into multiple smaller files. Cheers, John

No news of this as of yet. It is something that will be looked into in the future, but at the moment this is low priority so nothing for the time being. Regards, John

This is how it should look. Your assignments/calibration will now use the letters, but the numbers still appear in the JoyNames section to enable the mapping of the numbers obtained in the scan to the letters via the GUIDs.

Looks like your registry is in a bit of a mess and needs cleaning. The first thing to try to do this is: Disconnect your devices Uninstall the devices from the device manager Reboot your PC. Re-connect your devices - let windows install the default device drivers Start P3D. Once this is done, post the log, ini and joyscan csv files again please.

Hi, could you post the lua script please?

No, sorry - not heard of MobiFlight before. Just googled it though and it looks interesting...

Sorry, just posted a possible solution when I noticed the GUIDs for your two devices are the same! Can you post your FSUIPC5.Joyscan.csv file please?

You need to convert the decimal value to hexadecimal, so 4976 = 0x1370 which would correspond to a frequency of 113.70 (BCD format). Hope that helps, John

Hi, looks like your stick and throttle have both been assigned a joystick id of 1. You will need to change the id of one of the devices by following the steps Pete posted in this recent thread: Cheers, John

By the way, the key file should be in J:\Lockheed Martin\Modules and not 'J:\Prepar3d\modules' as mentioned....

Hi Erwan, the log file shows the mouse macro is being activated ok. There are a few things you could try: 1. Duplicate your macro file (giving it another name), and in the second file change the left mouse-click code (3) to a left release (13) [P38 of Advanced User Manual]. Then assign this macro to the key release. 2. Instead of using two macro files (as above), you could edit the existing macro to contain both the left click and the release - see the section entitled 'Multiple actions in one macro control' P37 of advanced user manual. 3. If the above two fail, add event logging to see whats being sent when you both click and release with the mouse in the sim. Cheers, John

Hi, did you try starting P3D and checking if FSUIPC is registered? If you key file is still in the modules folder it will check the registration when you start P3D.