• 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.

MSFS20 Runway and Other Starts

G

GaryGB

Messages
8,958
Country
us-illinois
Hello:

I'd like to better understand how one implements Runway Starts ('other' / Helipad) for grass bush airstrips that have sloped runways (NOT FLAT !).


Does MSFS-2020 SDK XML still allow creation of Runway Starts ('other') for grass bush airstrips that have sloped runways without also creating a SDK default runway type ?

If so, how does one code this, as all the tutorials I have seen thus far show MSFS-2020 Runway Starts as incidental to first placing a SDK default runway type. :banghead:



A substantial proportion of GA flying IRL is now done in Microlight / Ultralight / Sport aircraft from rural airstrips having no ICAO / IATA designation with sloped Runways.

In many cases there is no Runway, but rather just a farm field, and more often than not, it is sloped.


MSFS-2020 SDK GUI appears to require first placing a default Runway that is a flat paved object, with moveable Runway Start Locations at each end.

Are we supposed to position the 'Runway' object, then position the Start locations, and later delete the Runway object ?


If one deletes a Runway object, does this leave Runway Start locations intact as objects separate from a Runway object originally used to insert them into the project ? :scratchch


Also, how would one place a single Helipad 'Start Location' in MSFS-2020 XML code ? o_O

GaryGB
 
Last edited:
I can't answer this in respect of the internal design tools but using ADE 2020 Alpha I am able to place both the helipad start and other runway start. There are no errors thrown in the build but only the actual runway starts appear in the start position list:

1603790740336.png


There are a number of airport elements which are accepted by the packagetool/compilers but which do not show in the sim
 
Thanks, Jon. :)

As in ADE version 1.79.7475, MSFS SDK GUI deletes associated "Runway" Starts if a "Runway" is deleted.

AFAIK, one may opt to instead use a "Helipad" Start to replace a "Runway" Start on non-level terrain.


EGCW RWY_04-22 was deleted in ADE after the RWY Starts were replaced via Add... > Other Start > Helipad using RWY Start position data from the de-compiled EGCW *.XML.

Welshpool Airport - Wikipedia

en.wikipedia.org en.wikipedia.org


Can the Alpha build of ADE for MSFS-2020 compile using a "Helipad" Start type to replace a "Runway" Start type at ex: EGCW ...if processed outside the MSFS SDK GUI ?


If so, I would be grateful if you could please attach the MSFS-2020 airport source *.XML, and a compiled MSFS-2020 project file / folder set for EGCW, either in this thread ...or via PM.


PS: I have attached below, the *.AD4 files for EGCW derived from FSX Acceleration via BGL2XML 1.8x and ADE version 1.79.7475 for prospective study and testing.


Thanks for your further consideration in helping us to better understand what MSFS-2020 SDK currently allows us to compile ...if processed outside the MSFS-2020 SDK GUI. :teacher:

GaryGB
 

Attachments

Last edited:
So to be clear you want to delete the runway and replace the starts with Helipad type or other type.

Generated a FS2020 project using the FSX version of EGCW. Added helipad starts in place of runway starts and deleted the runway and it's starts.

Built it - no compiler errors.

The result is no starts placed

1603871465420.png


I will check but my guess is this is another airport or scenery element that is in the schema and compiles but is not rendered in sim at this time
 
The immediate reply from Asobo is that the other start is not implemented. That is, it is compiled but currently ignored by the sim.

I am running a couple more checks
 
I have moved this to it's own thread since things appear more complicated than first thought. The outcome may be the same that helipad starts are not implemented but the schema types for RunwayStart and (Other)Start are different in MSFS than FSX and I need to make sure ADE is generating the completely correct code before closing this off
 
Hi Jon:

Thanks for looking into this, and I agree this sub-topic merits its own thread. :)

I was concerned that Asobo might have purposefully not implemented Helipads yet, as they have also not yet implemented Helicopter flight in MSFS-2020.

If you are aware of a way that a POI could be found via a ICAO code search in the MSFS GUI "airport" list, and used to launch flights, perhaps that might be considered as a way to make MSFS more functional for those wishing to develop bush / farm airstrips (but NOT Helipads per se) ....without having to utilize the terra-forming feature set.

Alternatively, is there a way to disable run time display of both a flat / hard surface and texture for MSFS SDK-compliant "runways" by ex: using a narrow or "0" Meter RWY width ? :scratchch

Thanks again in advance for your reply on this. :coffee:

GaryGB
 
Last edited:
I can pretty much confirm that the only start types that will appear in the airport list of start positions are those designated RUNWAY with a valid runway number/designator. types HELIPAD and WATER do not appear in the list of start positions although they compile correctly. A new type TRACK shown in the schema for MSFS causes a compiler error of invalid type tag. I have reported this to my ASB contact. It probably also needs reporting on Zendesk. This is now closed off for me until a fix is provided
 
GaryGB said:
Alternatively, is there a way to disable run time display of both a flat surface and texture for MSFS SDK-compliant "runways" by ex: using a narrow or "0" Meter RWY width ? :scratchch
Click to expand...

Hi Jon:

Does MSFS-2020 SDK currently allow us to suppress the run time RWY flat / hard surface and texture display via a minimum or "0" Meter RWY width parameter value in the *.XML source code ...as we are able to do in prior versions of MS- FS2Kx ?

Alternatively, can the MSFS-2020 ADE version feature a POI substitution for an ARP, in a type of add-on Package that enables a MSFS startup map query for an ICAO (or other max. 5-digit ID string), that can be used to spawn a flight with a "start location" at the POI's assigned Geographic coordinates and altitude with an aircraft in the 'on-ground' position ?

Otherwise, IIUC, we may have to resort to saved *.FLT files, until Asobo implements more fully the planned Helicopter flight features, and also enables Water RWYs for seaplane flight (which is already largely implemented) ...in MSFS-2020. :scratchch

GaryGB
 
Last edited:
The runway element in MSFS has a property for transparency. Set to true this does appear to hide the runway. Runway Starts still appear to work.
 
Thanks, Jon.

That is good news for some types of airfield development scenarios, as some might prefer a 'flattened' / hard RWY surface superimposed over their Bing imagery textures. :)

IIUC, a flattened / hard surface at a specified altitude would still be present, and could be terra-formed via MSFS SDK GUI before hiding the default RWY texture ? :scratchch

GaryGB
 
Last edited:
You must log in or register to reply here.
Back
Top