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
Reproduced the issue I have told you about: timewarp causes a general overheating.
The temperature is the same for all the parts of the vessel, it is dependent on the warp level, doesn't seem to change during the night, and does not scale linearly with the warp.
The temperature doesn't increase immediately, but seems to grow with an exponential curve settling to a final steady state temperature, suggesting that some for of heat dispersion is still happening (possibly radiation, since this issue is also present in space).
These are the temperatures I measured on the launchapd:
Warp 1x: 26°
Warp 5x: 41°
Warp 10x: 50°
Warp 50x: 66°
Warp 100x: 69°
Warp 1000x: temperature exceeds 2000° and causes everything to explode.
The text was updated successfully, but these errors were encountered:
Update: the specific temperatures seem to depend on the part's size.
The temperatures I reported above refer to 1.25m parts: 2.5 and 3.75m parts seem to overheat more and explode earlier.
I can reproduce the effect with any combination of parts, and both in atmosphere and space.
Reproduced the issue I have told you about: timewarp causes a general overheating.
The temperature is the same for all the parts of the vessel, it is dependent on the warp level, doesn't seem to change during the night, and does not scale linearly with the warp.
The temperature doesn't increase immediately, but seems to grow with an exponential curve settling to a final steady state temperature, suggesting that some for of heat dispersion is still happening (possibly radiation, since this issue is also present in space).
These are the temperatures I measured on the launchapd:
Warp 1x: 26°
Warp 5x: 41°
Warp 10x: 50°
Warp 50x: 66°
Warp 100x: 69°
Warp 1000x: temperature exceeds 2000° and causes everything to explode.
The text was updated successfully, but these errors were encountered: