Vector 1.1 with default mesh?

[Hippo 34]

I'm pondering buying Vector 1.1, but not buying the Pilots Global FTX mesh.  So I'd be using the default mesh.  What issues (if any) can I expect to see?

 

(I am using FTX Global Base).

 

[Kilo60 660]

I'd like to know this as well...

 

Although, I bought Pilot's Global FTX mesh and virtually every single AP in FSX got put on a cliff or plateau... All FS GLOBAL Mesh regions now are deactivated in FSX!

 

Now I'm hoping Vector can fix all these AP's as the AFM AP elevation fixer program is no longer is to be used with the FTX version as Pilot's have apparently stated Vector will "FIX" all the AP elevation issues regarding plateaus..

[Mephic 129]

If you use it with default mesh best way to start is disable all aec for every airport. You won't need elevation corrections.

[Hippo 34]

So if used with the default mesh, I won't get airports on cliffs / in valleys, and other weird landscape distortions?

[Rocky_53 1,566]

So if used with the default mesh, I won't get airports on cliffs / in valleys, and other weird landscape distortions?

 

No, that is definitely not the case in my experience. If you use Vector without a third party mesh, then you WILL have elevation issues. These will be more prominent at default FSX airports. As for payware airports, some of these have issues, even when using a good quality mesh. My experience has been so far:-

 

1) I purchased the original Vector on release and uninstalled it within minutes, as I found I hated the underlays on the roads, which were far too wide, and the elevation issue was apparent at several payware airports. I decided to wait for the v2

 

2) I installed this latest version and was REALLY pleased that the control panel worked well and allowed the removal of road verges and also the tweaking of many other things too. The main interest for me was the airport correction tool within the control panel. While I still have issues at default airports it has cleared ALL issues at payware airports at this moment in time. Having issues at default airports, for me pesonally, is not a problem as I only fly to payware airports anyway.

 

3) One thing I have noticed for whatever reason, after uninstalling UTX, everything appears far more 'organised' with Vector, things just seem to fit together better. As I say, just my opinion FWIW.

 

When Orbx release there own landclass then things will really look good.

[Hippo 34]

Rockliffe - thanks for the response.  I have seen most of your posts on the Orbx forum, and have a lot of sympathy with your (and others') opinions expressed over there.  It is thanks to these opinions (and to the reply closing off that thread by the Orbx CEO) that I have not bought Vector, and it seems saved myself a lot of grief (so thanks again).

 

I am astonished that with all that has happened, the word "mesh" does not appear on the Orbx Vector product page or on the FSS page, not even as a recommendation.

 

Moving on.  I do use use default, as well as payware airports; does the provided tool make it possible to deal with elevation issues at default airports?  I think that even if you don't use default airports, them being raised on plateaus still looks pretty awful as you fly along nearby.

 

Good to hear that you like the tweaking tool.  So is the airport elevation issue now the only major remaining problem?  I think I remember seeing screenshots of peaks shooting up into the skies and other weird anomalies - this sort of thing I could live with if they're infrequent.

 

I do want to buy Vector, but everything I've seen suggests a product which was rushed out way too early.  And the response from Orbx as to need a mesh / don't need a mesh has left a very bad impression with me.

 

So, the $64k question: will 1.1 be staying on your system?

[JRBarrett 3,034]

I have used Pilot's Global Ultimate mesh for almost two years, and have been living with the fact that the price one has to pay for enhanced terrain is airports on plateaus.

 

I had hoped that version 1.0 of Vector would correct these issues, but it did not - the airport elevation corrections did not make it into the final release.

 

I'm very happy to say that Vector 1.1 HAS fixed this issue in my installation. Probably 98% of the default FSX airports that were raised on plateaus by the enhanced mesh, have now been flattened to match the surrounding terrain.

 

Since the airport elevation corrections in Vector 1.1 were intended to work on conjunction with enhanced mesh, you would want to turn them off (globally) with the new configuration program if you use default FSX mesh, or you will have issues with airports being sunk into the ground (generally), though some will be raised on plateaus.

 

On the other hand, if you already have enhanced mesh, but have currently disabled it, I would urge you to re-enable it (first), then install Vector 1.1... I think you would be very pleased with the results.

 

Overall, Vector 1.1 looks much, much better than the first version. Road widths are much improved, and the roads blend in far better.

 

There are still bugs due to inaccurate source data in some locations, but overall, the new Vector is a great improvement on the first version, and the airport elevation corrections for enhanced mesh really do work, and work well!

[Rocky_53 1,566]

 

So, the $64k question: will 1.1 be staying on your system?

 

Yup!

[Hippo 34]

If you use Vector without a third party mesh, then you WILL have elevation issues. These will be more prominent at default FSX airports.

 

This is something that I find puzzling.  I get that if you have a mesh then the default airport elevations may not be the same as the mesh and issues can arise.  But if you have the default mesh and default airports and no elevation issues, then why would vector introduce elevation issues?  Don't all Orbx have to do to the airport elevations for this setup is ... nothing whatsoever?  Or offer a "default airports" option in their tool perhaps?  Clearly I must be missing something here, I'd be grateful if someone can enlighten me as to what.

 

I'm afraid I remain unconvinced (and recent postings at the Orbx forums don't inspire much confidence).  Maybe I'll wait and see what 1.2 brings...

