Prepar3d 2.5, migration tool fsx.exe with no registration. Help!

[Zone]

Hi, ive had fsuipc installed before with my Prepar3d along side migration tool. I just recently screwed up my install and had to wipe all my stuff. 

I can run Prepar3d and registration is good, but when i run fsx.exe "legacy mode" it wont load. 
I have fixed this problem once before but i cant for the life of me find the topic with the good information or figure it out. 
Not sure what i need to do.

 

[Pete Dowson]

I can run Prepar3d and registration is good, but when i run fsx.exe "legacy mode" it wont load. 

I have fixed this problem once before but i cant for the life of me find the topic with the good information or figure it out. 

Not sure what i need to do.

 

Sorry, what do you mean by "i run fsx.exe "legacy mode""? What "won't load"? If you mean FSUIPC4.DLL, then you need to look at your DLL.XML file -- it is that which tells SimConnect to load the assorted DLLs you have installed. It is nothing at all to do with what "mode" you might adopt.

 

Pete

[Zone]

I rarely use Prepar3d.exe which works fine with FSUIPC, Registration loads fine.
If i load Fsx.exe from prepar3d the registration does not get loaded once in the sim.
I have both XML files set.  The DLL loads but not the registration.

 <Launch.Addon>

        <Name>FSUIPC 4</Name>

        <Disabled>False</Disabled>

        <Path>Modules\FSUIPC4.dll</Path>

    </Launch.Addon>

 
I have this in prepar3d dll.xml and the fsx dll.xml    
What do i need to do so that registration works when i load legacy mode ? 

[Pete Dowson]

I rarely use Prepar3d.exe which works fine with FSUIPC, Registration loads fine.

If i load Fsx.exe from prepar3d the registration does not get loaded once in the sim.

 

Sorry, I still don't understand. What on Earth are you doing loading FSX.EXE "from Prepar3D". Surely you need to run FSX from its own folder, not "from Prepar3D". That makes no sense to me!

 

And what do you mean by "legacy mode". I don't understand that either.

 

Pete

[Zone]

Seriously ?? .... Im running migration tool which allows Pepar3d to run like FSX for Compatibility. There's a old topic on this but this information is not simple.
 http://forum.simflight.com/topic/71840-registration-issue-with-migration-tool/

This program makes a copy of Prepar3d.exe and renames it Fsx.exe and changes the version information... 
This allows things like scenery and aircraft to install and function. Your program loads fine within both exe's
However the registration information is not activated/found in Fsx.exe but it is fine in Prepar3d.exe. The Loader.dll works fine and can be found within "addons" tab.










INSTALLATION FOR FSX:

SetupPath="C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\"

Checking version of the FSX EXE:

... Version 10.0.61637.0  (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

    Found SimConnect build 60905 (Original)

    Found SimConnect build 61242 (SP1 May07)

    Found SimConnect build 61259 (Acc/SP2 Oct07)

Checking if there's already a version of FSUIPC4 installed in:

       C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Modules\FSUIPC4.DLL

... No previous valid version found.

FSX Modules folder created okay!

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\ZoneDT\AppData\Roaming"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Users\All Users\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Default\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Default User\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\Public\AppData\Roaming"

 ... No FSX.CFG there

Looking in "C:\Users\ZoneDT\AppData\Roaming"

Found FSX.CFG in "C:\Users\ZoneDT\AppData\Roaming\Microsoft\FSX\FSX.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 created 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

   Installed "Profiles in Separate Files.pdf" okay




Loads in both exe's like i said. Appears in addons.




Prepar3d.exe loads fine with Registration information. 





Load the game with the edited Prepar3d.exe aka "Fsx.exe" and the registration information will not appear/load.


Let me know what i should do, thanks pete.
 

Edited March 9, 2015 by Zone

[Thomas Richter]

Hi,

 

check if you find a new FSUIPC INI file that is used instead when you start in this migration mode. If so you need to copy the key file and rename it to the same as the new INI file.

[Pete Dowson]

Seriously ?? .... Im running migration tool which allows Pepar3d to run like FSX for Compatibility.

 

Ouch. Why didn't you say that in the first place? That nasty system in a right pain in the ***!

 

The problem is you've renamed the EXE, so all the files FSUIPC uses are renamed accordingly -- take a look at your INI file, for example, and LOG file. Rename your KEY file to suit.

 

There is a  section in the FSUIPC documentation dealing with renamed copies of FS.

 

[LATER]

Ah, I see Thomas has also given the same answer. Thanks Thomas!

 

Pete

[Zone]

I figured it out. All i did was make a copy of FSUIPC4.key in same "module" folder and rename FSUIPC4.key to FSUIPC4.fsx.key
Both exe's work fine now, was a easy task after i figured out that's all i needed to do.

Pete, just a idea but maybe FSUIPC should create both these key files for people with Prepar3d just incase they use MigrationTool.
Just saves the user in troubleshooting. In anycase the documentation is all there.

Thanks guys! Much obliged