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

No Parking?

Golf-HotelDelta said:
I'm sorry, I didn't see that comment.

If you have requested take off, the only possibility is "Taxi for take-off options" followed by "Request Taxi - ...".

George
Click to expand...

No its completly seperate, as in once I am cleared to land, vacant runway, then all I have is [Taxi for take-off options]
 
Are you sure you have the radio on and tuned to the correct frequency? I had one occurrance where the master avionics switch was off :o

George
 
I can see one error in the ADE file. It is possible to exit both active runways via Rwy 12/30 and taxiway G without passing through a hold-short node.

You will also find a yellow taxiway line along the length of all runways. You need normal nodes on the centre-line near each end.

George
 
Louimann1 said:
I would try it, but now im getting this odd error keep appearing everytime I try to load up a airport.

I know this isn't the right place for this query, but any ideas? [I have turned everything down to Minimal and it still appears] :confused:
Click to expand...

We have seen this bug related to bad settings in the apron edge lights properties. I thought we had it fixed. Can you make sure (By selecting some edge lights and Editing) that the settings are there and that you have a color shown in the color property. If any value is set to zero then change it. The defaults are separation 60.96m (200ft), brightness 1.0 and color Blue. If this is OK then please attach or send me the BGL file so I can look at it with our test tools.
 
Golf-HotelDelta said:
I can see one error in the ADE file. It is possible to exit both active runways via Rwy 12/30 and taxiway G without passing through a hold-short node.
Click to expand...
Ah yes, I didnt notice that. Its because I added that taxiway last.

Golf-HotelDelta said:
You will also find a yellow taxiway line along the length of all runways. You need normal nodes on the centre-line near each end.
Click to expand...
Im not quite sure I understand what you mean. I dont see a taxiway along the runway?

Louimann1 said:
I would try it, but now im getting this odd error keep appearing everytime I try to load up a airport.

I know this isn't the right place for this query, but any ideas? [I have turned everything down to Minimal and it still appears] :confused:
Click to expand...
Re the error: I have deleted the .ade file from the \addon directory, and it would load up perfectly. Now when I added the original file back in, I got the same error message, and when I put the edited .bgl file back in, still got the error. So does this mean that it is something to do with the .bgl files?
 
Louimann1 said:
Ah yes, I didnt notice that. Its because I added that taxiway last.


Im not quite sure I understand what you mean. I dont see a taxiway along the runway?


Re the error: I have deleted the .ade file from the \addon directory, and it would load up perfectly. Now when I added the original file back in, I got the same error message, and when I put the edited .bgl file back in, still got the error. So does this mean that it is something to do with the .bgl files?
Click to expand...

See my post about apron edge lights and let me see the bgl file please. Also you should not have a .ade file in Addon Scenery, only Bgl files but I assume that is a typo?
 
Last edited:
scruffyduck said:
See my post about apron edge lights and let me see the bgl file please. Also you should not have a .ade file in Addon Scenery, only Bgl files but I assume that is a typo?
Click to expand...

Yeh that is a typo - Too many abbreviations!

Here is the .bgl file:
 

Attachments

Last edited by a moderator:
It seems you were right, as soon as I delete the Apron Lights, Loads perfectly! [And considering I never needed them in the first place for this airfield, Its problem solved for me [For now - Cos im gonna be onto bigger airports which requre them soon!]

But back onto my original question. I have got a screenshot of the ATC panel to show the only option avaliable:
 

Attachments

  • ATC.jpg
    ATC.jpg
    33.5 KB · Views: 484
Louimann1 said:
It seems you were right, as soon as I delete the Apron Lights, Loads perfectly! [And considering I never needed them in the first place for this airfield, Its problem solved for me [For now - Cos im gonna be onto bigger airports which requre them soon!]

But back onto my original question. I have got a screenshot of the ATC panel to show the only option avaliable:
Click to expand...

You are correct - it is the apron eedge lights. At least one of the strips is very short indeed. much below the minimum separation length of 200ft (61m) As a result FSX is running out of memory trying to calculate a spacing that works out below 1m. This is a problem with ADE - we do not have a check in place to deal with very short lengths of lights between vertex points. In the default compile FSX will just ignore them as too short. FSX also fails to generate either a start or end light for the strip. ADE tries to recalculate the spacing to ensure that a light does appear at either end of the strip. The fix at the moment is to ensure that no length of lightin is shorter than the set separation. We will apply some extra code and warnings if the user does this.

As for your second question where is your aircraft and what are you expecting to see?
 
Last edited:
scruffyduck said:
You are correct - it is the apron eedge lights. At least one of the strips is very short indeed. much below the minimum separation length of 200ft (61m) As a result FSX is running out of memory trying to calculate a spacing that works out below 1m. This is a problem with ADE - we do not have a check in place to deal with very short lengths of lights between vertex points. In the default compile FSX will just ignore them as too short. FSX also fails to generate either a start or end light for the strip. ADE tries to recalculate the spacing to ensure that a light does appear at either end of the strip. The fix at the moment is to ensure that no length of lighting is shorter than the set separation. We will apply some extra code and warnings if the user does this.
Click to expand...

Ahh I see, Point Noted :)

-

Answer to original post: Making parking 6.00 metres, allows them to show up on ATC.
 
Last edited by a moderator:
Yiiipiiiiehhhhh yeah yeah yeah.

Uff - that was a hard work to find out this.

We have all to deserved one or more beer.:D
 
You must log in or register to reply here.
Back
Top