Problem registering 4.931

[Arismac]

G'day Pete,

 

I have tried several times to install and register 4.931. Each time the registration appears to fail. My next move is to try purchasing a new License but thought I had better check with you first.

 

I only have P3D v1.4 on my G:/ drive and P3D v2.2 on my E:/ drive. The issue first appeared after I installed the "Black Box" edition of the Airbus into P3D v2.2.

 

I also perhaps should have said that I am running P3D v2.2 from an LM hack "AFR-FriendlyD3D.exe" file in order to enable SLI.

 

Cheers,

Mac

 

EDIT:  When I run P3D v2.2 from the "Prepar3D.exe" file FSUIPC 4.391 is showing as registered. So it looks as though LM have tricked us again. Currently SLI and FSUIPC do not seem to be compatible.

 

[Pete Dowson]

I have tried several times to install and register 4.931. Each time the registration appears to fail. My next move is to try purchasing a new License but thought I had better check with you first.

 

I only have P3D v1.4 on my G:/ drive and P3D v2.2 on my E:/ drive. The issue first appeared after I installed the "Black Box" edition of the Airbus into P3D v2.2.

 

I also perhaps should have said that I am running P3D v2.2 from an LM hack "AFR-FriendlyD3D.exe" file in order to enable SLI.

 

If you use an EXE with a different name, then all of the FSUIPC files also use a different name. This is a facility used to enable different configurations to be used with one install, which is what FSUIPC assumes you are doing.

 

Look in the Modules folder. You will see FSUIPC4.INI, FSUIPC4.LOG and FSUIPC4.KEY. Those files are only used if you run the proper Prepar3D.EXE. You may also see another .LOG and another .KEY which include the name of the other EXE. You will have to make a copy of your KEY file and rename it in a similar fashion.

 

Pete

[Arismac]

Thank you Pete, I will try and follow instructions. I should say that I am not the only one that will be affected by this as a number of people are accepting the option to run P3D v2.2 in SLI mode, which I must say is a huge performance boost.

 

Mac

 

EDIT: OK got it, sorry a bit thick this morning. Thanks again, Pete.

[Pete Dowson]

I should say that I am not the only one that will be affected by this as a number of people are accepting the option to run P3D v2.2 in SLI mode, which I must say is a huge performance boost.

 

Why not just rename AFR-FriendlyD3D.exe to Prepar3d.exe? Or does that new file in turn need to load the original EXE?

 

Pete

[steppy1982]

I Have the same problem. I have done everthing after the guide.. I have checked  that my .key-file has the same name as the .ini,  .log and .exe but still no luck.(AFR-FriendlyD3D) My registration is valid in regular prepar3d.exe but not with AFR-FriendlyD3D.exe

 

Hope you can help with this.

 

Stephan.

Edited April 27, 2014 by steppy1982

[Pete Dowson]

I Have the same problem. I have done everthing after the guide.. I have checked  that my .key-file has the same name as the .ini,  .log and .exe but still no luck.(AFR-FriendlyD3D) My registration is valid in regular prepar3d.exe but not with AFR-FriendlyD3D.exe

 

It isn't the same problem, then!

 

Please show me the actual log file. Is there a Prepar3D.exe as well as this one with the strange name?

 

Pete

[steppy1982]

Hello!  thanks for your response. Yes i have the regular p3d.exe in my game dir. My FSUIPC4.AFR-FriendlyD3D.exe.log looks like this:

 

********* FSUIPC4, Version 4.931 by Pete Dowson *********
Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.AFR-FriendlyD3D.exe.ini"
Running inside Prepar3D v2 on Windows 8
... Prepar3D has been renamed as "AFR-FriendlyD3D.exe"
Module base=58180000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
       31 System time = 28/04/2014 16:22:06
       31 FLT path = "C:\Users\Stephan\Documents\Prepar3D v2 Files\"
       31 Trying C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\SimConnectP3D2.dll
       31 Found it: trying to connect
       31 FS path = "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"
      344 LogOptions=00000000 00000001
      344 ### Failed to obtain SIM1 Frictions access: no frictions facilities available!
      344     Reason 6: SIM1 base=595F0000
      344     FrictionAddr=596F2E50 contains 5960F7E0
      344     BrakingAddr=596F4110 contains 9999999A
      344 WARNING: Failed to install Mouse Macro hooks!
      344 Wind smoothing fix is fully installed
      344 SimConnect_Open succeeded: waiting to check version okay
      344 Trying to use SimConnect Prepar3D
     2047 Running in "Lockheed Martin® Prepar3D® v2", Version: 2.2.10437.0 (SimConnect: 2.2.0.0)
     2047 Initialising SimConnect data requests now
     2047 FSUIPC Menu entry added
     2094 C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\FLIGHTS\OTHER\Prepar3D.FXML
     2094 C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.AIR
    36735 System time = 28/04/2014 16:22:43, Simulator time = 06:20:00 (10:20Z)
    52422 System time = 28/04/2014 16:22:59, Simulator time = 06:20:04 (10:20Z)
    52422 *** FSUIPC log file being closed
Average frame rate for running time of 6 secs = 31.4 fps
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 

 

My FSUIPC4 Install.log file look like this:

 

Installer for FSUIPC4.DLL version 4.931

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\FSX
     Parameter"AppPath"
... NOT found! ...
Looking in registry for ESP install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\ESP
     Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\Prepar3D
     Parameter"AppPath"
... NOT found! ...
Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v2!  <<< ...
===========================================================

INSTALLATION FOR Prepar3D v2:
SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"
Checking version of the Prepar3D v2 EXE:
... Version 2.2.10437.0  (Need at least 1.0.677.0)
Checking if there's already a version of FSUIPC4 installed in:
       C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL
... Version 4.931 found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Stephan\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default.migrated\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Stephan\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\Stephan\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D2.dll" okay
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "List of FSX and P3D controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
===========================================================

All installer tasks completed.
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

The guide i was refering to was this thread: http://forum.simflight.com/topic/76746-using-fsuipc-with-p3d-v22-in-sli/

 

Stephan.

Edited April 28, 2014 by steppy1982

[Pete Dowson]

The most likely reason is that FSUIPC 4.931 is not compatible with P3D 2.2.10437.0. Please apply the hotfix from LM to bring it up to 10438 -- there's a link next to the FSUIPC 4.931 download link in the Download Links subforum.

 

If that doesn't fix it, please double check that your correct KEY file is

 

"C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.AFR-FriendlyD3D.exe.key"

 

because FSUIPC isn't even finding your name and email address from such a file. Since you installed in Program Files, which is a protected area, you might need to run Explorer "as administrator" to edit or rename files in that folder.

 

The guide i was refering to was this thread: http://forum.simflig...p3d-v22-in-sli/

 

 

Ah. I see their his files were named differently to yours, without the 2.exe". All the files, INI, LOG and KEY must be nmaed the same way.

 

I really HATE these EXE renaming fiddles. FSUIPC has to rely on the process name to know what it is running inside. It also messes other programs up, like Opus and EZCA.

 

Pete

[steppy1982]

OK, I will try to find the Hotfix and give this a go. Thanks so much for your help so far :)


*update* The Hotfix from LM did the trick. Now FSUIPC runs with my registration. Did not catch that I had to use the hotfix with this version of FSUIPC.. :oops:


Thanks again.

 

Stephan.

Edited April 28, 2014 by steppy1982