This article's documentation is for anything that uses the Source engine. Click here for more information.

VVIS++

From Valve Developer Community
Jump to navigation Jump to search

English (en)Русский (ru)Translate (Translate)

VBSP++VVIS++VRAD++BSPZIP++

This article or section is a stub. You can help by expanding it.
Comparison between regular VVIS's and VVIS++'s compile speed. VVIS++ compiles visibility data significantly faster than regular VVIS.
Developer(s)
Initial release
Aug 4, 2025
Stable release
May 4, 2026
Operating system
Windows
Type
Map compiler
Target engine(s)
Source
Distribution
Freeware

VVIS++ VVIS++ is a community-made modification of Source's VVIS developed by ficool2. It significantly reduces VVIS compile times, while providing the same result as regular VVIS.

Differences

  • Depending how big the map is, or how the map was optimized, and the CPU, VVIS++ will be 50% to 2700% faster compared to original VVIS.
  • Scales up to 64 threads
  • Added AppID mounting in gameinfo.txt
  • Deprecated func_viscluster, as VVIS++ is fast enough that visclusters aren't needed anymore and using visclusters will hinder VVIS++ optimizations.
  • Removed VMPI, possibly because VVIS++ is fast enough that VMPI isn't needed anymore.

Compile Comparison

Map - d2_coast_01 (pre-Anniversary)
  • Stock VVIS (64-bit, HL2:DM 20th)
    • i5-3470S (2.9GHz base, 3.2GHz boost, no AVX2, 4 cores & 4 threads) - 2:23:39 (VVIS only), 2:25:12 (total incl. stock VBSP, VRAD)
    • i5-12400F (2.5GHz base, 4.0GHz boost, AVX2, 6 cores & 12 threads) - 38:32 (VVIS only), 39:53 (total incl. stock VBSP, VRAD)
  • VVIS++ (64-bit, HL2:DM 20th)
    • i5-3470S (2.9GHz base, 3.2GHz boost, no AVX2, 4 cores & 4 threads) - 7:21 (VVIS++ only), 7:50 (total incl. VBSP++, VRAD++)
    • i5-12400F (2.5GHz base, 4.0GHz boost, AVX2, 6 cores & 12 threads) - 1:30 (VVIS++ only), 1:38 (total incl. VBSP++, VRAD++)
Note.pngNote: Pre-Anniversary (Xbox 360/Orange Box) version of the map, no visclusters, compiled using 64-bit VVIS shipped with HL2: Deathmatch (20th Anniversary version) and VVIS++. Additionally, VRAD++ with -both works differently, as LDR lighting data will be redirected to HDR, saving the VRAD compile time and total compile time.
Note.pngNote: On the i5-3470S system, Meltdown and Spectre security patch is enabled. Both system runs Windows 11 IoT Enterprise LTSC 2024.

Supported games

VVIS++ is supported for all games on Source 2013 Source 2013 (Half-Life 2 incl. it's episodes and Portal, and the Team Fortress 2 branch Team Fortress 2 branch), Left 4 Dead engine branch Left 4 Dead engine branch (and later), Source Filmmaker Source Filmmaker and Garry's Mod Garry's Mod.

Other games/mods tested & additional notes

VVIS++ has been also tested with the following games, other VBSPs or engine branch:

Game Engine branch (game) VVIS++ Version Notes ViewDiscuss
All Source 2013 Singleplayer Source 2013 Singleplayer games
Half-Life 2 Half-Life 2 (including Episodes)
Half-Life: Source Half-Life: Source
Portal Portal
Source 2013 Singleplayer N/A (Universal) Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to a Source 2013 SP game's bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 SP game and edit the BSP executable pointer to $SteamUserDir\Your Source 2013 SP game\bin\x64\vvisplusplus.exe, or use the tool from the command-line.
All Source 2013 Multiplayer Source 2013 Multiplayer games Source 2013 Multiplayer N/A (Universal) Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to a Source 2013 MP game's bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 MP game and edit the BSP executable pointer to $SteamUserDir\Your Source 2013 SP game\bin\x64\vvisplusplus.exe, or use the tool from the command-line.
All Source 2004 Source 2004 and Source 2006 Source 2006 games Source 2004
Source 2006
Team Fortress 2 branch (before Apr 6) Not supported. VVIS++ can read Source 2004 and 2006's .bsp (meaning it is compatible with Source 2004/2006's VBSP), however, Source 2004 & 2006's VRAD will fail to compile maps compiled with VVIS++.
Left 4 Dead Left 4 Dead Left 4 Dead engine branch N/A (Universal) Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to Left 4 Dead 2's (or games running on L4D branch) bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 MP game and edit the BSP executable pointer to $SteamUserDir\Left 4 Dead 2\bin\x64\vvisplusplus.exe, or use the tool from the command-line.
Left 4 Dead 2 Left 4 Dead 2 Left 4 Dead engine branch N/A (Universal)
Team Fortress 2 branch (before Apr 6 VVIS++ update)
Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to Left 4 Dead 2's (or games running on L4D branch) bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 MP game and edit the BSP executable pointer to $SteamUserDir\Left 4 Dead 2\bin\x64\vvisplusplus.exe, or use the tool from the command-line.
Alien Swarm Alien Swarm Alien Swarm engine branch N/A (Universal) Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to Alien Swarm's (or games running on Alien Swarm branch) bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 MP game and edit the BSP executable pointer to $SteamUserDir\Alien Swarm\bin\x64\vvisplusplus.exe, or use the tool from the command-line.
Portal 2 Portal 2 Portal 2 engine branch N/A (Universal) Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to Portal 2's (or games running on Portal 2 branch) bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 MP game and edit the BSP executable pointer to $SteamUserDir\Portal 2\bin\x64\vvisplusplus.exe, or use the tool from the command-line.
Counter-Strike: Global Offensive Counter-Strike: Global Offensive CS:GO engine branch N/A (Universal) Installation:
   First method: Extract "tools_plusplus" folder, then run toolsplusplus_installer.exe, pointing it to the game root directory.
   Second method: Install the tool to CS:GO's (or games running on CS:GO branch) bin/x64 folder (you will need to create the "x64" folder), then go to compatibility folder and drop all the .dll files into x64 folder.
After installing VBSP++, either open Hammer (or Hammer++) in your Source 2013 MP game and edit the BSP executable pointer to $SteamUserDir\Counter-Strike: Global Offensive\bin\x64\vvisplusplus.exe (or $SteamUserDir\csgo legacy\bin\x64\vvisplusplus.exe), or use the tool from the command-line.
Mapbase Mapbase games or Mapbase's VBSP Source 2013 Singleplayer with Mapbase N/A (Universal) BSPs generated by Mapbase's VBSP are compatible with VVIS++. For installation, follow the same instructions as Source 2013 SP games.
Tip.pngTip: Since VVIS++ is completely standalone, instead of installing it on the x64 folder you have created, you can put VVIS++ anywhere (in a different folder for example) and the tool will work.

System Requirements

  • VVIS++ supports any 64-bit processors (CPU), but it can take advantage of AVX2 (Intel Core series - since 2013 (Haswell), Celeron and Pentium - since 2020 (Tiger Lake) or AMD Excavator - since 2015) if the CPU supports it.
  • CPU with AVX2 support would compile maps much faster than CPU without AVX2.

External links

Navigation