Pramod Posted June 21, 2020 Report Share Posted June 21, 2020 I am having problem in making FSUIPC6 to work with P3D v5. I have installed FSUIPC6 following the instructions and in P3D I can access FSUIPC GUI but the profiles are not working. Previously, using FSUIPC5 and P3D v4.5 I had profiles of various aircrafts in a sub-folder "Profiles" under the "Modules" folder of P3D and everything worked fine. So after installing FSUIPC6, I copied the Profiles sub-folder to my FSUIPC6 installation folder "C:\Users\mathu\Documents\Prepar3D v5 Add-ons\FSUIPC6". But when I run P3D and open the FSUIPC GUI then the profile of the active aircraft does not show up. So how can I fix this problem please - thanks. Link to comment Share on other sites More sharing options...
John Dowson Posted June 21, 2020 Report Share Posted June 21, 2020 Did you also copy your FSUIPC5.ini to your new installation folder and rename it to FSUIPC6.ini? Could you attach your .log and .ini files and I'll take a look. Link to comment Share on other sites More sharing options...
Pramod Posted June 21, 2020 Author Report Share Posted June 21, 2020 Yes I did. When I open the FSUIPC GUI I can see the name of the profile associated with the active aircraft but the axis and button assignments are blank. I am attaching the INI and Log files - Thanks for your help. Pramod FSUIPC6.ini FSUIPC6_prev.log InstallFSUIPC6.log Link to comment Share on other sites More sharing options...
John Dowson Posted June 22, 2020 Report Share Posted June 22, 2020 I see you are using OneDrive. This may be causing issues Could you try re-installing to a folder outside of your Documents folder. The Documents\Prepar3D v5 Add-ons\ folder should really only be used to hold the FSUIPC6/add-on.xml file anyway. Just re-run the installer and select a different folder (e.g. C:\Prepare3D Add-ons\FSUIPC6). This will also uninstall FSUIPC6 from its current location. You will need to move your files (.key, .ini, .lua, .mcro, etc) and folders across to the new installation location afterwards. Link to comment Share on other sites More sharing options...
Pramod Posted June 23, 2020 Author Report Share Posted June 23, 2020 No, that did not help. However, what I found that for some reason FSUIPC6 changed the assigned letters for some of my controllers (I had "AutoAssignLetters=Yes" in the INI file carried over from FSUIPC5). I have a yoke and a joystick (which I use for the taildraggers and helicopters). So FSUIPC6 switched the assigned letters between the yoke and the joystick. So now I have set it to "AutoAssignLetters=No" and now everything works fine. Thanks for your help. Pramod Link to comment Share on other sites More sharing options...
Pete Dowson Posted June 23, 2020 Report Share Posted June 23, 2020 3 hours ago, Pramod said: So FSUIPC6 switched the assigned letters ... No, FSUIPC follows the GUIDs. Sometimes Windows will assign things differently. This normally only happens after a re-install, but also occasionally because different USB sockets are used. 3 hours ago, Pramod said: So now I have set it to "AutoAssignLetters=No" and now everything works fine. The Autoassigning action operates when a new device (additional ID number and/or GUID) appears, as when you add devices. Pete Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now