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
It's a little extra work, but it, you know...works.
They stacked for me. I had a set of three and a set of four; dropped all of 'em from one group, picked 'em all back up again, they stacked into one group.
Potential causes:
1. The tether object count array thinks it is already full (didn't update properly)
2. The tether base object ID for the tether you placed is not the same as the tether base object id of the last tether you placed - this shouldn't be an issue but I've seen other games do this stuff... So if you have 2 tether objects (modules) in your pack and you empty one of them, place a few more from a second tether module, and then go pick up the previous modules tethers they'll place in a new slot because their ID's don't match.
3. A variable is corrupted in the runtime code because someone forgot to encapsulate it.
4. Something on your computer is messing with your ram or your ram is broken.
5. Overclocking can corrupt memory if the temperature gets too high or the overclock is on the edge of stable.
6. Probably many more but it's a very simple bug to fix if it's a code issue.