Hi Chris.
There are a few mesh packages in the Library. They cover LOD5, LOD7 and LOD8.
The LOD5 and LOD7 are worldwide mesh sets. The LOD8 is for the Pacific Theatre only. I would recommend making a new CFS2 copy, and replacing the stock mesh completely... and see how you like it. Earlier threads have covered this.
The reason for this is that some stock mesh for CFS2 was done at LOD9, and the sources were suspicious... some mesh even being grossly misplaced. Also, we don't need LOD9 in the sim, as it doesn't add much, and consumes framerates and disk space.
The LOD8 mesh is trimmed for sea-level... so it shouldn't need a lot of flattens... also saving framerates.
The watermasks can completely replace the stock masks, but will override them if placed in their own folder.
The VTP1 lines ( beaches, streams and roads ) are not done for any of these masks.
The masks and lines need to be redone on an LOD5-sized basis to detail the CFS2 world... just like FS2004 or FSX. And that also requires an intensive use of Ground2K to do the lines. A single LOD5-sized mask plus lines could take a few weeks... multiplied by the size of the world, and it would take decades. For just the Pacific theatre, it would take years for a single developer. We just don't have the right tools, so VTP1s end up hand-drawn.
...so, I recommend tossing out the default VTP1 BGLs if the new masking is used.
As I wrote, the best thing is to remake watermasking, and lines on an LOD5 basis. That is what Sander de Cocq did for Europe... but Sander used FS2004 images for his data in his process. The FS2004 data suffers the same type of misplacements in the sim. My data used SRTM data and masking from various sources, so it fits more realistically. But the masking is rough-hewn, and should be considered as such... covering the world better than the defaults, but not quite as detailed or accurate as we'd like.
Truthfully, we need a tool to convert saved SBuilder ( or SBuilderX ) files to a format that can be compiled to our LWM1 and VTP1 BGLs. That would solve almost all problems. We can convert FS2004 LWM2 assembly files to LWM1 assembly files with Edgar Knobloch's utility, but there is no conversion for VTP2 lines to VTP1. VTP1 lines are an old problem that Sander was working on just before he stopped his CFS2 involvement. Even the Ground2K compilation was a bit rough.
I have asked the old Aces members if they could make the tool available that they used for CFS2 lines and water, but there hasn't been a response. I suspect that tool may be lost. It probably was a GIS tool addon or plugin.... but even the coding of such a plugin would help solve the coding mystery.
EDITED:
Rami's above example shows why more than beaches are needed... the LWM masking needs refinement ( hand-drawn over satellite images ) before the beaches are added. I suggested LOD5 sized, but LOD8 sized could work as well for an airfield package. The LOD8 mesh should still work for such hand-drawn BGLs, as it is based on SRTM data, which is masked for sea-level by LandSat7 imagery.
The only advantage of the rough masking I made here is that it will better blend to detailed hand-drawn masks and shores than the default BGLs at a mid-distance from the airfields. I am stating that position-corrected airfields and target areas also still need detailed LWM and VTP1 BGLs created using Ground2K and satellite or aerial imagery.
Dick