VIDE: Difference between revisions
Jump to navigation
Jump to search
Bug:Automatic scan doesn't add custom decals. [todo tested in ?]
Bug:point_message texts are treated as sounds by automatic scan. This bug can cause VIDE trying to pack sounds that don't exist! [todo tested in ?]
Bug:Sometimes textures used as
Bug:BSPs which have compressed will fail to load in VIDE, and need to be decompressed with BSPZIP first.
Bug:The CRC resource is not correctly edited or stripped when using the VTF Editor. Resaving a VTF which contains a CRC will result in a corrupted file!.
Note:The file is sometimes still salvageable if this happens[Clarify].
Adidores1054 (talk | contribs) No edit summary |
Adidores1054 (talk | contribs) No edit summary |
||
| Line 2: | Line 2: | ||
{{SoftwareBox | {{SoftwareBox | ||
| title = | | title = {{vide|4}} | ||
| developer = riintouge | | developer = riintouge | ||
| initial_release = Dec 25, 2009 | | initial_release = Dec 25, 2009 | ||
Latest revision as of 04:00, 1 November 2025
VIDE, or the Valve IDE, is a third-party tool used by Source developers and mappers. Its primary feature is the embedding of custom content into a .bsp map file and features a mass VTF/VMT editor.
Features
- Hammer Splitter Editor
- Package Viewer (equivalent to
GCFScape) - Particle Editor
- VBSP Editor
- VMT Editor
- Mass VMT Editor
- VTF Editor (equivalent to
VTFEdit) - Mass VTF Editor
- BSP Info
- Entity Lump Editor (equivalent to Entspy)
- Pakfile Lump Editor (equivalent to Pakrat)
Tutorial
There is a tutorial by TopHATTWaffle on his website, here.
Download
Bugs
$refracttinttexture aren't added by automatic scan. [todo tested in ?]See also
- Third Party Tools
- Pakrat - An alternative program to the VIDE, albeit deprecated.
- Compile Pal - Can pack into the BSP as part of the compile setup
- Compiling
- Entspy
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||