Page 1 of 1
Tool Error
Posted: Thu May 20, 2004 2:01 pm
by scubaneo13
I remade my made and yes I did use kirks tut. I get this error in tool.
Couldn't read map file './toolbeta.map'
building intermediate geometry...
building collision geometry...
### ERROR couldn't update edge #0 (red).
### ERROR couldn't update edge #3 (red).
### ERROR failed to build collision geometry.
### ERROR failed to import collision bsp.
Does anyone know how to fix this?
Posted: Thu May 20, 2004 5:13 pm
by scubaneo13
I remade the made for about the 5th time and now I get this error in tool
building intermediate geometry...
building collision geometry...
reducing collision geometry...
building collision bsp...
### ERROR couldn't build bsp because of overlapping surfaces (orange).
### ERROR couldn't build bsp2d.
### ERROR couldn't build leaf.
### ERROR failed to import collision bsp.
Posted: Thu May 20, 2004 6:19 pm
by DM01
in your HaloCE folder, look for yourmapname.WRL, import that into your map in 3ds max 6 (dont convert unites, and dont replace current scene) then see where the lines or faces or whatever with your newly imported .wrl stuff selected and fix the stuff that you see that is wrong.
Posted: Thu May 20, 2004 6:24 pm
by gamble
its easier to just run an stl check
in the modify tab, on the pull down list (same one with edit mesh in it) there is an option called stl check. You can check any open edges/vertices or any overlapping faces. its very useful
Posted: Thu May 20, 2004 7:13 pm
by kirks4
Gamble wrote:its easier to just run an stl check
in the modify tab, on the pull down list (same one with edit mesh in it) there is an option called stl check. You can check any open edges/vertices or any overlapping faces. its very useful
STL check works fine, as long as you don't have any areas where you have detached geometry into seperate objects. STL will then give you false positives around every object that has been detached.
Use the wrl file, it will tell you exactly what tool saw wrong with the level
Posted: Fri May 21, 2004 11:22 am
by scubaneo13
I did a STL Check and there are no errors and I still get this error in tool
building intermediate geometry...
building collision geometry...
reducing collision geometry...
building collision bsp...
### ERROR couldn't build bsp because of overlapping surfaces (orange).
### ERROR couldn't build bsp2d.
### ERROR couldn't build leaf.
### ERROR failed to import collision bsp.
and Kirk what is the wrl file?
Posted: Fri May 21, 2004 11:36 am
by kirks4
scubaneo13 wrote:I did a STL Check and there are no errors and I still get this error in tool
building intermediate geometry...
building collision geometry...
reducing collision geometry...
building collision bsp...
### ERROR couldn't build bsp because of overlapping surfaces (orange).
### ERROR couldn't build bsp2d.
### ERROR couldn't build leaf.
### ERROR failed to import collision bsp.
and Kirk what is the wrl file?
Check out the new tut on the homepage...see if that helps
Posted: Fri May 21, 2004 12:16 pm
by silencer88
look in you haloCE folder for the (yourmapname).wrl file.
import that into 3ds max on top of your map file (uncheck all the import settings)
now, select the different parts of the wrl file by name and they will be in the area where your triangles intersect. (it may be a little hard to find them but you'll manage)
in order to fix this, you probably will want to move come vertices around (you should know how to do that...)
Posted: Fri May 21, 2004 3:51 pm
by scubaneo13
Silencer88 and kirks4 thanks alot for your help I finally got it to work

Again thanks
Posted: Sat Feb 12, 2005 3:37 pm
by Offsprey
i, unfortunately am using gmax. I dont have STL check as an edit mesh modifier, nor will it let me import the .wrl file,any ideas
Posted: Fri Feb 18, 2005 8:43 pm
by Waverunner
mee too
Posted: Sat Feb 19, 2005 2:15 pm
by Waverunner
ok, actually it does import the wrl file. When u import it using chimp, press H to open up all of the objects in ur map. It should say something like chimp edge error 1, 2 3 etc. When u click on it it will show u where ur problems are.
I thought it wasn't importing it before too.
Good luck!