Bluestreak is terrible. Get max 8 and use blitzkrieg.
It will make your life infinitely easier.

Bluestreak tends to make up errors out of thin air, and modelling collision geometry for halo is hard enough as it is.
Edited by UnevenElefant5 on Apr 12, 2011 at 12:46 AM

Bluestreak requires that your meshes all be in editable mesh, rather then editable poly, and all use multi-sub objects. Otherwise it exports files fine. The only issue with it is that it takes about 10X longer.

Now, if max 8 worked on vista and up reliably that'd be great, but it'd be better if someone tried to port blitz to the newer max versions.

Maybe it's time someone updates bluestreak so it's not so long to work?

Max 8 works fine on my win7 64bit.
Also if you guys are modeling in anything newer than max8, you can use the collada plugin to get the model and textures back to max8.

I just tried to export my level like that yesterday with Bluestreak. It told me I had 7 open edges in the middle of the sky, where there was absolutely no geometry.

idk

It hasn't given me any issues aside from the ones I mentioned. Either way though, blitz for newer versions would be best.

Did you make sure you had turned the map into triangles? Most of my errors with Blustreak occurred because I hadn't made the mesh into triangles before exporting.

Dont think that would be the issue. Halo converts the geometry as soon as it's compiled through tool anyway. It could be just your reading on the .wrl file. You could think that it's showing open edges whereas infact they are representing the near co-planar edges, or whatever they're called. :/

Well all it gives me is 7 open edge errors when I compile it. There's no other error that it could be, and even if there was, it's in the middle of the sky, there's no geometry there anyway.

Also Yak, everything was triangulated.

Anyway, I didn't mean to take over the thread with my bluestreak error, it was just supposed to be an example. I know Bluestreak works perfectly for some people, but just in my experience, it's been nothing but trouble.

Let a tool triangulate your geometry can always cause issues. I've ran into issue with UDK also because things weren't triangulated. While the tools are made to do it they can't do it nearly a efficiently as you or 3DS Max.

Bluestreak doesn't just "make the errors up" - post the model in question.

Might be the rotation, but I have gotten "errors" where there was nothing wrong before with Blustreak. My fix has been triangulating pre-export.