Topic: .mod plugins

[candle_86]

I got 3dsmax9 as yall know and want to start using it for more than just renders, is there a .mod plugin for it?

[atheorhaven]

I got 3dsmax9 as yall know and want to start using it for more than just renders, is there a .mod plugin for it?

I believe that the .MOD plugins only work up to Max 6, 5 for sure.  I think Rod O'N was talking to the same buddy who supplied us with the gmax plugins about porting to Max 9, or it was marstone.. one or the other if I remember correctly. 

But for now, nothing yet for Max 9, other than export to .3ds and import into gmax for final output to .MOD..

[candle_86]

problem with taht though, i have to export to .nif if i do it to .3ds gmax cant import it crash's i think the .3ds changed since gmax. And if i do .nif i have to remap it

[Rod ONeal]

I've never had a problem with any .3ds file importing into gmax? Could you post a .3ds file that causes gmax to crash on you so I can try it?

[candle_86]

yea ill have to make one lol, it only seems to happen with ones made in 3ds if i import a .nif in 3ds then export to .3ds it doesnt happen, and only after i mapped it

[Rod ONeal]

OK. I'd like to check it out when you get a chance. Thanks

[GotAFarmYet?]

Athor was close the plugins for max stopped at 5.
exporting to a 3ds file for max 9 and being able to open it in GMax should have worked though.
Rod is the best person to get this error worked out though as he is the one who got use the plugin for GMAx

[markyd]

and if your making models for sfc III I have found when exporting anything above 3.1 can have and issue on the overall effect of your meshes if they are unified.

But it does depend on the complication of the mesh..

in 3.1 your mesh can be as complicated as it likes, but it will retain all smoothing groups etc, outside of this say using max 5 then exporting to .mod, even if your smoothing groups are sorted can sometimes resort to an ugly effect, thats what happend to my gagarin i worked out last month.

[FoaS_XC]

and if your making models for sfc III I have found when exporting anything above 3.1 can have and issue on the overall effect of your meshes if they are unified.

But it does depend on the complication of the mesh..

in 3.1 your mesh can be as complicated as it likes, but it will retain all smoothing groups etc, outside of this say using max 5 then exporting to .mod, even if your smoothing groups are sorted can sometimes resort to an ugly effect, thats what happend to my gagarin i worked out last month.

There is a fix to that. I wrote this script for Max9. It requires that the object be an editable poly. Select each object and run the following script.

Code: [Select]


alledges = #{1..(polyop.getNumEdges $.baseobject)} -- all edges bitarray
alledges -= polyop.getOpenEdges $.baseobject --exclude open edges
splitedges = #{}
for i in alledges do
(
edgefaces = polyop.getFacesUsingEdge $.baseobject i as array --the faces of the edge
smoothgroup1 = polyop.getFaceSmoothgroup $.baseobject edgefaces[1]
smoothgroup2 = polyop.getFaceSmoothgroup $.baseobject edgefaces[2]
if smoothgroup1 != smoothgroup2 or smoothgroup1 == 0 or smoothgroup2 == 0 do splitedges[i] = true
-- if the smoothing groups are different or nonexsisting add edge to splitedges bitarray
)
polyop.setEdgeSelection $.baseobject splitedges
$.EditablePoly.splitEdges ()

One of these days I'll remake it to be able to handle multiple objects, but for now just run it on each object. Basically what this does is it detects whether an edge is hard or smoothed. It an edge is hard it will split it.

[markyd]

and if your making models for sfc III I have found when exporting anything above 3.1 can have and issue on the overall effect of your meshes if they are unified.

But it does depend on the complication of the mesh..

in 3.1 your mesh can be as complicated as it likes, but it will retain all smoothing groups etc, outside of this say using max 5 then exporting to .mod, even if your smoothing groups are sorted can sometimes resort to an ugly effect, thats what happend to my gagarin i worked out last month.

There is a fix to that. I wrote this script for Max9. It requires that the object be an editable poly. Select each object and run the following script.

Code: [Select]


alledges = #{1..(polyop.getNumEdges $.baseobject)} -- all edges bitarray
alledges -= polyop.getOpenEdges $.baseobject --exclude open edges
splitedges = #{}
for i in alledges do
(
edgefaces = polyop.getFacesUsingEdge $.baseobject i as array --the faces of the edge
smoothgroup1 = polyop.getFaceSmoothgroup $.baseobject edgefaces[1]
smoothgroup2 = polyop.getFaceSmoothgroup $.baseobject edgefaces[2]
if smoothgroup1 != smoothgroup2 or smoothgroup1 == 0 or smoothgroup2 == 0 do splitedges[i] = true
-- if the smoothing groups are different or nonexsisting add edge to splitedges bitarray
)
polyop.setEdgeSelection $.baseobject splitedges
$.EditablePoly.splitEdges ()

One of these days I'll remake it to be able to handle multiple objects, but for now just run it on each object. Basically what this does is it detects whether an edge is hard or smoothed. It an edge is hard it will split it.

Nicely done mate, ur an intelligent guy... but i think i will just use 3.1 for exporting . mods from now on...   but for the newbiees this is invaluable..

[Tus-XC]

or just detach each smoothing group to the mesh... very annoying

[FoaS_XC]

Tus, this script has the same effect, except that it automates it.

[Tus-XC]

Tus, this script has the same effect, except that it automates it.

really.... hmmm..... well now...

[FoaS_XC]

Check out that video tutorial I did for break models
http://www.youtube.com/Robinomicon

It's shows how it works in Part 2 of the break model sets