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

Runway Properties

Messages
302
Country
us-virginia
Hello Jon,

I apologize if this has been asked and answered, but I'm not able to open an airport.bgl using v1.05 and change and save a runway property - specifically, closed for take-off or closed for landing.

When I make the change and press ok and then re-open the properties box the old setting is still displayed.

I'm going to use bgl2xml to make the change and then recompile using bglcomp, but I was hoping to use ADE. Maybe I'm missing a step, but thought I'd bring it to your attention.

Thanks,
kagazi
 
Hello Jon,

I apologize if this has been asked and answered, but I'm not able to open an airport.bgl using v1.05 and change and save a runway property - specifically, closed for take-off or closed for landing.

When I make the change and press ok and then re-open the properties box the old setting is still displayed.

I'm going to use bgl2xml to make the change and then recompile using bglcomp, but I was hoping to use ADE. Maybe I'm missing a step, but thought I'd bring it to your attention.

Thanks,
kagazi


Hmmm - I need to check that - maybe there is a bug
 
Well I just tried it here with 1.05 and it worked fine for both primary and secondary ends. I have a vague recollection about something to do with different marking settings -
 
Jon
can you remember that there are two settings for closing rwy's for take off/landing
one in Pattern, which is where you should change the rwy settings
and the check boxes, one in each of the Primary and secondary tabs, which i don't know what they are used for could these be the ones Kagazi is using.......
also FS does not always honour closing some rwy's, but should still show in ADE

Ray
 
Ray/Jon that's it. I was making the change in the check box located in the primary and secondary tabs. I went to the pattern tab and made the change there and all is fine. Interestingly, I went back to the primary and secondary tabs and they still indicate the old setting.

Thanks,
kagazi
 
Thats good Kagazi :)
I don't think the check boxes do anything sometimes they appear ticked most times they don't...............
Jon will probably let us know later what they do.....
as far as i know just ignore them..........

Ray
 
Thats good Kagazi :)
I don't think the check boxes do anything sometimes they appear ticked most times they don't...............
Jon will probably let us know later what they do.....
as far as i know just ignore them..........

Ray

Not sure guys - certainly to close a runway end you need to use the check boxes in Markings. The SDK says they do what is on the check boxes on the Primary and Secondary Tabs. They have no visual effect for sure - perhaps they affect ATC and AI traffic - maybe someone else will know for sure if they work or not
 
I used them in my EGCB to turn off RW02 and RW20 which FSX persisted in using. In real life most traffic uses RW27L and RW09R, though RW32 and RW14 are occasionally used. RW27R and 09L are never used unless one is waterlogged. Another one runs in line with RW27L and RW09R but is actually a taxiway, they are all grass, hence the confusion. FSX adds to the confusion by using the taxiway and the middle runway as RW27L and R etc... So using the facility to turn on and off is really useful and does indeed work. However, it has to be done peace meal and FSX forced to accept it. So you sort one runway out, save and reopen, then do another and so on. Coming back to check them all. The alternative being deselecting one runway, go to the next runway to select. Go back to the first one and find its been reselected. Persevere and it begrudgingly accepts what you want it to do. At least, thats what I always find. Had the same effect with an airport that only has 2 runways also.

Reider
________
Honda NS400R
 
Last edited:
Jon,
Appears ADE does what it's supposed to do. I retested the same airport and this time I changed the setting in the pattern tab first and ok'd the change and closed properties. I then reopened properties and made changes to the primary/secondary and ok'd and closed. When I reopened the changes were all showing. I can't explain what happened last night :confused: but seems to work now. I'm going to do a bit more experimenting and I'll let you know if anything unusual shows up.

Regards,
kagazi
 
Jon,
Appears ADE does what it's supposed to do. I retested the same airport and this time I changed the setting in the pattern tab first and ok'd the change and closed properties. I then reopened properties and made changes to the primary/secondary and ok'd and closed. When I reopened the changes were all showing. I can't explain what happened last night :confused: but seems to work now. I'm going to do a bit more experimenting and I'll let you know if anything unusual shows up.

Regards,
kagazi

No worries - if you find something repeatably wrong let us know and we will have a look
 
Back
Top