11 minutes ago, downscc said:

Before I started the FSDT/Flightbeam adventure

hahahaha, good definition!.

Cheers, Ed

11 minutes ago, downscc said:

Before I started the FSDT/Flightbeam adventure, I had installed all my Orbx products (I have most of the regions, airports aren't ready yet) and I noted they went to the top of the scenery library. Fair enough, I hadn't set an insertion point yet so i added one airport from the P3Dv3\Addons directoy (my home base KCRP available in AVSIM) and set that to the top of the library.  Then I followed Greg's method to install all the FSDT/Flightbeam airports with the new installers.  I have all but KCLT.  All went as planned with entries made by the installer to the addon document folders and the scenery/texture files in my SSD D: drive.  I notice that although addons are not in the scenery.cfg file, they do appear when you open the World > Scenery Library menu item and they appear above my manually added KCRP and all the Orbx. So it appears as there is a proper order to things.

Now am I contemplating how to best install Pilot's FS Global NG mesh and I believe that this will be manual entries to the scenery.cfg to ensure proper placement.  I cannot find anything yet in the SDK that provides an ability to force a layer number with the add-on.xml.

Hi Doug, the SDK isn't of much help, I agree. For the FreeMeshX I ended up adding the layers manually. But I may end up using the XML "layer"  entry as per the SDK. I wrote a post about this here: https://www.avsim.com/forums/topic/511395-installing-add-ons-in-v4/?do=findComment&comment=3635920

Maybe it will help in what you're trying to accomplish.

 

cheers

-E

31 minutes ago, downscc said:

Now am I contemplating how to best install Pilot's FS Global NG mesh and I believe that this will be manual entries to the scenery.cfg to ensure proper placement.  I cannot find anything yet in the SDK that provides an ability to force a layer number with the add-on.xml.

Do you still have your NG mesh installed in its own folder? (FSGU_NG) If so, insert the first DVD from the FS Global Ultimate set and run the installer. It will ask if you want to look for an update - answer "yes". It will download an updated P3D Version 4-aware installer, which will then run. You will go through the same steps as if your were installing for the first time, including entering your user ID and password for the Pilot's web site. Once you do that, it should automatically load your product key. In the next step, you will be asked if your want to do a full install, or just update the scenery layers. Choose the latter. It will automatically insert all of the Global NG entries in the scenery.cfg file in the proper location - (right after the 1107 Base scenery, which should be Area 098) . The update takes about three seconds, and once the scenery.cfg is updated, you will have all your high res terrain mesh.

In the case of something like mesh - which has to be layered into the scenery system in a very specific place, it is probably best to use the default installer which directly modifies scenery.cfg - rather than trying to make it work with the new system, which is more suitable for things like add-on airports.

Hi,

Anybody has this issue? Over at FSDT there are few people that having this problem too. I tried to follow virtuali instructions to troubleshoot it but still no luck.

Flightbeam sceneries are fine. I install with antivirus disable, run as administrator, and restarted the sim before installing. Tried uninstall all Flightbeam products and install again but still having problem with FSDT ones.

 

Thank you,
Hoang Le

2 minutes ago, JRBarrett said:

Do you still have your NG mesh installed in its own folder? (FSGU_NG) If so, insert the first DVD from the FS Global Ultimate set and run the installer. It will ask if you want to look for an update - answer "yes". It will download an updated installer, which will then run. You will go through the same steps as if your were installing for the first time, including entering your user ID and password for the Pilot's web site. Once you do that, it should automatically load your product key. In the next step, you will be asked if your want to do a full install, or just update the scenery layers. Choose the latter. It will automatically insert all of the Global NG entries in the scenery.cfg file in the proper location - (right after the 1107 Base scenery, which should be Area 098) . The update takes about three seconds, and once the scenery.cfg is updated, you will have all your high res terrain mesh.

In the case of something like mesh - which has to be layered into the scenery system in a very specific place, it is probably best to use the default installer which directly modifies scenery.cfg - rather than trying to make it work with the new system, which is more suitable for things like add-on airports.

Thank you, Jim, that is exactly what I will do.  I was a little cautious about running the installer again because I didn't want to have to reinstall the FSGU_NG data I already have on my data SSD.  Excellent.  I will give that a try as soon as able.

5 minutes ago, Hoang said:

Hi,

Anybody has this issue? Over at FSDT there are few people that having this problem too. I tried to follow virtuali instructions to troubleshoot it but still no luck.

Flightbeam sceneries are fine. I install with antivirus disable, run as administrator, and restarted the sim before installing. Tried uninstall all Flightbeam products and install again but still having problem with FSDT ones.

 

Thank you,
Hoang Le

I had that a few times when I was installing several at a time.  I just waited for the installers to finish and then ran it again and it worked just fine.

1 minute ago, sfgiants13 said:

I had that a few times when I was installing several at a time.  I just waited for the installers to finish and then ran it again and it worked just fine.

Hi,
I only install one at a time, tried several times each airport but still having problem.
Thank you for your help so far,

Hoang Le

On 2/6/2017 at 9:13 PM, gregmorin said:

Ed

No this would not work. FSDT will move all your PD3V3.4 to the new location when you install the first airport to PD3V4. You have no choice in this. However the PD3V3.4 airports will work just as well when they are moved.

Greg

Hi Greg, checked this with Umberto at FSDT and he says to avoid modifying your existing P3Dv3.4 setup when you run the installer at the start you should have de-selected the option to install to P3Dv3, VERY simple, in its own words.

Just wanted to let you know.

Cheers, Ed

 

8 minutes ago, edpatino said:

Hi Greg, checked this with Umberto at FSDT and he says to avoid modifying your existing P3Dv3.4 setup when you run the installer at the start you should have de-selected the option to install to P3Dv3, VERY simple, in its own words.

Just wanted to let you know.

Cheers, Ed

 

Thanks Ed. That is the way I tried it first. I like my way better.

Greg

7 minutes ago, gregmorin said:

Thanks Ed. That is the way I tried it first. I like my way better.

Greg

Yes, I think we have different goals. Mine is to leave P3Dv3.4 installed until a good number of addons are updated to P3Dv4 (which I think will be sooner than later), but without any major changes on its files and file structures, that's why I couldn't understand why it would get modified by installing new things into P3Dv4.

Anyway, your OP is very useful and I'll use it as a guide to my P3Dv4 setup (including FSDT and SODE).

Thanks, Ed