VSIF2VCD: Difference between revisions

From Valve Developer Community
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 13: Line 13:


If all maps were parsed correctly, you should see correctly-named scenes in your game's "scenes" directory, along with some hex-named scenes that weren't found on any map (if there are any).
If all maps were parsed correctly, you should see correctly-named scenes in your game's "scenes" directory, along with some hex-named scenes that weren't found on any map (if there are any).
 
== Changelog ==
;1.1 (April 23, 2012)
*Replaced division with multiplication to possibly increase accuracy.
== External links ==
== External links ==
* [https://skydrive.live.com/redir.aspx?cid=65b4d1e61b5cd82a&resid=65B4D1E61B5CD82A!918&parid=65B4D1E61B5CD82A!188 Download binaries and source code]
* [https://skydrive.live.com/redir.aspx?cid=65b4d1e61b5cd82a&resid=65B4D1E61B5CD82A!918&parid=65B4D1E61B5CD82A!188 Download binaries and source code]

Revision as of 04:16, 23 April 2012

VSIF2VCD is a command line scenes.image decompiler.

Usage

In the command line, type VSIF2VCD "game directory".

Game directory is where gameinfo.txt is located.

The game directory must include the following files:

  • scenes/scenes.image
  • maplist.txt - a text file listing all maps in the game, with Windows line separator.
  • maps/<map name>.bsp or maps/<map name>_l_0.lmp - for each map in maplist.txt.

Because scenes.image stores scene names as CRC hashes, map files are needed for the decompiler to name extracted scene files correctly. Otherwise, scenes will be extracted with unreadable names like a00dba79.vcd.

If all maps were parsed correctly, you should see correctly-named scenes in your game's "scenes" directory, along with some hex-named scenes that weren't found on any map (if there are any).

Changelog

1.1 (April 23, 2012)
  • Replaced division with multiplication to possibly increase accuracy.

External links