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
I explain in more detail here.
https://steamhost.cn/steamcommunity_com/workshop/discussions/18446744073709551615/2147595624110387769/?appid=600480
Firstly, in case anyone doesn't know what normals are: https://blender.stackexchange.com/questions/43462/why-do-normals-exist
Basically, 3D models which have "normals" data need to be kept separate to 3D models which don't have this data. They just need to have different "voCollection" tags. The tags can be literally anything e.g. "carrot" or "sponge". As long as "carrot" only contains 3D models which do have normal data and "sponge" only contains 3D models which do not have normal data.
The mod maker simply need to change the "voCollection" tag for the object causing the issue to something else. In the base game I make the "voCollection" tag for any models without normals to "{collection name}_no_normals" to make sure they are separate.
Hope that helps!