calc_triangle_representation: cannot convert

Well, I was working on the map, and I got around to compiling and I got this (error?) that I had never seen before: "calc_triangle_representation: cannot convert"

Here is my compile log... this is just for running vbsp only, though it WILL continue and run vvis and vrad afterwards. The problem is, no map is actually created!

** Executing...
** Command: "c:\program files\steam\steamapps\james_bond_007_jw@hotmail.com\sourcesdk\bin\vbsp.exe"
** Parameters: -game "c:\program files\steam\steamapps\james_bond_007_jw@hotmail.com\counter-strike source\cstrike" "C:\Program Files\Steam\SteamApps\james_bond_007_jw@hotmail.com\sourcesdk_content\cstrike\mapsrc\militia3z26"

Valve Software - vbsp.exe (Jan 19 2005)
1 threads
materialPath: c:\program files\steam\steamapps\james_bond_007_jw@hotmail.com\counter-strike source\cstrike\materials
Loading C:\Program Files\Steam\SteamApps\james_bond_007_jw@hotmail.com\sourcesdk_content\cstrike\mapsrc\militia3z26.vmf
fixing up env_cubemap materials on brush sides...
Material glass/glasswindowbreak070b is depending on itself through materialvar $crackmaterial! Ignoring...
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (3)
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (2)
Processing areas...done (0)
Building Faces...done (0)
Chop Details...done (0)
Find Visible Detail Sides...
Merged 792 detail faces...done (0)
Merging details...done (1)
FixTjuncs...
PruneNodes...
WriteBSP...
NODRAW on terrain surface!
done (3)
writing C:\Program Files\Steam\SteamApps\james_bond_007_jw@hotmail.com\sourcesdk_content\cstrike\mapsrc\militia3z26.prt...done (1)
WARNING: node without a volume
WARNING: node without a volume
Creating default cubemaps for env_cubemap using skybox canyon...
Run buildcubemaps in the engine to get the correct cube maps.
Finding displacement neighbors...
Found a displacement edge abutting multiple other edges.
Finding lightmap sample positions...
Displacement Alpha : 0...1....1...2...3...4...5...6...7...8...9...10
Building Physics collision data...
done (3) (1669867 bytes)
Emitting linux collision data (use -nolinuxdata to disable).
Building Physics collision data...
done (3) (2678225 bytes)
Placing detail props : 0...1...2...3...4...5...6...7...8...9...10
Writing C:\Program Files\Steam\SteamApps\james_bond_007_jw@hotmail.com\sourcesdk_content\cstrike\mapsrc\militia3z26.bsp
48 seconds elapsed
-0.038100 -0.484686 0.000000
0.088900 1.636042 0.000000
0.088900 -0.484686 0.000000
-0.088900 -0.484686 0.000000
make_triangles:calc_triangle_representation: Cannot convert
-0.038100 -0.484686 0.000000
0.088900 1.636042 0.000000
0.088900 -0.484686 0.000000
-0.088900 -0.484686 0.000000
make_triangles:calc_triangle_representation: Cannot convert
Memory leak: mempool blocks left in memory: 48
Memory leak: mempool blocks left in memory: 5

** Executing...
** Command: Copy File
** Parameters: "C:\Program Files\Steam\SteamApps\james_bond_007_jw

sorry it got cut off a bit there at the end. Anyways, I assume that I have an invalid brush of some sort somewhere, but is that the case and if so, do those numbers tell me anything?? I even tried selecting (most) all of the new things i had changed since my last working compile and hiding them, but it didn't have any effect - the error was still there - which i found quite odd. Thanks for any help!

Maybe there's some problems with any of your displacement surfaces, since they're built up by small triangles.

The "make_triangles:calc_triangle_representation" error isn't a fatal one which stops the compile. It's more likely that the "NODRAW on terrain surface!" and "WARNING: node without a volume" errors need fixing for your level to compile. The 'map'->'check for problems' menu command should find the problem brushes for you.

I think raptor is on the right track. If you try and make a plane
with three sides into a displacment it may give you that error. I
seem to remeber getting that at one point but I dont remeber how or if
I fixed it.

check for problems, and look at your displacement maps

well the warnings have been thre a long time (haven't gotten around to fixing them) and the map has always worked fine with them.... i actually fixed the problem, though. What I finally did is just start deleting parts of the map and then compiling over and over til it stopped. The problem was apparently with a func_breakable... the odd thing is that i have many copies of the exact same breakable that work just fine. i replaced it and its good as new

I had this problem on my map. It turned out to be a "prop_static" which
had a wrong world model or something. i changed it to another fence and
now it works... as i see it, it can be any kind of entity?

there is no way to fix it but deleting 1 objekt at a time, compile
untill you find the problem. (make a backup of the original which you
can go back to and then just delete that objekt so you dont miss to
replace something else you deleted)