P3D stock mesh error

[Martyson]

@Bavarello,

Have you tested this location and done screenshots?

"80 Nm on the radial 128 of VUE VOR"

[Bavarello]

You said :
"However, the nearest airport is Luena FNUE"
"80 Nm on the radial 128 of VUE VOR"
"I believe that this anomaly is present everywhere."

Were your screenshots taken there?

https://imgur.com/Wf0Zfp5


https://imgur.com/7VmjURd

[Martyson]

I did a short video (better than screenshots).

https://youtu.be/XV81p2HPut0

[Bavarello]

I did a short video (better than screenshots).

Good idea Martyson make the video .... thanks for your time!
I believe you agree that on your sim, you see the anomaly of the autogen. Even if on my sim it is more marked.

https://imgur.com/cbpki1J



https://imgur.com/w2gmnu6


https://imgur.com/eiqoG7F


I highlighted with black lines. The anomaly has a direction from north to south, like pattern QMID13

[druco]

I did a short video (better than screenshots).

Thank you Martynson once more for you time and support.

Good idea Martyson make the video .... thanks for your time!
I believe you agree that on your sim, you see the anomaly of the autogen. Even if on my sim it is more marked.

I highlighted with black lines. The anomaly has a direction from north to south, like pattern QMID13

exactly ... as soon as Martynson puts the vegetation at its maximum, the empty lines appear immediately.
And as we can see the error occurs in two completely different and distanced areas.
In my case, as I reported from the beginning, the error was noted at the CP NDB zone west of FNMA


Thank you both for your support

[Bavarello]

I wonder if a solution will be found for this anomaly? We had two important hot fixes ... but on this issue, absolute silence. How long do we still have to wait for a solution?
It has been seen by thousands of users ... but I don't see any feedback.

[Barksdale]

It's probably one of those situations where the obvious suspects aren't causing the issue. Patience and I'm sure someone will figure it out.

[Spencer Nelson]

Hey everyone,

Thanks for all of the information! We are aware of this issue and are working towards a fix.

Spencer

[druco]

Hey everyone,

Thanks for all of the information! We are aware of this issue and are working towards a fix.

Spencer

Thanks Spencer, we look forward on this fix