trench issue with 1m setting around Quito?

[Boeing or not going 578]

North of Quito, Ecuador, with mesh slider in p3d to 1m

 

 

[AviatorMoser 353]

Possibly could be a gap in data revealed or created by the 1 m resolution setting. The FreeMeshX data is sampled at 38 m. Do you see this at 5 m or 10 m?

[Boeing or not going 578]

On 3/29/2018 at 9:47 AM, AviatorMoser said:

Possibly could be a gap in data revealed or created by the 1 m resolution setting. The FreeMeshX data is sampled at 38 m. Do you see this at 5 m or 10 m?

I tried other settings and yes I see it still

[AviatorMoser 353]

Okay, I also have a similar issue up in Alaska -- may need to get a new patch out there. This happens when the data misaligns by a single "pixel".

Edited May 6, 2018 by AviatorMoser

[AviatorMoser 353]

If anybody else sees a trench here or there, feel free to let me know where. It will take some time because I'm currently up to my neck with work with paper revisions, but once I submit those, I'll have some breathing room to start fixing some odd defects here and there.

[Boeing or not going 578]

On 5/10/2018 at 4:36 AM, AviatorMoser said:

If anybody else sees a trench here or there, feel free to let me know where. It will take some time because I'm currently up to my neck with work with paper revisions, but once I submit those, I'll have some breathing room to start fixing some odd defects here and there.

happy to help test a patch take your time

[AviatorMoser 353]

Eventually, I'll get to it!