Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem














I don’t understand why you’re saying there’s a viscluster running through the whole map, because that’s factually incorrect. On the V1 map, yes, there was one — but that was because I didn’t know the engine well enough at the time and I made mistakes like that. However, this version doesn’t repeat the same mistake. There is no viscluster at all in this version. I invite you to add me on Discord or Steam so I can send you screenshots of the VMF to prove it to you.
That is a terrible idea. Viscluster the whole map may make compile time faster (ofc), but the map will run like ♥♥♥♥. Because you're not allowing the compiler to do vis optimization. Basically you put the whole map into a single vis. Ex: stuff will render across the map because the engine think its in the same vis. This map will run like ♥♥♥♥ on a multiplayer server.