fast vis? Created 17 years ago2006-09-07 10:37:25 UTC by crazylf2

i'd like to ask would fast vis decreased the r_speed ?
there are any different of full VIS or fast VIS ???

No fast VIS is a way of compiling faster if you want to simply test the map in seconds...It does a lousy job compared to normal and I don't suggest it.

Yeah, the lighting and a few other things will come out rather ugly in fast VIS compared to a full VIS compile. As Habboi said, use it for testing if you can't be bothered waiting for a full compile.

I don't notice i gigantic difference in lighting between normal and fast VIS, but I know for sure your r_speeds will be super-high! (On fast, VIS spends far less time calculating what you'll be able to see at any given point in the game, so lots of stuff is rendered unecessarily)

There is absolutely no reason to sit through an entire--regular--VIS compile for most stages of a map's construction imo, especially if the map is huge--you'll spend a lot of time waiting!

For the final stages of your map though, it's absolutely essential, so you among other things, get the lowest r_speeds you can.

the lighting and a few other things will come out rather ugly in fast VIS compared to a full VIS compile.

Lots of people say this--which I'm franky kinda tired of--, but I've never noticed much of an impact on lighting, or anything else really except r_speeds, so I decided to do a simple test:

Fast and normal VIS compiles for my example twisted map:

Normal:

Fast:

They look virtually identical to me If you have a better example to prove me wrong, I'd love to see it

Until then, for all but final compiles:

fast vis = ok! (imo)

Although this is HL in HL2 I noticed this cave I made...On fast it was darker at the edges but on normal it was lighter...Very annoying when I tweaked it for ages on fast and then final on normal to see it changed.

Final Compiles - Full Vis only.

You don't notice it straight away - but you feel it in game.

Always do -full vis for "final" maps. And Even for testing - because sometimes Full vis finds errors that Fast and Normal skip over

...because sometimes Full vis finds errors that Fast and Normal skip over

It's exactly the reverse.

Full VIS "fixes" errors that subsequently aren't shown in the compile log--though it never eliminates the problem. Fast VIS will let errors come through, paticualarly "Leaf Saw" errors that would never show after a Full VIS compile.

Personally, I'd rather know about the errors and eliminate it them