General Category > General Discussion

P3D v1.4

<< < (2/4) > >>

Kosta:
OK here is an update: without migrator, everything is peachy. Installation went OK, installed, ran LSZH+GSX...

I didn't even try installing with the migrator.

But unfortunately, running in the Legacy Mode disables Addon Manager for some reason - would there be any chance you could maybe look into making it work with the legacy mode? I don't know any backgrounds with this stuff, apparently when addon manager that is for P3D doesn't find prepar3d.exe, it won't load.

Running with the open migrator, but not in the legacy mode is completely fine.

virtuali:

--- Quote from: Kosta on August 28, 2012, 01:54:52 pm ---I just hope that after the installation FSDT has nothing against me running P3D in legacy mode, meaning like fsx.exe.
--- End quote ---

As I've said, it's possible there will be some issues: if our installers are tricked into believing they are installing in FSX, they will not enable some specific P3D configurations, so it's likely that nothing will work.

The most important thing to be checked is:

On the %APPDATA%\Lookheed Martin\Prepar3D\EXE.XML file, the section that launched the Couatl program should look like this:


<Launch.Addon>
  <Name>Couatl</Name>
  <Disabled>True</Disabled>
  <ManualLoad>False</ManualLoad>
  <Path>fsdreamteam\couatl\couatl.exe</Path>
  <CommandLine>--mode=prepar3d</CommandLine>
</Launch.Addon>


Note this line:


<CommandLine>--mode=prepar3d</CommandLine>


If the installer believes it's running in FSX, it will not add that line so, you will add it yourself after the installation.

Kosta:
I have exactly that.

If I forced addon manager to run in FSX mode for p3d in legacy mode, would that work? What do you think?

virtuali:

--- Quote from: Kosta on August 28, 2012, 02:32:03 pm ---But unfortunately, running in the Legacy Mode disables Addon Manager for some reason - would there be any chance you could maybe look into making it work with the legacy mode? I don't know any backgrounds with this stuff, apparently when addon manager that is for P3D doesn't find prepar3d.exe, it won't load.
--- End quote ---

I guess that's the likely the reason: if the migrator hides or renames the prepar3d.exe and replace it with a dummy fsx.exe, the Addon Manager won't work, because it's doing the correct thing, which is checking the executable (doesn't matter how it's named, it checks whichever executable the Addon Manager was launched by) actual file version, and depending on that version, it decides to enable FSX or P3D support. If the .EXE is not the real one, the Addon Manager will not recognize it and will not work.

I'm sorry, but we already did the RIGHT thing, which is supporting P3D NATIVELY. We don't have any plans to do additional work, just to support a tool that shouldn't be needed in the first place, because they right thing for other developers to do, would be doing the additional work we ALREADY made, to adapt their installers to run in P3D proper.

virtuali:

--- Quote from: Kosta on August 28, 2012, 02:35:34 pm ---If I forced addon manager to run in FSX mode for p3d in legacy mode, would that work? What do you think?
--- End quote ---

I don't have any idea, without knowing *exactly* what legacy mode does.

Navigation

[0] Message Index

[#] Next page

[*] Previous page