Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
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!