From Valve Developer Community
Jump to: navigation, search

Changes 12/15/09

Updated the section about fast mode and whatnot to try and clear up some confusion and imply that you should try to always run VIS on full. Let me know if this helps/if someone can see it working better another way. --LordNed 02:43, 26 December 2009 (UTC)


When i compiled my map with vis it messed up my map. Can anyone help me with this.

  • I would but that map is long gone. I haven't used vis since that happened. what actually happened was that after i used vis and them made more changes to the map, none of the changes appeared.Cubedude 17:16, 2 Feb 2006 (PST)
I have another question about compiling with vis. For water to appear correctly do you have to compile with vis. Cubedude 10:31, 4 Feb 2006 (PST)

So is this compiler called vvis, VVIS, VVis or Vvis? --Andreasen 03:32, 8 Mar 2006 (PST)

Well, since it's an acronym (though I don't know what from), I'd say VVIS. Jupix 03:35, 8 Mar 2006 (PST)
But what if "vis" stands for "visibility"? Then the vis should normally be written "Vis" instead, like "VVis". I'd like to know what the inventor of this program called it. --Andreasen 07:46, 8 Mar 2006 (PST)
Good point, sounds plausible. Jupix 23:58, 11 Mar 2006 (PST)
I believe it's safe to refer to VVIS as VIS or vis, I always do and everyone know right away what I'm referring to. --wisemx 04:09, 12 Mar 2006 (PST)
Aha, so THAT's what "vis" is. It could mean line-of-sight visual, or have something to do with visgroup, or in-game visual effects from VVis. Anyway, I'm looking for some consistency when refering to the actual program, and searching through vvis.dll, I found it being referenced to as "VVIS" ONCE. The rest of the time it's called "vvis", so I'm confused, but as the program is also called "vvis.exe", and is refered to as "vvis.exe" in the compiler, I'm going to go with "vvis". --Andreasen 12:52, 29 Mar 2006 (PST)
The first V in vvis (and in vbsp and vrad) almost definatly stands for Valve, although I have no solid evidence of this. Also, vis and bsp are used in compiling for older engines such as idTech 3 and Quake 3, so I would asume the abreviaions of the last part of the same. Also, I'd gues that the last part in vvis (vis) stands for Visibility, making the full acronym (or abreviation) Valve Visibility.--Levybreak 04:38, 18 May 2008 (PDT)

Why my map takes so long time (15min) to run vvis (PortalFlow takes most of the time)? It has no leaks and isn't "huge" map. Does it normally take so long with it? --nom1nator 18:48, 18 February 2009 (UTC)

Ok, fixed the problem. The problem was "WARNING: Cluster portals saw into cluster" error, and I just tied some complex structures to func_detail, so now it runs in few minutes. --nom1nator 18:48, 18 February 2009 (UTC)

Computer Hardware

I have a dual core machine with 2 GB of system RAM. Which is more likely to decrease VVIS compile time: a faster, quad-core processor or 4-12 more GB of RAM? Does anyone know? --Corion 21:38, 18 September 2009 (UTC)

The new processor. VVIS never gets anywhere near 2GB of memory unless your map has ludicrously low lightmap scales. --TomEdwards 08:40, 19 September 2009 (UTC)
Hey wait, this is VVIS. I thought you were asking about VRAD. If VIS stake more than a few minutes, it means you need to optimise visibility. --TomEdwards 08:41, 19 September 2009 (UTC)