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
https://www.youtube.com/watch?v=0aGQQHomg5Q&t
I'm following your video step by step. I'm replicating the conditions as close as possible up to using controller (normally mouse keyboard), having the door overlap on the edge of a 16x16 plate and placing the new door 2 studs behind it. For me it the doors work just fine, the new one doesn't break and the old one doesn't re-appear.
I have the impression the door removal isn't correctly being stored to the world chunk so when a new one is placed the previous status is called up again.
My appdata is on an SSD, maybe read/write speed is a variable here?
---
Also that vault door snake is impressive ;) LEGO Worlds has a very powerful physics engine, I remain convinced it's GBC and train derailment capable.
Instead of placing a new door straight into its final location with the Build Tool, you first put the door in a spot where it works and Copy it with a brick (if you just copy a door it won't be visible), now paste the copy into its position. It should overwrite any previous doors or bricks in that location.
This scenario happens (to me) when a brick is placed too close to the door or if the paint tool is used on it.
It's with the Garage Door I ultimately managed to replicate the problem but the copy method solved it for me. Did it work for you?