GSX Prepar3d EZCA and FSINN working together?

[gypsyczar]

I am trying to fly on VATSIM using Prepar3d.  In order to do so I'm using the Flightsim Estonia FSX2Prepar3d tool for installation and fooling Prepar3d into thinking it is fSX to allow FSINN and EZCA to work.  I would also love to get GSX to work in this environment but no luck so far.  Of course, I can install GSX in the native Prepar3d mode and it works fine, but then FSINN and EZCA do not work, 

In order to coexist with EZCA and FSINN a copy of the the Prepar3d exe has had the version information changed and renamed by the FSX2Prepar3d tool to FSX.exe to spoof FSX as below:

FILEVERSION 10,0,61637,0
PRODUCTVERSION 10,0,61637,0
FILEOS 0x40004
FILETYPE 0x1
{
BLOCK "StringFileInfo"
{
   BLOCK "040904B0"
   {
      VALUE "FileVersion", "10.0.61637.0 (FSX-Xpack.20070926-1421)"
      VALUE "ProductVersion", "10.0.61637.0 (FSX-Xpack.20070926-1421)"
      VALUE "FileDescription", "Microsoft Flight Simulator©"
      VALUE "CompanyName", "Microsoft Corp."
      VALUE "InternalName", "fsx.exe"
      VALUE "LegalCopyright", "Copyright ¨ Microsoft Corporation. All rights reserved."
      VALUE "LegalTrademarks", "Microsoft© is a registered trademark of Microsoft Corporation."
      VALUE "OriginalFilename", "fsx.exe"
      VALUE "ProductName", "Microsoft© Flight Simulator X"
   }

If I use the "hacked" Prepar3d file then all BUT GSX works.  I have checked and the exe.xml and dll.xml files are good.  Running under the "hacked" Prepar3d exe neither the Addon Manager or Couatl appers to load.  I have not been able to find any error files

I realize that this is not a  FSDT problem, but I would love to get this all working together,  Does anyone have any suggestions on how to make this work?

[virtuali]

This has already been discussed here:

http://www.fsdreamteam.com/forum/index.php?topic=7205.msg60620#msg60620

I realize that this is not a  FSDT problem, but I would love to get this all working together,  Does anyone have any suggestions on how to make this work?

The only real way, is that those other developers ( EZCA and FSINN ) would support P3D correctly, without requiring such hacks. Other than supporting P3D natively and properly, there's not much more we could do.

[gypsyczar]

Thank you for the rapid reply. 

I guess GSX goes on the shelf until everybody else catches up.

You wouldn't care to write a VATSIM voice client would you   

[virtuali]

I guess GSX goes on the shelf until everybody else catches up.

The correct solution should have been: everybody else on the shelf, until THEY catch up. You are not sending out the correct signal, if you stop using the product that did the right thing and supported P3D properly, preferring the ones that required hacks to work.

In any case, maybe we found a workaround for this, keep watching the forum for an update.

[virtuali]

Have a look here, we have an update that will hopefully work with the migration tool in Legacy mode. Let me know if it works:

http://www.fsdreamteam.com/forum/index.php?topic=7237.0

[gypsyczar]

You Guys Rock!!!!

 I'll try your solution and get back to you as soon as I land!

I wish all of the vendors were as responsive as you!

Thanks again

[gypsyczar]

SUCCESS!

However, if you are using the FSX2Prepare3d tool you need to change the batch file to:

set AddonManagerForcedVersion=4747
start FSX.exe
set AddonManagerForcedVersion=

When you turn the virtual FSX on in the tool it points to FSX.exe in the Prepar3d directory

[virtuali]

Yes, of course you are right, the disguised Prepar3d.exe is now named FSX.EXE. I'll update the batch file on the forum post.