Terrain disappearing when the camera is close to the ground

[gotmachine]

Transferring the original issue opened in the KSPCF repo by @tony48 and confirmed by @GarwelGarwel

Video of the bug : https://youtu.be/xfpvmWvLrzM
Video 2 : https://youtu.be/TGtglECDghA The bug doesn't seem to occur when switching to a craft at a higher altitude
This occurs in KSRSS when a vessel is landed in some parts (the lowest? see video 2) of the Valles Marineris canyon. When the camera approaches the ground, the terrain completely disappears.
KSP version : 1.12.3
Mods installed :
Harmony 2.2.1
Kopernicus 1.12.1-139
KSRSS reborn branch on gitlab. To install it, download the repo https://gitlab.com/ksrss/KSRSS and copy the KSRSS folder to the KSP GameData.
ModularFlightIntegrator 1.2.10
ModuleManager 4.2.2
(VesselMover 1.12 for testing purposes, I've tested without it and the bug still occurs)
Save file : save.zip
To test, go into the tracking station, select the Buggy 1 craft and fly it. If for some reason the craft is destroyed, teleport a new craft to Mars to these coordinates using the set position in the alt F12 menu : -13.9 latitude, -59.2 longitude.

[R-T-B]

Will look into this for next set of prelease experiments, agree it's in the domain of Kopernicus.

[R-T-B]

Looking at our side of things, this could be happening in the Kopernicus OnDemand system. Can either @tony48 or @GarwelGarwel test the following config, which disables OnDemand (this will inflate ram usage while installed) and see if it fixes the issue? If not, I suspect a stock code bug and will begin investigations there.

Put attatched zipped
DisableOnDemand.zip
cfg file in any GameData folder (I'd suggest GameData/Kopernicus/Config just for ease of management). Let me know the outcome.

[tony48]

@R-T-B The issue still happens with OnDemand disabled. However, ballisticfox found that it is fixed when we remove the VertexHeightNoise mod from the Mars cfg. I think we'll just do this and ignore the problem, it's up to you if you still want to investigate.

[R-T-B]

I'll add a note to look at VertexHeightNoise when I next have a coding window. Thanks for the field testing.