plane with no normal - wtf? Created 14 years ago2010-02-26 03:29:40 UTC by Tetsu0

Plane with no normal - Tommy14 says

This error is always caused by vertex manipulation. A plane is defined by 3 unique coordinates. If any of the three coordinates are the same, then you don't really have a plane (its either a line or a point). There is no way to fix this error other than to delete the brush and recreate it completely.

Well ok so i did that to one brush, brush 156; entity 0, side 9.

exported to .map, compiled.. same error. same brush, same side.
Went back to hammer searched for the brush, and a different brush popped up. So i said.. wtf.. deleted, re-created, and recompiled.

same thing. same brush number, side, entity.. everything.
did that again like 6 times. and the thing is all the brushes that the log file is reporting have been made with the brush tool. I havent touched any of them with the VM tool, or even the clip tool.

Alt+P isn't reporting anything either.

This is bugging the CRAP outta me. Any suggestions?

The .rmf-file may be corrupt, have you tried saving it to a new .rmf-file?

Have you used the VM-tool anywhere in your map, if so, those brushes would be your prime suspects. Could be that a damaged brush have caused a chain of reactions causing the compile tools to intercept a legal brush as a damaged one.

If you're using a beta of the Compilator (with HLFIX), csg actually reports a different brush number. This is caused by hlfix. To get the correct brush number, either temporary compile with Hammer (vis and rad off) or take a closer look at the hlfix compile process (note that there's no log of hlfix). Just start the compilation proces and when hlfix is finished and csg start, pause the compilation process so you can examine the hlfix bit.

No i found it.
I traced the error to a clipped-to-hell 'boulder' that i was using for some rubble. Alt+p reported no errors and the brush itself was a func_illusionary. It didnt look suspect til i remembered when i loaded the map, a clone of that brush couldnt load due to errors in the file.. stupid stupid stupid..
once i deleted that, everything was peachy.

The brush 156 error could've spawned from everything in that area being assigned to a visgroup?

I have no idea, all i know is that it's working and my mod can progress.

And Atom, i was not using the beta, just the good-ol compilator, so HLFIX was not included in the compile.

But the compilator does crash for me like every time i run my first map with the compilator still open. It's only after i disconnect from the map and minimize half life, i get the .net error. after that though it's completely fine and stable running in the background.

Ill look into that.

i never ever had the crash problem with compilator fyi..

it happens the first time i run a map and then minimize after a map.
After a reboot only.