New Orbx Central v4.0 now available to download

[kurtb 121]

Why is this update not available to all? Opening orbx central everyday and no message of an update lol!!!!

[CFIJose 5,485]

7 minutes ago, kurtb said:

Why is this update not available to all? Opening orbx central everyday and no message of an update lol!!!!

It's a full download.

You need to download OC v4. Delete FTXC v3. Install OC v4.

[CFIJose 5,485]

I checked the ORBX Central forum again today and I'm starting to get some answers to my questions.

1) You can download ORBX Central and as long as you do not update your airports, only new installs will utilize the .xml method. This means we can use our current scenery.cfg files. Don't update your airports or migrate and you should be safe.

2) You can stick with FTXC v3, but future new airports will require the new ORBX Central to install them.

I have not personally tested the above, but it sounds credible.

[AnkH 2,266]

Well, what a nice release then: you can stick with all the old stuff for having a working sim, but when you want something new, you have to switch to a non-working approach... A mess, nothing more or less...

[Wise87 1,281]

14 minutes ago, DJJose said:

2) You can stick with FTXC v3, but future new airports will require the new ORBX Central to install them.

I guess I won’t be buying anything new than. I’m not touching 4.0 until I need to do a clean install down the road because right now my sim has been running great for the last year. 

[CFIJose 5,485]

Beta testing is more than posting a few pretty pics online. It does require some experience. 😁

The reason why I did not take part in the beta testing for OC v4, is because I helped them discover that Objectflow for P3D v4 would not work without the Visual C++ Redistributable Packages and I did not even get a thank you.

OC pdf has no mention of my last post. It seems that ORBX want its users to forget about v3 and move right to v4. There's really no reason for them to support v3, now that v4 has been released. JM2C

 

 

Edited August 7, 2019 by DJJose

[hschuit 11]

I wanted to move the Global Base files to an external library but guess what the manual says: "Unfortunately, due to technical limitations, Orbx Global Base Pack can’t be migrated into a
library."  I guess this means that after installing a P3D content version update, your Global Base files will be overwritten just like in the old days.

[MaDDogz 242]

Perfect!

[Christopher Low 5,353]

2 hours ago, DJJose said:

I checked the ORBX Central forum again today and I'm starting to get some answers to my questions.

1) You can download ORBX Central and as long as you do not update your airports, only new installs will utilize the .xml method. This means we can use our current scenery.cfg files. Don't update your airports or migrate and you should be safe.

2) You can stick with FTXC v3, but future new airports will require the new ORBX Central to install them.

I have not personally tested the above, but it sounds credible.

Not great if.....

1) You use the old scenery.cfg method, and you want to keep on using it because certain scenery packages need to be above others in the pecking order. Yes, I know that I can use external utilities for this, but I should not have to.

2) You want to carry on using the scenery.cfg method, but ORBx Central will not permit it when anything new is installed.

 

[Maikel van der Heijden 4]

I'm now using the Scenery Config Editor for installing addons. Using the V3 version of FTX Central works fine so I'm happy using both of these programs.

If I'm going to update to FTX Central V4, confirm I can not install the ORBX addons in my flightsim map anymore. I now install them in Program Files > Lockheed Martin > Prepar3D V4 > ORBX or Addon Scenery and I do not use the .xml method and I really want to keep it this way, because I always make a clean install when a new version of P3D comes out anyway.

I've read the comments made in this topic but can anybody confirm that V4 will not work in this way anymore and I must make use of this .xml method?

Maikel

[CFIJose 5,485]

36 minutes ago, Christopher Low said:

2) You want to carry on using the scenery.cfg method, but ORBx Central will not permit it when anything new is installed.

My understanding is that you can install new scenery and it will be added with .xml method (i.e. KSUN before the new OC)

It shouldn't affect the scenery.cfg. Have you been able to confirm that it does not work as it should?

[CFIJose 5,485]

16 minutes ago, Maikel van der Heijden said:

I'm now using the Scenery Config Editor for installing addons. Using the V3 version of FTX Central works fine so I'm happy using both of these programs.

If I'm going to update to FTX Central V4, confirm I can not install the ORBX addons in my flightsim map anymore. I now install them in Program Files > Lockheed Martin > Prepar3D V4 > ORBX or Addon Scenery and I do not use the .xml method and I really want to keep it this way, because I always make a clean install when a new version of P3D comes out anyway.

I've read the comments made in this topic but can anybody confirm that V4 will not work in this way anymore and I must make use of this .xml method?

Maikel

I can confirm based on the manual and everything I've read, that new installs or updates to installed airports will utilize the .xml method. This will probably require you to delete the updated airport with your scenery config, re-number, and save the new scenery.cfg.

[Maikel van der Heijden 4]

10 minutes ago, DJJose said:

I can confirm based on the manual and everything I've read, that new installs or updates to installed airports will utilize the .xml method. This will probably require you to delete the updated airport with your scenery config, re-number, and save the new scenery.cfg.

Thank you for replying, this is quite a deal breaker for me as I really want to keep all my flightsim stuff on one hard drive. I'll just keep V3 as long as I can.

[MDFlier 2,031]

Well.. I saw the title of this thread, so I jumped right over to Orbx and downloaded FTXCv4 and installed it.

It asked me if I wanted to uninstall v3, so I let it. The install went pretty quick. 

Without starting P3D, I started looking around in FTXCv4. I noticed a "Migrate to Library" button under every product in the 'My Products' tab. So... I went through and migrated every Orbx product to an external folder, E:\Orbx Library\. The process completed after about 45 minutes. It appears to have moved the files from my P3D\Orbx folder to the new library. There is no way it downloaded everything that fast.

After all  of that, I fired up P3D. The 1st startup took quite a while (~10 minutes) and I had to click yes to allow each of them. One airport has a problem, LSGK. Getting "Path not found: E:\P3D\Prepar3Dv4\Orbx\FTX_EU_FTX_AA_LSGK\Scenery\*_objectflow.xml". The "*_" is the problem there. This is the only airport FTXCv4 didn't migrate.

I had to export the scenery library and run the Vector AEC tool, as well as reapply all of the Vector fixes (rename 4-5 Vector files to .off) to fix the elevation issues at FlyTampa's KLAS again, but all of my other airports are fine (FB: KIAD, KDEN, KMSP FT: KBOS, KLAS, T2G: KMCO, LVFR: KBWI and KMSY)

So, it appears that I got lucky that most everything worked. I'll have to look into the LSGK issue later. I took a quick look with Lorby and everything appears to be in the proper order in the list as well. Life is good. Thank you blind luck! If I had read this thread first, I probably wouldn't have done all that..

 

Edited August 7, 2019 by MDFlier

[Christopher Low 5,353]

I do not have a huge number of ORBx scenery packages, so it may not be a big issue that the ORBx entries are all converted to the XML method (so long as it does not mess about with the rest of my Scenery Library).