[article] Compiling Errors

This is a discussion topic for the article "Compiling Errors" by Leperous which can be found here

Article description:

A list and their solutions

Damn great tut, can't find much better tuts.

respect for best error tut to date where respect is due 5

why did it take so long for one person to learn what the different error messages meant, thank god someone finally got this up...thnx lep.

The FindPortalSide error can occur if you have an entity's origin outside the map.

Another error you may want to have is the Warning: MICROBRUSH x error. This occurs when you have a brush smaller than 1 unit in any axis, and often occurs when making your skybox, since you're shrinking all your brushes down.

"Brush XXX: WARNING, microbrush"

Does the find brush tool not work for this? View --> Go To Brush Number or ctrl+shift+G. Always worked for me in older versions of the editor, too, but if it's borked now, nevermind.

Hah, good call with the Memory Leak item ;-) that's always annoyed me when people post that...

I've got a Vis warning of sorts, "WARNING: Cluster portals saw into cluster".
Is that an error? My map sure doesn't show any problems.

I believe "WARNING: Cluster portals saw into cluster" means that you have overlapping brushes.

Edit: I just tested this theory and it is incorrect. I'm not sure what causes that message.

WARNING: Cluster portals saw into cluster basically means that VIS is freaking out over your leaves. Turning some angled geometry in my map into func_brushes made the message go away. Run GLview and if you see a lot of white lines really close together or at a bunch of angles, you've found your problem.

Cool tut but not complete yet

(vbsp)

• Can't find surfaceprop iron for material MODELS/PROPS_DEBRIS/REBAR_MEDTHIN03, using default
• Brush xxx : areaportal brush doesn't touch two areas

A great list of quick answers to error messages!
Thankyou Leperous, RabidMonkey777 and KungFuSquirrel for solving my Microbrush problem. The find brush tool just threw me out into the void, but ctrl-shift-G worked wonders (I overlooked it in the menus).
Mine were caused by some careless use of the brush clipping tool, leaving me with tiny pyramid points that I couldn't see.

Good start to this much needed list, one i would like explained is 'degenerate faces' in the vrad process, Ive had this one and it might be the cause of a realy bad crash on my map that happens randomly, sometimes right at round start, sometimes after a few rounds have been played...

Face List Count >= OVERLAY_BSP_FACE_COUNT

The limit for this is actually 64 faces, but what it refers to is faces after the BSP splitting is done, so your overlay could be spanning more faces than you think.

More errors from VBSP:
HashVec: point outside valid range
a vertex is outside the valid map extents, which usually indicates a malformed brush.

Error: material *** doesn't have a $bottommaterial
You've tried to use a water texture which should only be placed in the map automatically by the compiler. Invalid materials usually end in _beneath or _bottom. There will be a matching texture without those suffixes which you can use instead.

Error: MAP_MAX_***
(where *** is PLANES, FACES, BRUSHES, BRUSHSIDES, TEXINFOS etc.)
You've exceeded the maximum number of these items allowed in a map.

Error! Too many detail props emitted on this map!
You've uses a displacement surface with a texture that automatically generates prop_details (grass tufts, etc.) over too large an area. Use a different texture or reduce the size of the displacement.

Damm

New error:

1. 1. 0.000000
2. 1. 0.000000
3. 1. 0.000000
4. 1. 0.000000

make_triangles:calc_triangle_representation: Cannot convert

btw: more error's can be found here: http://www.interlopers.net/errors/errors.php#1-15

"make_triangles:calc_triangle_representation: Cannot convert"

That's an odd one. I've tried to track this error down before, and it doesn't actually appear in the source code of the compile tools. Instead, it seems to be coming from the VPHYSICS.DLL library which is loaded by VBSP.

At best guess, it seems to be related to an error building the collision geometry of a model. The coordinates it gives are no use, since they're not map coordinates.

So if you get this, check for props that you've added recently. Particularly, check for props that you've given a Solid Type: Vphysics setting. They may be causing the error.

Another one I've seen recently:
Bad detail brush side
(happens in VBSP).

This one seems to happen when you've got certain kinds of mixed face contents on a detail brush. For instance, if you have a clip texture on one face of a func_detail, and the skybox texture on the other sides.

I can't seem to recreate that 'bad detail brush side' error, perhaps it's now out of date?

I can't replicate it now, either. It may have been something else that was the problem. I'll try to replicate the situation I got it in.

Allready solved my problem, what it was I don't know just was replacing some walls and stuff and suddenly it was dissapeared

Does anyone know why I can't properly compile cs_office? I extracted the .bsp from the .gcf file with GFCscape, and then I decompiled the .bsp with VMEX into a .vmf file. Now when I try to compile the .vmf (without any edits to the map), it fails when trying to write the .bsp. So does anyone know what's going on? Obviously the map works for it wouldn't be playable. I'll post the error log below.

materialPath: c:\program files\valve\steam\steamapps\solo3021\counter-strike source\cstrike\materials
Loading E:\cs\cs_office_d.vmf
Brush 2529: bounds out of range
Brush 2529: bounds out of range
Brush 2530: bounds out of range
Brush 2530: bounds out of range
Brush 2531: bounds out of range
Brush 2531: bounds out of range
Brush 2532: bounds out of range
Brush 2532: bounds out of range
Brush 2533: bounds out of range
Brush 2533: bounds out of range
Brush 2534: bounds out of range
Brush 2534: bounds out of range
Brush 2535: bounds out of range
Brush 2535: bounds out of range
Brush 2536: bounds out of range
Brush 2536: bounds out of range
Brush 2537: bounds out of range
Brush 2537: bounds out of range
fixing up env_cubemap materials on brush sides...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
0 . . . 1 . . . 2 . . . 3 . . . 4 . . . 5 . . . 6 . . . 7 . . . 8 . . . 9 . . . 10 0 . . . 1 . . . 2 . . . 3 . . . 4 . . . 5 . . . 6 . . . 7 . . . 8 . . . 9 . . . 10 Processing areas... done (0)
Building Faces... done (0)
Chop Details... done (0)
Find Visible Detail Sides...
Merged 180 detail faces... done (0)
Merging details... done (1)
FixTjuncs...
PruneNodes...
WriteBSP...
HashVec: point outside valid range

1 threads
reading e:\cs\cs_office_d.bsp
Error opening e:\cs\cs_office_d.bsp

[Reading texlights from 'lights.rad']
[1 texlights parsed from 'lights.rad']

Loading e:\cs\cs_office_d.bsp
Error opening e:\cs\cs_office_d.bsp

Note: Once again, the extracted map has not been editted whatsoever.

You didnt have "plain with no normal."

Well written and pretty clear (some of the errors could do with some more explaining) but pretty good overall.

Thank you VERY much! You saved my map! I had the "Face List Count >= OVERLAY_BSP_FACE_COUNT" error. And you fixed my problem!

Ok, I got some weirdass error, and I can't figure out what the hell is the problem!

12/ - func_breakable: UTIL_SetModel: not precached: models/props_junk/wood_crate001a_damagedmax.mdl

This will come in handy