Hey guys,

 

I just bought 4 different airports and the CRM pack with this great ORBX sale, but as I was checking out I noticed they aren't officially "P3Dv2 compatible". I was wondering if anyone had any idea of how--err, broken--these airports are that aren't offically v2 ready? If it's bad I'll just use them in FSX, but I was wondering if it's worth putting them into P3D.

 

Thanks for any input,

No idea but I would think with migration tool would not be a problem, I think the only difference is there is no installer pointing to P3D - maybe someone else will chime in

Hey guys,

 

I just bought 4 different airports and the CRM pack with this great ORBX sale, but as I was checking out I noticed they aren't officially "P3Dv2 compatible". I was wondering if anyone had any idea of how--err, broken--these airports are that aren't offically v2 ready? If it's bad I'll just use them in FSX, but I was wondering if it's worth putting them into P3D.

 

Thanks for any input,

 

I have installed some airports from ORBX with the EMT tool. And I do experience issues. There are minor glitches like the plane wheels being partly buried in the runway payment or some details missing.Then I experience that P3D2 rebuild scenery at launch mostly every time. Also sometimes the EZCA camera add on won't start. I suspect this might have something to do with the ORBX airports.

"I have installed some airports from ORBX with the EMT tool. And I do experience issues"

 

​Good to know I would have thought differently - thank you

I have installed some airports from ORBX with the EMT tool. And I do experience issues.

Anything really major? Wheels buried I can deal with, but I'm talking like custom buildings gone missing, or mesh/terrain issues.

There has been a guide at Airdailyx how to install Orbx stuff without a native P3D2 installer by setting symbolic links and then installing using the P3D1 option in the installer. If you do it this way then P3D will even automatically update the objectflow.dll to a P3D2 working version at startup. Most airports work without a problem then. Exceptions are for example PAKT (due to the special modelling of the airport)

Okay, thanks Carlos for that. Could you please point me to that guide?

Anything really major? Wheels buried I can deal with, but I'm talking like custom buildings gone missing, or mesh/terrain issues.

 

The scenery appeared corrupted in 2S1 and in WA56 Israels farm most things were missing. So I removed these airports in P3D and deleting the files on the HD.

Now when I installed my newly purchased Orbx South Alaska these airports were added in the P3D list and I encountered many crash to desktop before they were removed again. The major thing is that I have issues and it does not seem to be easy to remove the suspect makes me regret I installed them.

 

 

Okay, thanks Carlos for that. Could you please point me to that guide?

 

Here you go:

http://airdailyx.blogspot.de/2013/11/a-guide-for-installing-orbx-scenery.html

 

When running the installer you must select that you want to install into Prepar3d v1 (not FSX). The symbolic links created if you follow the steps in the guide will point towards your Prepar3d v2 directories so that the installer thinks it is installing into v1 but actually installs into v2.

 

 

The scenery appeared corrupted in 2S1 and in WA56 Israels farm most things were missing. So I removed these airports in P3D and deleting the files on the HD.

Now when I installed my newly purchased Orbx South Alaska these airports were added in the P3D list and I encountered many crash to desktop before they were removed again. The major thing is that I have issues and it does not seem to be easy to remove the suspect makes me regret I installed them.

 

There are guides in the Orbx forums how to uninstall scenery. If you follow the guide then there will be no traces left of the Orbx airports. I bet your instabilities have nothing to do with the Orbx sceneries. Never encountered any problems from installing Orbx airports into P3D2 other than some missing objects...

Here you go:

http://airdailyx.blo...bx-scenery.html

 

When running the installer you must select that you want to install into Prepar3d v1 (not FSX). The symbolic links created if you follow the steps in the guide will point towards your Prepar3d v2 directories so that the installer thinks it is installing into v1 but actually installs into v2.

Great! Thanks a bunch!

Great! Thanks a bunch!

If you want them to work right do this.

1. Either get the the EMT or create symbolic links from FSX to V2

2. Open the installer and select the FSX install option it should show the P3Dv2 directory now.

3.Install the airport

4.Open P3dV2 and it will ask if you want to run the Objectflow.dll,Say no

5. It will offer an update for Objectflow.dll say yes p3dv2 will now restart

6. Enjoy the airport

using this method makes objectflow.dll work in p3dv2 without objectflow many things will be missing from the airports if you select the p3d install this wont work you must select the FSX install option.

4.Open P3dV2 and it will ask if you want to run the Objectflow.dll,Say no

Say no? Never heard of doing that, but will do.

Say no? Never heard of doing that, but will do.

The reason is that if you click yes it will crash p3d if you try to load the incompatible objsectflow.DLL the one you get from the update works fine

Also, most orbx FSX addons will be P3D v2 compatible by the end of the year, or at least that's the aim.

The problem with installing them via EMT is that the installer will then install a FSX version of the objectflow.dll. This one crashes P3D2. However, i you install it via symbolic links and choose to install in Prepar3d v1 then the installer will install a P3D v1 version of objectflow.dll which will then be updated to a v2 version once you start P3D. This works like a charm (except for airports like PAKT which use very special modelling techniques). An install via the EMT will not work properly! And installing them with symbolic links for FSX will also not work properly for the explained reason. You must install the P3D v1 version.