point of putting vis on normal?

[DoctorGordon3]

Yes, quick question:

I put vis on fast, as i find that it compiles....faster. But, im wondering, what are the benefits of just doing it normal?

Same with rad.

 

[Alieni²]

Id like to know too.

 

[Turd Furguson]

Fast vis builds simple vis leafs that aren't too efficent. normal vis lowers r_speeds and makes your level less prone to broken terrain. Increases framerates on complicated maps.

 

[Finger]

Ok, DO NOT release a map, that hasn't gone through the full VIS process!

VIS calculates 'visibility' in the level; deciding at each point, what polygons the engine has to draw, and which it can exclude. Fast or no VIS means that the engine will be drawing MUCH more than it has to; increasing the amount of calculations per Millisecond, and dropping your framerate significantly.

Fast VIS is good for quick compiling, to check stuff out, but a final map should have full VIS calculation.

If you are serious about mapping, I would seriously encourage you to read the SDK documentation about optimizing levels. Also, go here www.snarkpit.com for tons of info on Halflife and Halflife2 mapping. You can also search for Halflife1 tutorials on the VIS process, as it works the same way in HL2.

As for RAD..this calculates the lighting in the level. fast RAD will calculate less light bounces, and give you subpar lighting. Once again; good for quick testing and checking of levels, while in development, but should be compiled on 'extra' for final levels.