Установить Steam
войти
|
язык
简体中文 (упрощенный китайский)
繁體中文 (традиционный китайский)
日本語 (японский)
한국어 (корейский)
ไทย (тайский)
Български (болгарский)
Čeština (чешский)
Dansk (датский)
Deutsch (немецкий)
English (английский)
Español - España (испанский — Испания)
Español - Latinoamérica (испанский — Латинская Америка)
Ελληνικά (греческий)
Français (французский)
Italiano (итальянский)
Bahasa Indonesia (индонезийский)
Magyar (венгерский)
Nederlands (нидерландский)
Norsk (норвежский)
Polski (польский)
Português (португальский — Португалия)
Português-Brasil (португальский — Бразилия)
Română (румынский)
Suomi (финский)
Svenska (шведский)
Türkçe (турецкий)
Tiếng Việt (вьетнамский)
Українська (украинский)
Сообщить о проблеме с переводом
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!