Display of transitions from taxiway to apron

[hotelfox]

Please help me with this issue:

In your ADE-Manual (03-29-2008) it says

'Junction Surface Type
Page: 50 of 117
If the links have different surface types then FS will choose the surface type of one of the links to use for the junction surface. FS will take the surface type of the first link clockwise before 270 degrees (true) as the surface type for the junction. This rule is fixed by FSX and it cannot be
changed.'

I am sure that my problem is based on the lines above.

View attachment 5327

The above shows an apron I am currently working on. I wanted to get a clear transition from the taxiway to the apron al along the edges of the apron. But after testing a lot I still get this result:

View attachment 5328

Is there a way to circumnavigate this phenomenon?

Appreciate your help!

 

[scruffyduck]

this does look like the issue of having the taxi link surface different than the apron surface. Generally we would try to avoid that.

 

[Pyscen]

Is there a way to circumnavigate this phenomenon?

Appreciate your help![/QUOTE]

Hotelfox...

I have had similar issues also... I have circumnavigate this by either reversing the direction or changing the path (green line) to Taxi (blue)... either way works. Also looking at the width (radius) (lack of a better term) of the path or taxi... which can cause it.

I have tried to change (correct) this for awhile... What ever works as they say..

 

[hotelfox]

this does look like the issue of having the taxi link surface different than the apron surface. Generally we would try to avoid that.

But these are exactly the details which contribute to the 'face' of an airport. Switching to draw everything in concrete or in any other surface doesn' t sound 'sexy' to me.

Don' t take it personally, Jon. I already have an idea of who created the hazards ...

I have had similar issues also... I have circumnavigate this by either reversing the direction or changing the path (green line) to Taxi (blue)... either way works. Also looking at the width (radius) (lack of a better term) of the path or taxi... which can cause it..

Thanks - I am still in the process of testing. Will include your versions as well!

 

[scruffyduck]

Don' t take it personally, Jon

I don't We work only with the tools that are provided with FSX and the limitations that we find it contains.

 

[GHD]

Is there a way to circumnavigate this phenomenon?

Even some default airports have this problem, eg KLAS:



You can spend hours positioning the transition nodes before you succeed.

 

[hotelfox]

Even some default airports have this problem, eg KLAS:

Doesn' t look like an up-to-date graphics solution, I think.

You can spend hours positioning the transition nodes before you succeed.

Sounds promising
But it' s a rainy Sunday afternoon in Bavaria. Testing probably is one of the better options ...

 

[rfields]

Try changing the width of the apron paths to the parking spots to small numbers - 5 feet, or less.

I've had some success with that.

As Jon said, this is a problem because of the way FS draws surfaces. It is not something we can fix with ADE, but with some detailed work sometimes we can minimize the impact.

 

[glottis]

Jan

try making the path to the taxiway narrower, then add another node to the same path right on the edge of the asphalt taxiway, making sure you then change the short piece of path on the taxiway to asphalt
if that fails to make it less obvious, draw a small asphalt apron along side of the asphalt taxiway the width of the problem area,
and then move the concrete one back the same distance, it is possible to fix this and make it look neater in FSX with a bit of probing around.................

 

[hotelfox]

Jan

try making the path to the taxiway narrower, then add another node to the same path right on the edge of the asphalt taxiway, making sure you then change the short piece of path on the taxiway to asphalt
if that fails to make it less obvious, draw a small asphalt apron along side of the asphalt taxiway the width of the problem area,
and then move the concrete one back the same distance, it is possible to fix this and make it look neater in FSX with a bit of probing around.................

o.k., Ray. I' ll test that. Sounds convincing!

 

[glottis]

Jan

if you look at your first pic you'll see the some nodes are working and some are not,
the ones that are not working put an extra node next to the one already there,
then by moving these two back towards the taxiway may cure this problem,
i think Doug mentioned try reversing the path direction,
this doesn't always work but the double node will, but still worth a try,
maybe a combination of all these and some juggling back and forth should produce a result
I've always been able to fix this by these ideas, Eventually

 

[Pyscen]

Jan

if you look at your first pic you'll see the some nodes are working and some are not,
the ones that are not working put an extra node next to the one already there,
then by moving these two back towards the taxiway may cure this problem,
i think Doug mentioned try reversing the path direction,
this doesn't always work but the double node will, but still worth a try,
maybe a combination of all these and some juggling back and forth should produce a result
I've always been able to fix this by these ideas, Eventually

Eventually, yes We WILL find a way

 

[sddjd]

hotelfox,
Just as an alternate idea, I found that in some tight areas like this creating both surface types as apron worked for me. Keeping in mind the foreground/background priorities of the materials, I've created very detailed apron intersections and then applied apron paths over them instead of taxi paths. The transitional display issues disappeared for me then.