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
But I understand your concerns. Was just hopping to be able to "close" the gaps on my asteroid base with smooth stone, a not other stuff like steel.. makes not homogen walls =)
Have a great day :)
If that's the case, this mod won't do that for you, all it does is copy the code for a normal Wall and I don't want to change that. But, I also love smooth walls and structures are easy to mod, so once I'm in space I might look into making airtight smooth walls in some fashion.
No promises for rn tho, but I'll post here if something happens
I've gone through and "updated" the mod with 1.5 compatibility
Should work, it just copies the code for walls, then changes which tile set is rendered. I haven't touched the mod's actual code since 2021, so unless they decided to re-work everything from the ground up with 1.5, it should still work lol
<packageId>whooooooooooo.SmoothWalls_copy</packageId>
It's annoying, I know, but it's an undesirable side affect of the fact this mod is designed in such a way that any other mods that change base behavior of walls will also affect this mod.
1) Ensure my mod is higher in the list than that embrasures mod so that it copies the vanilla wall definition instead of the new definition. In fact I would recommend that embrasures mod is loaded in last since other mods may rely on the wall definition as well.
2) Go into the mod definition and change
<ThingDef ParentName="BuildingBase" Name="Wall">
to
<ThingDef ParentName="BuildingBase" Name="MatchingEmbrasures">
The Name field can be literally anything, this is just an example.
<ThingDef ParentName="BuildingBase" Name="Wall">
It overwrites the definition of "Wall", and it appears that the mod author did this as an armature mistake rather than for a good reason. My mod is an extension of wall so that mods that change wall behavior also affects my own mod, which is usually a good thing but turns my walls into embrasures in this buggy case. So what's happening in the load order is this:
1) vanilla code is loaded in and compiled, giving you a wall structure
2) embrasures mod is loaded in and compiled, but it also overwrites (but does not compile since the texpath is different) the vanilla wall definition
3) my mod is loaded in, copies the wall definition, applies a different graphical path/name, and compiles.
So basically it just copies this dude's Embrasures mod and slaps on a new coat of paint. That would certainly explain @Sleban 's bug.
Seems like it's worth checking out, though I don't have time to test until tonight.
Realistic Rooms [1.3]
Wall Lights
Engraved Walls
But I just tested them all running alongside this mod and there is no outdoor penalty to workshops placed inside of smooth walls with a roof.
If you have the patience can you record a short video for me? Hit the Windows key and 'g' key at the same time to bring up Window's built in recording software, and just record yourself building a small room, making sure there is a roof, building something like a workbench, and checking how the work speed is calculated. Maybe check the room using the room stats display option at the bottom right too.
But unless something obvious happens in the video, I doubt we're gonna find the cause unless you manually disable all your mods one by one until you find the one that's creating this weird issue.
Can you show a screenshot? Also, if you replace this wall with a vanilla wall does it solve your problem?
This should also solve @VulpineVandal 's issue.