Ok guys been nearly a decade since I have done any HEK work. Decided to switch back over to CE hoping to make a good Infinity Remake since H2v was giving me issues.

So I created an updated forerunner base based on CEA design. Exported all apropriate files (jms) into the Models and Physics folders. Both versions of tool compile the gbx_model and physics model just fine. Collision however is where I get stumped. Both tool's report the same dang 4 open edges. Funny thing is, no edges are open at all! I even tracked down the edges manually and everything is aces.

Does anyone know wtf is going on? In case it matters, the model has about 7.5k verts and 14,020 faces.

Export as editable mesh, if that doesn't work, try using max 8 and blitzkrieg

Yeah should have mentioned that I'm using Max 7 and the jms exporter both 1.1 and 2. Im aquiring Max 5 now and will attempt using Max 8 as suggested. Thanks for the starting help. I'll update you on how it goes.

***Update. So I looked around and found that Max 6 version of the exporter. Got it working for Max 7 and attempted to export the model and run collision. here is the screencap of it.



Any other ideas? Not sure how moving to Max 8 or down to 5 will help.
Edited by Twinreaper on Jan 3, 2016 at 01:34 AM

File, Import, WRL, navigate to your HCE directory. Since its a collision model you're compiling, look for debug.wrl. Make sure you uncheck all the options it gives you after selecting the file (otherwise, it will purge your scene). It will create color coded objects for the errors (Open edge is red, like tool says in your message; it will create red geometry)

Side note: I recommend updating to Max 2014 or above simply because of the wealth of new tools included in newer packages.

I.ve imported the error file a dozen times and quadruple checked the red and gree edges it defines, and they are certaintly not open. Even Max confirms it by reporting no open edges in STL.

What new tool packages are we talking about? I do have the newest version of Max,2015 right?

2016 is newer but 2015 is just fine. I was under the impression you only had MAXR8.


BTW if you need any more help send me the max file and I'll take a look at it. I'm trustworthy ask anyone in this forum.

stl check is useless. border selection tool is the thing to use, if you have any borders then you must have open edges.
select all verts and weld at 0.01
Edited by Maniac1000 on Jan 3, 2016 at 02:19 PM

Can confirm

Wielding verts at 0.1 is the first thing I do when importing any kind of secondary, non by hand created asset. No verts left to wield, so yeah.

I just went ahead and deleted all sections of geometry that tool threw a fit about and it all compiles now. Sad part is Sapien cant seem to teleport the camera into the bsp. For all the complaints people gave H2v.....at least I never had an issue with being able to spawn into the map, and the radjosity process was much much quicker.

This problem is usually caused by your bsp not being completely zeroed out in the 3d world space: (applies to all 3d packages)

1. Select your bsp mesh.

2. Over on the right hand side of maxes UI hit the hierachy tab. (The icon with the large and three little monitors)

3. Select affect pivot point only and then directly below under the alignment sub section hit center to object.

4. Now zero out all of the X,Y,Z values by right clicking each of the co-ordinate spinners located directly at the bottom center portion of your screen.

5. Assuming you completed the above directions correctly go ahead and recompile and test out the result.

That didn't solve my problem. I think I know what is causing the issue. It would seem that when tool compiles geometry and collision, it attempt to reduce it, similar to how H2Tool wields vertices and faces to reduce and minimize issues with verts and faces that are within 0.35 of eachother.

I have a lot of geometry that makes up trim, that sticks out. I'm willing to bet that if i removed these trims and made flat faces, the errors would clear up.