VSI: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
(More info on how to work with VSI and common issues. More research needed!)
(Console formats aren't used in Companion Collection)
 
Line 7: Line 7:
* {{360}} {{l4d|4}} and {{l4d2|4}}
* {{360}} {{l4d|4}} and {{l4d2|4}}
* {{360}} {{ps3}} [[Portal 2 (Console)]]
* {{360}} {{ps3}} [[Portal 2 (Console)]]
* {{Nsw}} [[Portal Companion Collection]] {{confirm}}
* {{360}} {{ps3}} [[Counter-Strike: Global Offensive (Console)]]
* {{360}} {{ps3}} [[Counter-Strike: Global Offensive (Console)]]



Latest revision as of 07:55, 10 July 2025

Stub

This article or section is a stub. You can help by expanding it.

VSI (short for Valve Stripping Information) is a model-related file format that appears to take VTX and VVD files and remove the LOD data, for Xbox 360 versions of Source Source games. This is probably done to save disk and memory space. Hypothetically, it could be used on PC versions of Source (not recommended). VSI files are generated automatically by MakeGameData during the process of converting models to their proprietary console formats. It is used for processing lighting on models when converting maps.

Games

File format

Unknown, but often only a few bytes in size.

Usage

VSI files are generated automatically by MakeGameData as part of model pre-processing. Any model in a map that is not processed by MakeGameData will appear fullbright in game. VSI files alone are not enough for MakeGameData to process the models correctly and fix the fullbright issue. MakeGameData has to have access to and process all models used in the map, including stock game assets that aren't part of the mod, in order to fix the fullbright issue. Recommended to process maps separately to remedy this issue without causing zip bloat.