FSDreamTeam forum
General Category => General Discussion => Topic started by: specialist on June 02, 2017, 10:01:38 pm
-
In trying to figure out why I can't get KLAS elevation corrected with ORBX scenery, I posted this screenshot at ORBX in the course of our discussion, and realize that unlike before, all my FSDT, and for that matter, Flightbeam's scenery too, shows up in the list as a light grey color, like it's inactive or something. Obviously is not, but never the less, there you go. Also, when I run ORBX vector config tool, it use to mush all my scenery below ORBX, but now it doesn't or cant after trying the new installer method. Just curious if this is normal on how it suppose to look.
http://i90.photobucket.com/albums/k261/specialist/fsdt_zpsbkxbjiwm.jpg (http://i90.photobucket.com/albums/k261/specialist/fsdt_zpsbkxbjiwm.jpg)
-
That's entirely normal and it's how the new scenery configuration system works.
Also, when I run ORBX vector config tool, it use to mush all my scenery below ORBX, but now it doesn't or cant after trying the new installer method. Just curious if this is normal on how it suppose to look.
I don't think it's a good idea having a vector scenery on top of airports. And in fact, we keep getting many reports of conflict caused by that product so, I wonder if this is because it's always placed on the top of everything.
-
You have a point there, it could be one reason why the reports of conflict are caused. I know that I always have to keep bringing one of my LatinVFR airports to the top every time I run that vector config tool. If I don't the hills by runway 27 at KSAN just eats up the airport, and you can't see it.