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
that isnt the problem he is talking about. its not a problem with support values.
tc this is a known issue. was reported to the devs already.
the stone portals hitbox is so large that it has trouble detecting the 2x2 floor pieces as ground. no matter what material.
currently there is 2 workarounds : place it on normal ground or place it on the new grausten 4x4 floors. these are big enough and it works on them halfway decently.
one example is that the stone portal will refuse to place on 4x 2x2 marble floors. but you can place it on marble STAIRS that are stacked. the reason is that the hitbox of the stairs is bigger than the 2x2 floor pieces. the portal is unable to detect MULTIPLE smaller floor pieces below it currently. it always only sees 1 even if there is like 10 below it from the feel of it and it doesnt deem that 1 floor as enough space. and thus "invalid placement"
i tested this with all heavy build floor pieces. it applys to them all. includeing the grausten 2x2 pieces. the 4x4 works because 1 of them is big enough that the portal will register it as big enough to place.
will get patched soon hopefully.
also make sure there is enough space ABOVE the portal. its higher than 3 regular wall pieces stacked on each other.
Its not in the exact spot i wanted but its close enough.
Okay good to know. I was unable to find any information on whether or not this was a bug or intentional. Thanks for the info!