Snarkpit Forum Index » Source engine editing » Compile Options
Compile Options
1
Post Reply
Quote
 Re: Compile Options
Posted by Dark Tree on Sun Oct 9th at 12:13am 2005

I tried compiling my HL2 map with:

$vis_exe -full (to get a full vis compile)

but it wouldnt compile and gave me this:

Valve Software - vvis.exe (Dec 15 2004)
VBSP: Unknown option "-full"

Command line: "c:program filesvalvesteamsteamapps***sourcesdkbinvvis.exe" "-full" "-game" "c:program filesvalvesteamsteamapps***half-life 2hl2" "c:program filesvalvesteamsteamapps***sourcesdk_contenthl2mapsrc***"

usage : vvis [options...] bspfile
example: vvis -fast c:hl2hl2mapstest

Common options:

-v (or -verbose): Turn on verbose output (also shows more command
-fast : Only do first quick pass on vis calculations.
-mpi : Use VMPI to distribute computations.
-low : Run as an idle-priority process.
env_fog_controller specifies one.

-vproject <directory> : Override the VPROJECT environment variable.
-game <directory> : Same as -vproject.

Other options:
-novconfig : Don't bring up graphical UI on vproject errors.
-radius_override: Force a vis radius, regardless of whether an
-mpi_pw <pw> : Use a password to choose a specific set of VMPI workers.
-threads : Control the number of threads vbsp uses (defaults to the #
or processors on your machine).
-nosort : Don't sort portals (sorting is an optimization).
-tmpin : Make portals come from tmp<mapname>.
-tmpout : Make portals come from tmp<mapname>.

So it gave me a list of optional commands that either made no sense or were completely useless to me. None of them have anything to do with compiling your map with full vis. I thought that was what I did in HL1 but apparently not. What is the command in HL2 to compile maps with full vis?

Also, I tried to compile my map with:

$light_exe -extra (to give the map full a full RAD compile)

Of course...it didn't work and spat this out:


Valve Software - vrad.exe (Mar 8 2005)
----- Radiosity Simulator ----
Command line: "c:program filesvalvesteamsteamapps***sourcesdkbinvrad.exe" "-extra" "-game" "c:program filesvalvesteamsteamapps***half-life 2hl2" "c:program filesvalvesteamsteamapps***sourcesdk_contenthl2mapsrc***"

usage : vrad [options...] bspfile
example: vrad c:hl2hl2mapstest

Common options:

-v (or -verbose): Turn on verbose output (also shows more command
-bounce # : Set max number of bounces (default: 100).
-fast : Quick and dirty lighting.
-low : Run as an idle-priority process.
-mpi : Use VMPI to distribute computations.
-rederror : Show errors in red.

-vproject <directory> : Override the VPROJECT environment variable.
-game <directory> : Same as -vproject.

Other options:
-novconfig : Don't bring up graphical UI on vproject errors.
-dump : Write debugging .txt files.
-dumpnormals : Write normals to debug files.
-threads : Control the number of threads vbsp uses (defaults to the #
or processors on your machine).
-lights <file> : Load a lights file in addition to lights.rad and the
level lights file.
-noextra : Disable supersampling.
-debugextra : Places debugging data in lightmaps to visualize
supersampling.
-smooth # : Set the threshold for smoothing groups, in degrees
(default 45).
-dlightmap : Force direct lighting into different lightmap than
radiosity.
-stoponexit : Wait for a keypress on exit.
-mpi_pw <pw> : Use a password to choose a specific set of VMPI workers.
-nodetaillight : Don't light detail props.
-centersamples : Move sample centers.
-luxeldensity # : Rescale all luxels by the specified amount (default: 1.0).
The number specified must be less than 1.0 or it will be
ignored.
-loghash : Log the sample hash table to samplehash.txt.
-onlydetail : Only light detail props and per-leaf lighting.
-maxdispsamplesize #: Set max displacement sample size (default: 512).

And again....gives me many options OTHER than what I am looking for. Is there no equivelant to "-extra" in HL2?

also, among these options in vis and rad...are there any other special ways to compile like using "-full" and "-extra" to polish a map? Would you suggest "smooth #" or "bounce #"? And if so, how much? Why are full and extra left out fro mthe list of options of how to compile? Why am I such a moron?

I did google AND search this site many times before I posted this, even looking at Leperous' 'expert' compiling options for HL2.

So...how is this done? (full vis and extra rad)




Quote
 Re: Compile Options
Posted by Campaignjunkie on Sun Oct 9th at 12:36am 2005

VIS and RAD are already run on "full" and "extra" by default.

"-smooth" has been made kind of redundant with the addition of smoothing groups in Hammer. As for light bounces, I think the default is 100, so don't worry about that.




Quote
 Re: Compile Options
Posted by omegaslayer on Sun Oct 9th at 1:24am 2005

CP is right, by default they are on full, unless specified to be lower. The only thing I'd coment on is the -bounce. The tool has a built in detector, it will do as many bounces as it can before it recognizes the bounced light as becoming redundant"

you can see this when it goes:
Bounce 1: 150, 120,200;
.
.etc.
.
.
Bounce 8: 0,0,1 (it will stop here because all it is bouncing is black light)

Thats why on some maps you will have 7 bounces, and on others it will be 15, it all depends on how you lit your map.



Posting And You



Quote
 Re: Compile Options
Posted by Dark Tree on Sun Oct 9th at 6:03am 2005

so compiling your map with 'normal' vis and 'normal' rad is the highest setting for each? cool.





1
Post Reply