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 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.