AviatorMoser

Hi folks, Thanks for the community support. I really appreciate people stepping up to help others out. I stepped away from flight simulation for about half a year for a nice, healthy hiatus. Eventually, I'll get around to release a patch to fix some remaining issues.

You'll definitely notice a difference at low altitude if it's installed correctly. It's a 10-m mesh. That's 16X the data density of the stock mesh.The OP needs to double check their scenery library as that is usually the problem with most issues where no improvement is visible.

Yes, riG has hit the nail on the head. Because of the uptick in traffic for FreeMeshX and the increased costs of file sharing, direct downloads are no longer an option.

Eventually, I'll get to it!

Hi Boeing, Unfortunately, this almost impossible to diagnose.

I think these defects are still there and need to be corrected in the next patch as well. I'm currently rounding up major artifacts that stand out.

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.

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".

Thanks @MatthiasKNU

I'm puzzled. Looks like a couple of the vectors are very unaligned with the mesh. Generally, it's not a good idea to run a mesh without replacing the vectors as well.

The Vectors reinstall should be fairly simple with FTX Central these days. You just click on the icon in Central, and an uninstall option should be there. Then when it's uninstalled, just reinstall it with Central. Vectors is pretty much self contained within its folders, so I suspect Central wipes out those folders and the Scenery Library entries. As for why this problem occurs, I'm not sure. The AEC tool takes advantage of a "feature" or "bug" of the ESP engine where the altitude of an airport can be changed by loading in a dummy APX file early in the load order that changes the elevation of the airport irregardless of the elevation in the actual APX file that is load later. I think that's how it works, but I'm not positive. Somehow, FTX Vector gets corrupted and the airport elevations can become changed, but the other vector information in CVX files do not automatically adjust to the new airport elevation, and then you see effects where taxiways are sitting at the old elevation while the runways are at the corrected elevation. The whole elevation adjustment system in the ESP engine is very whacky and I'm a huge proponent of changing away from its 20 year old architecture. I hope this somehow helps.

If you are still running into sunken runways or raised taxiways, then I only had fixed this with a Vectors reinstall. I'm not sure why this happens, as it's only happened to me once.

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?

@Rusty Gunz This sounds exactly like a Vectors issue. Are you running FTX Vectors? It had corrupted in the past for me and I found trees and sunken runways all over the place. Ultimately, I had to reinstall FTX Vectors to fix it. This isn't mesh related.

It's always a mistake to not read either. If you read the question by @kiki, he was asking what dynamic lighting does, and I gave him a brief explanation and demo video of software where it's application is obvious. The English language exists so that people can read and understand each other, quite effectively I might add.