Is shutting VVIS off bad during a compile?

[SJthehero]

Hello, I wanted to come on here and ask a question thats been bugging me since I started mapping a few months ago. I didn't have any major compiling problems with my first and second maps I made, but my recent map I am updating has been a little problematic with the compiling process.

During the process, when vvis begins, it takes an insanely long amount of time for the map to actually compile (To put it into perspective, I was compiling it again today, and this time I had it on for about 8 or 10 hours, I lost count. Vvis barely made any progress, if any; FYI I am optimizing the map to the best of my knowledge. Nothing is really working. My first two maps would take less than 10 minutes to compile.).

I got so fed up with vvis one day, I actually shut the process off in task manager, BUT surprisngly enough, the map still compiled and it was playable. The only problem in the map was the skybox (Which players almost never see anyway) was pitch black, however it was still producing light.

Its really odd, and I can't find anything else about this online, and I am honestly worried if this is actually a bad thing. I did notice the only major thing that happens if you do this (Besides the skybox being total darkness) is the map cannot be packed in any bsp zipper program or whatnot, such as Pakrat.

My main question I have in all of this, is shutting vvis off during the compiler process have any negative long term effects? I appreciate any thoughts or help on this.

[TopHATTwaffle]

99 times out of 100 this is because of VVIS. If you’re like most people you opened Task Manager and saw that VVIS was running, and you stopped it. You can confirm this by opening your MAPNAME.LOG file and looking where it’s last entry way, probably on in the VVIS step. This is probably due to lackluster optimization, mainly func_detail usage in your level. I have 2 video tutorials on ways to solve this issue. Please check them out here:


http://www.tophattwaffle.com/hammer-tutorial-v2-series-6-basic-optimization/

http://www.tophattwaffle.com/hammer-tutorial-v2-series-21-optimization/

[SJthehero]

Originally posted by TopHATTwaffle:

99 times out of 100 this is because of VVIS. If you’re like most people you opened Task Manager and saw that VVIS was running, and you stopped it. You can confirm this by opening your MAPNAME.LOG file and looking where it’s last entry way, probably on in the VVIS step. This is probably due to lackluster optimization, mainly func_detail usage in your level. I have 2 video tutorials on ways to solve this issue. Please check them out here:


http://www.tophattwaffle.com/hammer-tutorial-v2-series-6-basic-optimization/

http://www.tophattwaffle.com/hammer-tutorial-v2-series-21-optimization/

Well your first video has been extremely informative. I will make sure to watch your second video on in depth optimization when I can. I have been making func_details for quite awhile, but never once did anyone mention why making a func_detail is important. Thank you very much for sharing your tutorials! They have been very helpful. This map is tricky to make with everything since the main room it takes place in is one big warehouse where everything can be easily seen.

Hopefully on my next compile, vvis will actually be normal instead of taking an ungodly amount of time. (I still can't believe it can go into an indefinite amount of time though! Thats crazy to think about.)

EDIT: Wow, the compile finally works again, and after going through and after adding in some func_visclusters and making a few surprisingly big, noticeable brushes func_details, the compile time took less than three minutes. Everything seems to be working, except for pakrat, it still won't open it up so I can pack some files up and then pak it up. But I am just glad everything is working.

Again, thank you for sending those tutorials you made and actually EXPLAINING why people should make func_details, because it bugged me for the longest time why no one would give me a proper answer on that.

[bundestrojaner]

Originally posted by SJthehero:

My main question I have in all of this, is shutting vvis off during the compiler process have any negative long term effects?

No shutting off the compiler at any stage has no negative effects, as you can simply run the compile again

[Dmitriy]

if want it to do vis fast just add this parameter:
-fast
Only do a quick first pass. Does not actually test visibility.

[TopHATTwaffle]

Originally posted by SJthehero:

Again, thank you for sending those tutorials you made and actually EXPLAINING why people should make func_details, because it bugged me for the longest time why no one would give me a proper answer on that.

Glad I was able to help. If you ever need more help, you can reach out to me on Steam, Reddit, the contact info on my site, or here on the SDK forums.

GLHF