Default AFCAD textures at certain angles

[fennelda]

Hi there,

I've noticed in the new Copenhagen (v2) that at certain angles, mainly facing north, default textures from the AFCAD are appearing on top of the scenery textures. I've almost fixed this by editing the AFCAD to make the runways transparent, hold short nodes to HOLD_SHORT_NO_DRAW and taxipaths to type PATH instead of TAXI. The only thing it doesn't fix is the offset threshold arrows, doesn't seem like you can hide those. Is there any way to fix this completely? At most angles it looks great.

[emilios[flytampa]]

I am not able to see this issue here. Could you pinpoint the locations perhaps? maybe a couple of shots?

[johnny_gitara]

Could be something like this? Appears and dissapers with view angle change

[Er!k]

What happens if you disable AI?

[johnny_gitara]

What happens if you disable AI?

I'll report when I finish my flight :)

[Wolkenschreck2]

What a wonderful scenery! Thank you for this new masterpiece, Emilios and Yannis. I can not wait to see what you will achieve with Amsterdam.

Concerning the default textures I can see the same glitches. After a quick look at the AFCAD (af2_ekch_nw_AI.bgl) I found that the draw flags (surface and detail) for 62 elements were still checked. Removing the draw flags resolved the issue for me. Should be an easy fix for Johan when he finds time to update it.

Edit: Saw the same issue with the runway textures. Setting the runway properties to "transparent" solved this too.

Happy Easter to all!

Christoph

[mtbrkhrd]

I'm seeing the same issue of default textures being visible at certain angles.
However the issue disappears if AI is disabled, so I suspect a conflict with AI aircraft. But since this issue only appears with this FlyTampa airport, and not with any other add-on airport I have, there might still be something that Emilios can do about it?

[emilios[flytampa]]

Sure thing, thanks.
We ll have a dedicated AFCAD thread with updates posted up soon

[fennelda]

Concerning the default textures I can see the same glitches. After a quick look at the AFCAD (af2_ekch_nw_AI.bgl) I found that the draw flags (surface and detail) for 62 elements were still checked. Removing the draw flags resolved the issue for me. Should be an easy fix for Johan when he finds time to update it.

Edit: Saw the same issue with the runway textures. Setting the runway properties to "transparent" solved this too.

The default hold short nodes also become visible - you need to set them all to HOLD_SHORT_NO_DRAW intead of HOLD_SHORT (and also the ILS hold shorts).
As I said in my first post, I still haven't found a way to disable to runway threshold arrows, even setting the runway transparent. Any ideas how to do this?

[Er!k]

I'm seeing the same issue of default textures being visible at certain angles.
However the issue disappears if AI is disabled, so I suspect a conflict with AI aircraft. But since this issue only appears with this FlyTampa airport, and not with any other add-on airport I have, there might still be something that Emilios can do about it?

There was a similar issue with Las Vegas... Caused by FSP payware planes... If you rule these out you see that everything is OK

[mtbrkhrd]

There was a similar issue with Las Vegas... Caused by FSP payware planes... If you rule these out you see that everything is OK

Thanks, I suspected as much. I thought Missi had fixed his planes? In any case, I wonder what is different here, since I don't see this issue on any other add-on airport I have.

[emilios[flytampa]]

It seems that it is affected by the ground model materials. Ours is fully P3D v4.5 native. Perhaps adding PBR materials on the ground creates even more problems with this AI package.

[johnny_gitara]

Can confirm also, whem AI traffic is turned off i can't see texture bleedthrough. Time to notify payware AI airplanes maker I guess.

[mtbrkhrd]

I got a message back from Missi, the developer of the FSP AI models.

He says he's working on solving the issue, but he needs to rework every aircraft and that this would take at least 20 days for each type. So it will be many months before this issue is solved completely from his side.
That's rather unfortunate.
So if things could be set to transparent in the AFCAD file, as was suggested further up, this might still be a good work-around for the time being? It is a mystery to me why this is only an issue at FlyTampa Vegas and Copenhagen, and not with any other add-on also using PBR materials.