In the first compile, vvis ran in 3 minutes, 57 seconds which is quite long (although not catastrophically long), as vvis shouldn't take more than a couple of seconds even on the most complex of maps.

This brings the issue of optimization: vvis will suffer when the map isn't optimized. Have you correctly used hint brushes, areaportals, nodraw, func_detail, no microbrushes, no weird-shaped brushes, snapping to grid in hammer..?

Then in later logs, vvis disappeared leaving vrad to run with "No vis information, direct lighting only".

This means that vrad will not have light bounces, only direct lighting which could explain the bad lighting/shadows in your map.

you might have turned off vvis by mistake or you may have a leak! Have you tried to search for errors in Hammer (Alt+P)?

the log also shows:

"material not found!" meaning that you have referenced a texture that doesn't exist.

"found a displacement edge abutting multiple other edges" meaning that a displacement is touching more than one other displacements at the same point along one of its edges. Although not an alarming error, it could be the cause of lighting anomalies. You have to go through your displacements one by one to find the error.

"error loading studio model ""!" meaning that you have a model-based entity (prop) without a model specified.

Focus on finding why vvis is not running to help fix your issue

Will2k

• Helpful x 1
• Thanks x 1