vbsp weird behavior/crashing
And finally, in case this matters (I doubt it does), here are my computer specs:
Intel i7-3770k OC'd up to 4.0 GHz
MSI Radeon 6850 PE/OC
8 GB Corsair Vengeance RAM
Asus Sabertooth Z77 motherboard
2x 500 GB Western Digital Caviar Blue HDD (RAID)
I can post the VMF if necessary, or any other pertinent information that I forgot. Thanks in advance to anyone who helps.
EDIT: Crap, posted in the wrong forum. Could someone please move this post?
So if you manage to compile the map properly at least once, vbsp will generate the .bsp file from the .vmf file, vvis will read the .bsp file and calculate visibility, and finally vrad will read the bsp and calculate static lighting.
If, subsequently, you try to compile and vbsp fails to run, vvis and vrad will both read the .bsp file that was written from your previous (successful) compile.
So the "Too many light styles on a face" warning you're experiencing means that you had too many named lights in the map affecting a single face when you last successfully ran vbsp*. It doesn't matter if you remove all the lights in the .vmf because vrad* is still working from an old .bsp file.
You need to find out what is making vrad crash, and fix it.
- Checked permissions: make sure your account has proper permissions in that folder- Verified tool cache file - turns out vbsp.exe was corrupt- Noticed that there was still "too many light styles" errors- Turns out, Valve's dropper instances include 4 named lights, which will cause these errors. I have attached my updated instances without lights.- vrad.exe kept crashing- Found this: https://developer.valvesoftware.com/wik ... _Crash_Fix
Everything's back working now. Thanks to Nacimota, ChickenMobile, and King_Ghidorah for all the help, all of you rock.
EDIT: Broke again. Turns out I had too many brush faces and I had to trim out the last part. Thanks again to the IRC folks for helping me again.