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
I figured I'd start this off here, since if definitely seems related to EVE:
I'm playing with the Reality Overhaul and I've discovered a vexing issue: At certain launch sites (I've not experienced it yet at the default one, but it might be a coincidence) when I reach exactly 6000m, BAM! My ship explosively tears itself apart. The logs don't mention any collisions or anything, just structural failures. I also noticed that this only seemed to happen if I had cloud cover at the site, and sure enough, if I disable the cloudLayers.cfg file, the problem disappears.
What's puzzling is that the config entry for Kerbin ("Earth") places the clouds at 4000m, though it's possible that somehow the scaling of Kerbin to Earth size causes them to appear at exactly 6000m instead.
I do see lots of NRE messages as per issue #22, but I don't have any reason to think they're related.
The text was updated successfully, but these errors were encountered:
I figured I'd start this off here, since if definitely seems related to EVE:
I'm playing with the Reality Overhaul and I've discovered a vexing issue: At certain launch sites (I've not experienced it yet at the default one, but it might be a coincidence) when I reach exactly 6000m, BAM! My ship explosively tears itself apart. The logs don't mention any collisions or anything, just structural failures. I also noticed that this only seemed to happen if I had cloud cover at the site, and sure enough, if I disable the cloudLayers.cfg file, the problem disappears.
What's puzzling is that the config entry for Kerbin ("Earth") places the clouds at 4000m, though it's possible that somehow the scaling of Kerbin to Earth size causes them to appear at exactly 6000m instead.
I do see lots of NRE messages as per issue #22, but I don't have any reason to think they're related.
The text was updated successfully, but these errors were encountered: