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].
SirYodaJedi (talk | contribs) |
m (Setting bug notice hidetested=1 param on page where the bug might not need tested in param specified) |
||
| Line 29: | Line 29: | ||
{{Bug|{{ent|point_message}} texts are treated as sounds by automatic scan. This bug can cause VIDE trying to pack sounds that don't exist!}} | {{Bug|{{ent|point_message}} texts are treated as sounds by automatic scan. This bug can cause VIDE trying to pack sounds that don't exist!}} | ||
{{Bug|Sometimes textures used as <code>$refracttinttexture</code> aren't added by automatic scan.}} | {{Bug|Sometimes textures used as <code>$refracttinttexture</code> aren't added by automatic scan.}} | ||
{{bug|BSPs which have [[BSPZIP#Compression|compressed]] will fail to load in VIDE, and need to be decompressed with [[BSPZIP]] first.}} | {{bug|hidetested=1|BSPs which have [[BSPZIP#Compression|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!. | {{bug|hidetested=1|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}}.}} }} | {{note|The file is sometimes still salvageable if this happens{{clarify}}.}} }} | ||
Revision as of 06:16, 20 May 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
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 $refracttinttexture aren't added by automatic scan. [todo tested in ?]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].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
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
