Another Vegas Terrain Issue...

[newmanix]

P3Dv2. All that's installed is FTX Global+Vector along with Other FlightBeam and FSDT airports. WOAI.

P3Dv2. All that's installed is FTX Global+Vector along with Other FlightBeam and FSDT airports. WOAI. Ran the tool, and did an extensive search, the only KLAS marked files were in the Vector folder which I removed. Still no change. Plus, what's this little airfield doing here?

http://i718.photobucket.com/albums/ww184/newmanix/IMG_2704_zps567a2e21.jpg

http://i718.photobucket.com/albums/ww184/newmanix/IMG_2705_zps25020ab4.jpg

http://i718.photobucket.com/albums/ww184/newmanix/IMG_2706_zpsbf79012c.jpg

http://i718.photobucket.com/albums/ww184/newmanix/IMG_2707_zpsc04ff35c.jpg

http://i718.photobucket.com/albums/ww184/newmanix/IMG_2708_zps4b5b3f36.jpg

[virtuali]

P3Dv2. All that's installed is FTX Global+Vector along with Other FlightBeam and FSDT airports. WOAI.

As discussed many times already, for example here:

http://www.fsdreamteam.com/forum/index.php/topic,10065.msg78976.html#msg78976

It's something that is caused by 3rd party meshes, and must be fixed by the mesh, because it must be smoother out around airports, like the default mesh is, because FSX airports can't really be sloped THAT'S why Microsoft pre-processed the default mesh to prevent this. This has been explained so many times here, it's something that must be reported to MESH developers, not airport developers.

The way FSX works, the mesh with the highest nominal resolution will ALWAYS "win" against anything else, regardless of its priority in the Scenery Library so, an addon Mesh that is expected to always show up, should be corrected, otherwise it will create issues at ALL airports that are sloped in real life, but can't in FSX.

Do you see that problem without FTX Global or any other 3rd party mesh installed ? I'm sure you don't.

[newmanix]

Okay so we are saying it's the Orbx FTX Global Vector product to blame here. I will let them know.

[virtuali]

P3Dv2. All that's installed is FTX Global+Vector along with Other FlightBeam and FSDT airports. WOAI. Ran the tool, and did an extensive search, the only KLAS marked files were in the Vector folder which I removed. Still no change. Plus, what's this little airfield doing here?

Vector doesn't have anything to do with this, only a mesh could so, either you are not looking in the right place, or the file is not easy to find, or you have *another* mesh.

[virtuali]

Okay so we are saying it's the Orbx FTX Global Vector product to blame here. I will let them know.

Never said this.

You said "All that's installed is FTX Global+Vector along with Other FlightBeam and FSDT airports. WOAI.".

If it's really ALL that is installed, since WOAI can't be (although is still very wrong to install FS9 models into P3D), Flightbeam obviously can't, that doesn't leave much else, according to your report.

Which is why, I've said to TRY disabling all the OrbX stuff JUST AS A TEST, and see if you still have the problem.

[newmanix]

I'm not the only one saying it. http://www.orbxsystems.com/forum/topic/77249-problem-with-fsdt-klas-and-vector-110-in-p3dv22/?hl=%2Blas+%2Bvegas

[virtuali]

I'm not the only one saying it. http://www.orbxsystems.com/forum/topic/77249-problem-with-fsdt-klas-and-vector-110-in-p3dv22/?hl=%2Blas+%2Bvegas

The last post in the Orbx forum seems to confirm it was a problem of the Orbx vector program which seems to have been fixed with the latest version.

I wasn't *sure* what caused it (I was just sure it wasn't FSDT KLAS, and it wasn't), although I strongly suspected it was an Orbx problem, and the last post seems to confirm it.

[newmanix]

I'm not the only one saying it. http://www.orbxsystems.com/forum/topic/77249-problem-with-fsdt-klas-and-vector-110-in-p3dv22/?hl=%2Blas+%2Bvegas

The last post in the Orbx forum seems to confirm it was a problem of the Orbx vector program which seems to have been fixed with the latest version.

I wasn't *sure* what caused it (I was just sure it wasn't FSDT KLAS, and it wasn't), although I strongly suspected it was an Orbx problem, and the last post seems to confirm it.

Yes. I'll try his fix and if it works, i'll post in both forums just in case anyone else comes accross this problem in the future.