Runway Edge Pavement

[jvile]

ADE will not let you add have more than 255 because it knows about the compiler error

Thanks Jon

I could not remember if we matched the limits the compiler gives with what ADE looks for.

 

[flyboy]

I just posted something related to this though Im not noticing anything in FSX except I see what I created in ADE. However, though I have edge-lines, I have no paved edges... which I would like.. This original post is a few years old so maybe there has been some type of fix...
I have 3 runways...
1. runway 13/31 with 13 being the primary.
This runway has an offset threshold on the secondary side.
2. Runway South that is 3.4 in length with a blast This one is 180 degrees to the runway so that the chevrons point the same direction (31)
3. North is same as 2, however for chevron direction it is primary runway heading (13)
Both of these are extra runways I am using for appearance since they have the chevrons already. I modified the runway length (greater than 3.3), names and identifiers since I couldn't compile as they were.

So, the question is, does any of this affect me paved edges?
If not, what does?
Thanks

 

[jvile]

You have 3 runways for SABE?

What is going to stop ATC from assigning the other 2 runways for landing.

 

[flyboy]

You have 3 runways for SABE?

What is going to stop ATC from assigning the other 2 runways for landing.

Good Question Jim...
I was trying to get the blast pads for both headings since the real airport shows them and the overun, gives me the arrows on the 31 side. (See Image)
If there is a better way, I could use it but thought the line up was important...
So, Main airport 13/32 with overun on 32 side giver me the white arrows shown in image & the two other runways are basically the same with the lengths and orientation rotated 180 degrees to control the yellow chevron direction.
I am open to other techniques...

 

[flyboy]

I understand about the overun.. I had a bit to extend to the blast pad.. but without it, the paved edge comes back...

Here is an image with the 13 blastpad next to runway 13. both have on overrun... But it leaves the area in between disconnected

 

[jvile]

Increase the length of the runway to 6870 ft.

For runway 13 use a 50 ft displaced threshold and a 750 ft blast pad

For runway 31 add the 427 ft displaced threshold then add a 510 ft blast pad

In the markings tab check

edge lines
edge payment
no threshold end arrows

 

[flyboy]

My runway is 6890
If I displace it, the threshold is off and the arrows show that aren't there.
On top of it the blast pad doesnt lign up.
Image 1 2 runways. (Both Chevrons and Approach lights lign up with original)
image 2 1 runway (Arrows dont go away although box is checked, and chevrons dont lign up)
If I could edit the chevron position and spacing as well as the approach lights, it would be great but I don't think that is an option.

 

[Aaron Parsons]

The markings in real world and based on the generic template FS uses will probably never match up perfectly. Look at the Runway Threshold markings...6 instead of 10...since I wanted my runway to be more actual-looking, I have gone and made my runway 0' wide and hidden all the lights from the runway. I'll be using lights created from AFLT placed in the spots identifiable on the map image (on zoom 18, I can see the actual DOTS where the lights are either free-standing or sunk into the pavement). A bit more work, but very representative of the actual airport. Once that is set, I will re-expand the runway and remove all markings and attempt to make invisible. It has to have some width for AI purposes. Using an apron for the runway has no issues for the user that I have seen.

 

[jvile]

Have you considered using the ADE Ground Poly utility and draw the apron and chevrons?