vvis.exe either taking an immensely long time or just crashes

It’s as simple as that.

I was compiling a map, vvis and vrad working fine. vrad usually takes the most time for me, if this is not normal then I must have a weird PC.

But yeah, any reason as to why vvis.exe is taking an infinitely long time to do something? At some point it stops using up any memory (only 86mb usually) and any cpu power, as if it’s completely idle. I witnessed it sit idle for -3 hours- for a simple thing once.

Is vvis just broken or is there something I should take into account while mapping?

Use VBCT.

Download Source SDK 2013 Singleplayer.

Then use this (this is VBCT preconfigured to mount garrysmod and compile off of the source sdk 2013 singleplayer bin files):
https://www.dropbox.com/s/2i84g1kc2cw29bk/Valve%20Batch%20Compiler%20Tool.zip?dl=0

What it is: https://developer.valvesoftware.com/wiki/Batch_Compile_Tool

All mappers should be using this, but you have to manually configure your paths, as seen in the SDKPaths.pro. You could change it to HL2 paths instead of garrysmod and source sdk 2013, but I use Source SDK 2013 to map directly off garrysmod. There’s a tutorial right here: http://forum.facepunch.com/showthread.php?t=1374587

EDIT: For the record, VBCT is god, and once you use it, you never go back. Pro Tip: Advanced Options > Advanced Compile Options shows dozens of options and variables you can configure with VVIS, VRAD, etc, (it’s pretty much checkboxes) and it’ll automatically add the options onto the compile programs. It also doesn’t freeze up your computer to the point of super-lag. I can even play a game while compiling with VBCT, and still not have any stuttering.

VBCT is good, but I’m guessing it probably won’t fix their problem.

If vis is taking more than a few secs - even on larger, more complex maps - or just crashes, you probably have a horribly optimized map and need to get that under control. I’d recommend looking into that.

Yyeeeaaah…probably. I think I know the reason lmao. Will probably fix it in the final versions.

You should fix it ASAP, not “in final versions,” otherwise you could end up with even more problems to fix, some incredibly difficult to find.