I have several Vehicle Links in my project, and all of them are linked to either a "Dock" or a "Parking" ramp. Now I have created a sloping 100ft. Mountain (finally figured out how to do that), but since Vehicle Links, just like Taxi Links are 'locked' to the Airport's Elevation (5000ft.). So when I 'draw' a Vehicle Link going up the mountain, it causes the whole mountain to 'flatten' to the airport elevation, is there a way around this? I can use 'Road' Vectors, but, they don't 'Link" to the network which causes a compiling error. Can you 'link' road vectors to the network? If there is a way to 'link' road vectors, that would actually be better, I would like to remove all the vehicle links and replace them with vectors instead, it would make things less of a headache because vectors follow elevations, links don't.
-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
FSX Vehicle Links
- Thread starter Tomt478
- Start date
First, a review of FS2Kx airport infrastructure ground vehicle type links (TaxiPath Type=Vehicle):
https://www.google.com/search?q=ADE...HATG4B1fCBwMwLjLIBwSACAE&sclient=gws-wiz-serp
IIRC, once created properly, you should be able to export Ground Vehicle TaxiPath links from ADE as CSV or XML files.
You can edit them to create source data for CVX Vector placement code using Geographic coordinates of Ground Vehicle link TaxiPath vertices.
Geographic coordinates of Ground Vehicle TaxiPath link vertices as a CSV file can be Imported to Google Earth to then create TaxiPath vertices.
Imported TaxiPath vertices can be 'saved as' by Google Earth ...into a KML data file (data is already projected in EPSG:4326 as required by FS).
Google Earth TaxiPath vertices saved as a KML data file can be converted to a BLN file by rhumbaflappy's KML2BLN utility:
https://www.fsdeveloper.com/forum/threads/kml2bln.310230/
Google Earth TaxiPath vertices saved as a KML data file converted to a BLN file can be Appended to SBuilderX.
The Geographic coordinates of Ground Vehicle TaxiPath link vertices Appended to SBuilderX can then be used to create CVX Road Vectors.
But remember that CVX vectors will be covered up by custom PR imagery land class, and airport infrastructure objects.
Also, CVX vectors will not 'link' to airport infrastructure objects or AI Traffic.
Random non-AI Freeway Traffic can be used with CVX Road vectors, but not airport XML AI Ground Vehicle Traffic.
GaryGB
https://www.google.com/search?q=ADE...HATG4B1fCBwMwLjLIBwSACAE&sclient=gws-wiz-serp
IIRC, once created properly, you should be able to export Ground Vehicle TaxiPath links from ADE as CSV or XML files.
You can edit them to create source data for CVX Vector placement code using Geographic coordinates of Ground Vehicle link TaxiPath vertices.
Geographic coordinates of Ground Vehicle TaxiPath link vertices as a CSV file can be Imported to Google Earth to then create TaxiPath vertices.
Imported TaxiPath vertices can be 'saved as' by Google Earth ...into a KML data file (data is already projected in EPSG:4326 as required by FS).
Google Earth TaxiPath vertices saved as a KML data file can be converted to a BLN file by rhumbaflappy's KML2BLN utility:
https://www.fsdeveloper.com/forum/threads/kml2bln.310230/
Google Earth TaxiPath vertices saved as a KML data file converted to a BLN file can be Appended to SBuilderX.
The Geographic coordinates of Ground Vehicle TaxiPath link vertices Appended to SBuilderX can then be used to create CVX Road Vectors.
But remember that CVX vectors will be covered up by custom PR imagery land class, and airport infrastructure objects.
Also, CVX vectors will not 'link' to airport infrastructure objects or AI Traffic.
Random non-AI Freeway Traffic can be used with CVX Road vectors, but not airport XML AI Ground Vehicle Traffic.
GaryGB
Last edited:
I just decided to do things easier, I just moved my Parking spot to an area at the bottom of the "hill" then moved the "Vehicle Link" to the bottom of the "hill" leaving it connected to the parking spot, then just added a "Road Vector" leading up the "hill" then just added some "Lightposts" for night lighting. I tested it out and it works perfectly, I get a gradual slope up the "Hill" all the way up to 100ft AGL. I'd like to make the "hill" a bit higher but due to space of the area, any steeper hill causes it to be too steep to drive up smoothly. I'm just happy that I was able to finally get the "mountain" thing to work properly, thanks to your help Gary. I just went through and re-read all those old messages from last year when we were working on that and played around with things until I got it to work. It's just a matter of aligning the vertices correctly and making sure they are all set at the proper altitude. It's time consuming, especially if you have a rather large area that you want to slope upward. Also, it only works with a "flatten" background, any others won't slope, in fact it states that in the SDK manual and the ADE manual as well. You just have to read,read, and read some more. Patience is a virtue when it comes to designing.