Export the jms once again. I think 3DS Max didn't save correctly.

i think you have a problem linking to the frame in 3dsmax, check that

That would be the "no geometry to export" error while exporting, not the "end of file" error while compiling the tag.

You can't just link a primitive to frame and import that into halo.

It has to be an editable mesh with Multi/Sub-Object material applied to it. Also make sure the material IDs are set to numbers in the multisubobj thing
Edited by OrangeJuice on Jul 27, 2015 at 04:15 PM

Check your mesh again. This error is usually caused when you have faces that have material IDs that don't exist in your multi/sub-object material group.

E.g., You have two materials in your material editor, IDs 1 and 2, but your mesh has faces with a material ID of 3. You need to change those faces to one of your existing material IDs.

Post of the year.

In my experience, the best way is to select each ID number in the Edit Polygon properties box and hide each ID until you have hidden every normal existing ID, then you will only be left with the odd materials.

For example, you select all triangles with an ID of 1, then hide all those. Repeat until you have hidden all the IDs that should exist.

Select the edges modifider, at the botom theres an option called Select Open Edges that indicates the problem

Use File -> import (mapname.wrl file in Halo root folder).

Uncheck all three boxes

Delete all objects with the names starting with VILS and VSEP (I believe those are right, running off my memory)

There should be a few objects starting with VIFS01, VIFS02, ect. Those are the edges that have issues. Since it's two degenerate triangles with that many errors, you probably should use the Border tool to select any open holes (make sure to mark render only materials with a exclamation mark (!) and any two sided materials with a % for collision (these still can't intersect other faces, but Render-only can.)

As for fixing the degenerates, try converting your object to editable patch and back to editable poly, it should have all edges defined and visible and you can see any vertices that aren't connected together as they should be.

This, coupled with the VIFS objects will tell you where exactly the error is (I usually move the unconnected vertex a bit tangent away from the offending edge and delete the polygon in between them, then in Edge mode I use Create a Vertex to placea new one where the vertex would be attatched to the offending edge and then target weld them accordingly.


Hope this helps.

Sorry, i didnt explain very well. Im using gmax so its a little bit diferent, shouldnt delete them, first search for a tool called wield. this thing combines vertexs so there is no open edges (its like a hole in a ballon, the ballon must be sealed) or other way can be creating faces in the areas with open edges (something like patching them)

Well this pic is more usefull

Deleting the open edges will only make your problem worse... And I never said to delete the VIFS objects , only the VSEP and VILS objects. As for the picture that was posted above, you have the Degenerate triangles problem, where the vertex is probably collinear with an edge. Maybe if you posted a viewport screenshot I could see what the issue is.

You don't delete open edges, you fill them in. The easy way to do this is to convert to editable poly, select the border tool, then hit select all. This'll highlight all the open edges and you can now proceed to fill them in with either the create or cap tool. Be sure to convert back to editable mesh when you go to export, however. Keeping it as poly will cause your JMS to read incorrectly for some odd reason.

If you connect all your vertices in edit poly mode your model will export fine, the difference between tools tolerance from edit mesh or edit poly as something to do with the interpretation of triangles and associated verts.

If I remember correctly, it has to do with the exporter you use.
Blitzkreig will work just fine with edit poly.

Oh yes, i hate it when tool says there are open edges when there really aren't. bluestreak exporter causes these issues when you export anything that is Editable Poly. Just convert it to Editable Mesh (i still get some errors in-game, missing faces and such).

I use junglegym way faster.

Blender is terribad, plsno.

http://forum.halomaps.org/index.cfm%3Fpage=topic&topicID=47033]Plsyes