I'm a newcomer from the 4.5 and was pretty much impressed by the job LM did with a landclass and terrain, and that makes me wonder whether we really need Vector OR ORBX Base and landclasses packs would suffice?

 

Thanks

Nope. Vector is more trouble than it's worth.

A deep analysis of a product is always welcome. Do you have one for Orbx Global Base to share as well?

From ORBX:

This version specifically for P3Dv5 is a derivative of the original Vector release.

 

It goes on to explain in some detail exactly what it is and why the customer might like to use it.

 

Prepar3D v5 itself contains a completely new build of the default landscape and airports, the first time this has happened since the release of its predecessor, FSX. However, while Vector uses the same Open Street Map database, it’s features are more configurable (via the control panel) and uses custom road and shoreline textures, which integrate better with our other Global products.

The main difference to the original version of Vector is the removal of the adjusted airport elevations for default airports. This component is not compatible with Prepar3D v5, which uses current and more accurate layouts compared to the original Vector database. Moreover, hundreds of airport ICAOs have changed in Prepar3D v5, which would cause duplicate airports to be displayed at those locations when using Vector’s airports.

 

7 minutes ago, Chapstick said:

Nope. Vector is more trouble than it's worth.

It was "must" in pre-V5 world, hands down. My question was about Vector + V5

1 minute ago, Tokitaumelie said:

From ORBX:

This version specifically for P3Dv5 is a derivative of the original Vector release.

 

It goes on to explain in some detail exactly what it is and why the customer might like to use it.

 

Prepar3D v5 itself contains a completely new build of the default landscape and airports, the first time this has happened since the release of its predecessor, FSX. However, while Vector uses the same Open Street Map database, it’s features are more configurable (via the control panel) and uses custom road and shoreline textures, which integrate better with our other Global products.

The main difference to the original version of Vector is the removal of the adjusted airport elevations for default airports. This component is not compatible with Prepar3D v5, which uses current and more accurate layouts compared to the original Vector database. Moreover, hundreds of airport ICAOs have changed in Prepar3D v5, which would cause duplicate airports to be displayed at those locations when using Vector’s airports.

 

Ok...so it's still the same Vector, but without AEC. 

Exactly and with the same configurable options. As you already own Vector for P3D v4, it is free of charge.

Edited June 16, 20214 yr by Reader

Does the Vector kill default road lights? They're awesome and I'd like to leave them 

You could try with and without at no cost?

V5 has more up to date vector data apparently, but I don’t like the look of the roads. They are kind of bright white in places and I just don’t like the look of it. There were some errors in V5 data as well, not sure how much of it has been corrected. I just put Vector V5 on and not looked back.

There was another thread saying that using vector can cause issues using the default flight planner. For me it does not crash it, but makes the planner take long time to load in data. Like 4 or 5 minutes it feels like sometimes!

Really you just need to test it and see which you prefer.

Edited June 16, 20214 yr by djbully

ok, thanks for the answers.

 

One more technical question - may I maintain the same installation for the Base, Vectors and LCs or they should be reinstalled for the V5?

30 minutes ago, G-YMML1 said:

ok, thanks for the answers.

 

One more technical question - may I maintain the same installation for the Base, Vectors and LCs or they should be reinstalled for the V5?

Just run Orbx central, choose P3D V5 when given the option, it should just use the same install files, but do all the configuring for V5. 
 

That is assuming your Orbx are installed to an external library, and not inside the Prepar3d folders.

Edited June 16, 20214 yr by djbully