You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While I first noticed this loading Galileo's Stock Visual Terrain, an installation with only Kopernicus 1.3.1-7 is doing this as well.
Terrain tiles disappear on Eve and Laythe at high altitudes and close approach. I haven't observed this at Kerbin. Terrain colliders are still present, so I can land on it, and I can observe scatter objects 'floating.'
Find attached KSP and Kopernicus logs, one from a stock install, and one from a stock plus Kopernicus 1.3.1-7 including the supplied editions of Modular Flight Integrator and Module Manager. The second set of logs should include the times when I observed the missing terrain tiles.
Testing environment was KSP_x64 on a Windows 10 1709 machine with 32 GB RAM and NVidia GTX 1080. No command line switches used, so I think it's using the stock Direct3D 9 mode.
The text was updated successfully, but these errors were encountered:
While I first noticed this loading Galileo's Stock Visual Terrain, an installation with only Kopernicus 1.3.1-7 is doing this as well.
Terrain tiles disappear on Eve and Laythe at high altitudes and close approach. I haven't observed this at Kerbin. Terrain colliders are still present, so I can land on it, and I can observe scatter objects 'floating.'
Find attached KSP and Kopernicus logs, one from a stock install, and one from a stock plus Kopernicus 1.3.1-7 including the supplied editions of Modular Flight Integrator and Module Manager. The second set of logs should include the times when I observed the missing terrain tiles.
Logs-Testing-131-7.zip
Testing environment was KSP_x64 on a Windows 10 1709 machine with 32 GB RAM and NVidia GTX 1080. No command line switches used, so I think it's using the stock Direct3D 9 mode.
The text was updated successfully, but these errors were encountered: