What causes a .m3 not to import into sc2 editor properly?
i'v tried importing .m3 files that i have exported from 3dsmax 2011 and the editor It displays the name,Status:(added),and size before freezing and crashing.
The models have Mesh,Vertex Normals, and and materials. with no bones or animations.
Not sure what's causing your error but keep in mind the exporter is still very beta. Geometry should export properly though with no big problems. I'll be doing a tutorial at some point to help explain the process for exporting an M3 correctly. Right now I have other commitments and can only spend intermittent time working on the importer/exporter.
As a rough guidelink your model should:
- be an editable mesh type
- have only one material assigned to it, multimaterials work too with each submaterial representing a submesh
- for the materials, 'Starcraft 2' should be used as the shader and 'Starcraft 2 Bitmap' should be used for maps.
If you're doing something wrong the exporter should throw an error but up until now I've had very limited user feedback with problems so I haven't been able to plug all the holes. Otherwise just wait till the tutorial gets posted to help clear things up for you.
Very simple Question...
What causes a .m3 not to import into sc2 editor properly?
i'v tried importing .m3 files that i have exported from 3dsmax 2011 and the editor It displays the name,Status:(added),and size before freezing and crashing.
The models have Mesh,Vertex Normals, and and materials. with no bones or animations.
Again, i know what the problem is,
its not reading properly, so would this be the exporters fault? if so to how to fix?
ACCESS_VIOLATION (0xC0000005) occurred at 001B:010C8FF6. The memory at '0x00000000' could not be read.
--------Manual Stack Trace (ID:3700 Stack:0x05AC0000 + 12,582,912 "Main Thread")--------DBG-ADDR<010C8FF6>("SC2Editor.exe")--------DbgHelp Stack Trace (ID:3700 Stack:0x05AC0000 + 12,582,912 "Main Thread")--------Works with 2010. But Blizz have really strange way of exporting models...
have you gotten other models to import correctly? (just curious)
@XYZMuffin: Go
Not sure what's causing your error but keep in mind the exporter is still very beta. Geometry should export properly though with no big problems. I'll be doing a tutorial at some point to help explain the process for exporting an M3 correctly. Right now I have other commitments and can only spend intermittent time working on the importer/exporter.
As a rough guidelink your model should:
- be an editable mesh type
- have only one material assigned to it, multimaterials work too with each submaterial representing a submesh
- for the materials, 'Starcraft 2' should be used as the shader and 'Starcraft 2 Bitmap' should be used for maps.
If you're doing something wrong the exporter should throw an error but up until now I've had very limited user feedback with problems so I haven't been able to plug all the holes. Otherwise just wait till the tutorial gets posted to help clear things up for you.
yeh, only a few though. :/