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
You still have the log though so post that unless this was more than 3 days ago (game deletes logs older than 3 days on launch); if you can't find it, could zip up all the .log files there xD
To send you can use any text or file sharing service, like google drive, dropbox, pastebin, etc. If you don't want it here you can add me on steam or DM it on discord ( @m_digi ).
new Factorum self-destruction could be evaded by using the detach mode...
Do you think it is possible to make an option to turn detach mode off?
Could it be that if someone tries to cut out (Detach Mode) a block there is no reputation drop?
One of my players reported that he could cut out NPC blocks....
Great mod! Thanks for everything you do with modding and helping the community!
Can you can include some details, like the SE log or the mod's log (which is what the folder on screen is about), what block exactly you were detaching and with what mode, etc.
For example, targeting the connecting plane of a modular engine pod, and cleaving the whole thing off cleanly.
It should probably throw an error if the cut point intersects a block (like the middle of a 1x2), and scale grinding time to the number of blocks it would cut through.
Thank you to offer this to the community ❤️ And thanks a lot for keeping this mod up to date ❤️
a f5 reload will always fix it.
I wonder if the same happens for vanilla merge block... if it's even reliably reproducible to begin with though xD
You have to report this on EEM so they fix their unload errors, or at least they catch them to not block other mods from unloading.
I've reported this to keen 2 years ago and they're ignoring it :(
EEM, has been on the save since the start of the play through, roughly 100 hours ago now - we started running into issues of "There was an error while loading the world! Check the log for more information." which is where we found that error, after going through the mods that were added (around 6), AW was the culprit. I can re add it and provide a full log if needed! Love the mod, used to use it all the time :)
Provide the SE log from when you tried it, that should identify one of various posibilities.
https://support.keenswh.com/spaceengineers/pc/topic/27696-advance-welding-merging-2-builds-permanently
If it persists after 2 tries then can you send their client SE log? on steam or DM on discord (@m_digi) if they don't want it here.
Does the lt+rt work elsewhere in the game though? so I can go digging around to see what they're reading =)
Meanwhile you can fix it by going in its terminal and convert it to ship (slap a control panel on it if it doesn't have terminal access)
This should have the same behavior as vanilla merge-blocks in terms of which grid is preserved, higher block count or static or rooted is the one kept.
That sounds pretty bad, can you send blueprints of the ships you merged or the world containing them?
Anyway, THANK YOU. And Digi, thank you for this mod. I like to rearrange my bases a lot... and this (now) will be a huge help.