[Rocky_53 1,566]

This is something that I find puzzling.  I get that if you have a mesh then the default airport elevations may not be the same as the mesh and issues can arise.  But if you have the default mesh and default airports and no elevation issues, then why would vector introduce elevation issues?  Don't all Orbx have to do to the airport elevations for this setup is ... nothing whatsoever?  Or offer a "default airports" option in their tool perhaps?  Clearly I must be missing something here, I'd be grateful if someone can enlighten me as to what.

 

I'm afraid I remain unconvinced (and recent postings at the Orbx forums don't inspire much confidence).  Maybe I'll wait and see what 1.2 brings...

 

Sure, I know it's confusing, and believe me, if anyone is going to get confused it will be me! I agree with you, the whole thing seems illogical, until you start reading a little more in depth about how things have been done. Vector, as with FTX Global, are two game changers in many people's eyes, they have truly transformed the look of FSX. FTX Global changes the default FSX textures, while Vector adds many, many other things like, roads, rivers, beaches, golf courses, city parks, tunnel entrances, frozen water etc etc. During the design of Vector, Pilots, who produce the software for Orbx, developed Vector based on actual, correct elevation data and not the incorrect data which many FSX airports have been based on. So yes, it would seem reasonable to expect Vector to be designed on FSX data, but then if FSX airports data is often incorrect, then it would be illogical. So because Vector has been created with the correct elevation data, this of course impacts on airports that are sitting pretty in FSX with incorrect elevation data!

 

To correct this, you have the option to install a third party mesh to correct the elevation data and bring airports in line with Vector. So it's not Vector that is wrong, it's the wrong data that is used in FSX! However, and this is where things go amiss, my own experience has shown that even with some payware airports, not all, there have been some big anomolies after installing Vector. However, by using the elevation tool within the Vector control panel this seems to have worked 100% of the time. But sadly it has not worked with default airports in my experience. So, my advice would be do some further research over on the Orbx forum before parting with cash, as I agree, it is a bit of a minefiled.

[Hippo 34]

Thanks for all the replies, btw, they've been very helpful.

 

 

 

FTX Global changes the default FSX textures, while Vector adds many, many other things like, roads, rivers, beaches, golf courses, city parks, tunnel entrances, frozen water etc etc. During the design of Vector , Pilots, who produce the software for Orbx, developed Vector based on actual, correct elevation data and not the incorrect data which many FSX airports have been based on.

 

 

So because Vector has been created with the correct elevation data, this of course impacts on airports that are sitting pretty in FSX with incorrect elevation data!

 

Sorry if I'm being a bit dense...

 

Would it not be more correct to say that it's the particular mesh that has been been created with the correct elevation data, and that the AECs correct for the mesh, and not for vector? 

 

My understanding is that only airports contain elevation data, and that no Vector items do (since they get their elevations from the underlying mesh).  Maybe this assumption is where I'm going wrong.

 

So if you're on default mesh, with default airports, and you add vector, I continue to fail see why the elevations of airports should change if you DON'T apply the corrections for them.

[Rocky_53 1,566]

So if you're on default mesh, with default airports, and you add vector, I continue to fail see why the elevations of airports should change if you DON'T apply the corrections for them.

 

That's a question I don't know the answer to, like yourself, I still don't fully understand the reasons why Vector should affect elevations, but it does. Here's a bit of blurb from Pilots...

 

VERSION 1.20: The configurator will now allow you to disable / enable AEC by airport or globally. This means you can disable AEC completely. You will not lose airport boundary polygons for airports with disabled AEC; with the new version, disabled AEC will just leave you with the default airport without VECTOR affecting it at all. This will allow you to turn off AEC completely and to turn it on for specific airports if you encounter issues.