H2V Tool (2007)
This page is incomplete! You can contribute information using GitHub issues or pull requests.
# structure-new-from-ass <ass-file> <use-release> h2tool.exe structure-new-from-ass "scenarios\multi\example\structure\example.ASS" yes
For the example above, Tool would expect to find an ASS file at
data\scenarios\multi\example\structure\example.ASS. Assuming no errors, the ASS file will be compiled into a level at
tags\scenarios\multi\example\structure\example. The scenario name comes from the parent folder name and the BSP name comes from the ASS filename.
Multiple JMS files can be placed in the models directory for multiple BSPs. Each JMS will be compiled into a separate structure BSP and added to the scenario. Scripts and trigger volumes can then be used to switch between the BSPs. Do not do this if you're making a multiplayer map.
<use-release> is unused and was probably related to running either a debug or release version of the toolset. Leave it as "yes".
Same as above, but outputs to the console much more in-depth information on the model while it's being processed. This is only useful if you're a developer that's debugging an import pipeline.
# structure-new-verbose-from-ass <ass-file> h2tool.exe structure-new-verbose-from-ass "scenarios\multi\example\structure\example.ASS"
Tool can be used to generate lightmaps. Using Tool, you will need the following arguments:
- Scenario tag path: This is not a file path! Leave off the ".scenario" extension and start the path from within the tags directory.
- BSP name: The name of the BSP tag without the file extension.
- Lightmap quality: Choose a setting string from the following list. Settings are ordered from lowest to highest.
|Setting||Photon Count||Sample Count||Gather Distance||Antialiasing Samples||Bounced Lighting|
|custom (h2codez-only)||User defined||User defined||User defined||User defined||User Defined|
# lightmaps <scenario> <bsp-name> <quality-setting> h2tool.exe lightmaps "scenarios\multi\example\example" "example" checkerboard
Once you run the command rasterizing should begin. Wait until it finishes and you will be able to see the results in H2V Sapien.
# lightprobes <scenario> <bsp-name> <quality-setting> h2tool.exe lightprobes "scenarios\multi\example\example" "example" checkerboard
# lightmaps_debug <scenario> <bsp-name> <quality-setting> <begin-light-index> <end-light-index> h2tool.exe lightmaps_debug "scenarios\multi\example\example" "example" checkerboard 0 1
TIF, TIFF, uncompressed 32bit TGA, JPEG, and BMP images with a color depth of 24-bits or higher can be compiled into a bitmap tag using the
# bitmaps <source-directory> h2tool.exe bitmaps "characters\cyborg\bitmaps"
For the example above, Tool would expect to find image files at
data\characters\cyborg\bitmaps\. Assuming no errors, each image file will be compiled into a bitmap tag at
tags\characters\cyborg\bitmaps\. Each image file that exists in the source directory will be compiled into it's own individual tag with the name of the tag coming from the image filename.
UTF-16 text files containing strings can be compiled into a multilingual_unicode_string_list using the
# new-strings <source-directory> h2tool.exe new-strings "scenarios\descriptions"
For the example above, Tool would expect to find text files at
data\scenarios\descriptions\. Assuming no errors, a file named "example.txt" would be compiled into
tags\scenarios\descriptions\example.multilingual_unicode_string_list. Each text file that exists in the source directory will be compiled into it's own individual tag with the name of the tag coming from the text filename.
# build-cache-file <scenario> h2tool.exe build-cache-file "scenarios\multi\example\example"
The resulting map file can be found in H2EK's
Checks a structure for errors.
# structure-analyze <scenario_structure_bsp> h2tool.exe structure-analyze "scenarios\multi\example\example"
Checks the scenario for errors.
# scenario-analyze <scenario> <inspection-type> h2tool.exe scenario-analyze "scenarios\multi\example\example" "count tags"
Use one of the following strings for inspection type.
"count tags" "dump tags" "find material references" "count edges" "check effects"
This command does nothing. It might have been used to test progress bars.
# progress-quest h2tool.exe progress-quest
# rebuild-structure-audibility <structure> h2tool.exe rebuild-structure-audibility "scenarios\multi\example\example"