Installer Steam
log på
|
sprog
简体中文 (forenklet kinesisk)
繁體中文 (traditionelt kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tjekkisk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spanien)
Español – Latinoamérica (spansk – Latinamerika)
Ελληνικά (græsk)
Français (fransk)
Italiano (italiensk)
Bahasa indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (hollandsk)
Norsk
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasilien)
Română (rumænsk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (Vietnamesisk)
Українська (ukrainsk)
Rapporter et oversættelsesproblem














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.