Thierrynach Posted January 29, 2015 Report Share Posted January 29, 2015 Hello Peter Registered user since long years, I just bought the version of FSUIPC to P3D. Unable to register the software. The installation went normally. I agree with my license but the software remains freeware version. I tried everything and nothing changes. What should I do? thank you Thierry nachtergaele Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 29, 2015 Report Share Posted January 29, 2015 Hello Peter Registered user since long years, I just bought the version of FSUIPC to P3D. Unable to register the software. The installation went normally. I agree with my license but the software remains freeware version If you were already registered for FSUIPC4 with FSX, why did you buy it again? It's the same version of FSUIPC4 which deals with both FSX and P3D! Maybe you registered originally for FSUIPC3 which is different, for FS9 and before? Pete Link to comment Share on other sites More sharing options...
Thierrynach Posted January 29, 2015 Author Report Share Posted January 29, 2015 (edited) Pete, Thank you for the response. I have a version of FSUIPC registered for FS9 but on another computer. My purchase is for a new machine with P3D. I do not have FSX on this PC just P3D. Pete, I found the problem but I do not know how to solve it. Here's what happens. I use TILEPROXY for landscapes in P3D. To use TILEPROXY with P3D just rename the file prepard3d.exe in FSx.exe. My folder "prepar3D" so I have two files (prepard3d.exe and fsx.exe) are the same. It is a ruse to fool TILEPROXY which does not recognize the prepard3D.exe file. If I run PREPARD3D.EXE then FSUIPC is OK and my license is recognized. If I run FSX.exe FSUIPC is unregistered versions. I checked in the "modules" folder Prepard3D and there are two FSUIPC file that changes the .EXE I open. FSUIPC4.FSX.LOG FSUIPC4.FSX.INI and when I open FSX.EXE and FSUIPC4.P3D.LOG FSUIPC4.P3D.INI and when I open PREPARD3D.EXE That's why I can not have a registered version when I run FSX.exe file that is actually the renamed file PREPARD3D.exe in FSX.exe for TILE PROXY I put the following 4 files in the "module" folder P3D FSUIPC4.P3D.ini, FSUIPC.P3D.log, FSUIPC.FSX.log FSUIPC.FSX.ini and all but it's crashing P3D has finished loading. There is only one simconnectP3D2.dll file in the module folder What can I do? thank you Thierry France Edited January 29, 2015 by Thierrynach Link to comment Share on other sites More sharing options...
Pete Dowson Posted January 30, 2015 Report Share Posted January 30, 2015 To use TILEPROXY with P3D just rename the file prepard3d.exe in FSx.exe. My folder "prepar3D" so I have two files (prepard3d.exe and fsx.exe) are the same. It is a ruse to fool TILEPROXY which does not recognize the prepard3D.exe file. These sorts of fiddles are a big cause of pain and problems! The thing is FSUIPC needs to recognise what it is running with! I checked in the "modules" folder Prepard3D and there are two FSUIPC file that changes the .EXE I open. FSUIPC4.FSX.LOG FSUIPC4.FSX.INI and when I open FSX.EXE and FSUIPC4.P3D.LOG FSUIPC4.P3D.INI and when I open PREPARD3D.EXE It would have helped more if you actually showed me the log files -- that's why log files are always produced, to provide information to solve problems! I understand the first files with the extra " FSX" part. That means it recognised that you'd renamed Prepar3D to FSX. This action is documented. It also means that you need to make a copy of your FSUIPC4.KEY file, renamed the same way ... i.e. FSUIPC4 FSX.KEY. However, I completely fail to understand why you also have files with " P3D" in the name! That can only happen if you also have run a copy of Prepar3D renamed rto "P3D.exe"! Have you also done that? Why? If you have you need another copy of FSUIPC4.KEY renamed as FSUIPC4 P3D.KEY. Please refer to the FSUIPC4 Advanced User's document. The section "Muliiple INI files" on page 48 explains. Pete Link to comment Share on other sites More sharing options...
Thierrynach Posted January 30, 2015 Author Report Share Posted January 30, 2015 Hello Pete Thank you for your response. I understood thanks to your indications. I renamed the file FSUIPC.Key in Fsuipc.FSX.KEY and everything works. :razz: A thousand thank you for your help. beautiful day Thierry 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