Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Not that this is a cause for your problem, but I would avoid using "Always On" modules just out of operational cleanliness. If your craft isn't running, there is no need for things like gyros, PIDs, and other controller mechanisms to continue to do unnecessary calculations. The easiest solution is to route them through your main power control for the craft.
Im thinking there may be a ram cache limit or cpu limit issue. I don't know for sure. It may just be that the part that is doing the calculations for the physics and controls may be reaching a limit while the visuals are fine.