3d max Pro optimizer sub-object selection?
polycounter
Does it work in 3d max at all?
For years already I use Blender decimate modifier for distant LODs. It can work for certain set of vertexes only, keeps UV and even normas mostly until its almost nothing left at least. So you just put a few of them for different parts of your model. Works like a charm in a word.
Today I tried to do it back in MAX. Years ago I used multires but it always been a crap. Now I try pro optimizer but sub-objct selection either doesn't work at all or it completely ignores whatever you selected.
What's the trick there?
Replies
Select your sub object, detatch it, run Pro opt, reattach
Isn't it breaking custom normals in 3dmax and makes hard edges I would have to fix after? I mean I want to do it on selected vertexes, not just separate meshes ? Max help says it should work on just selection . I wonder maybe I missed something?
Pro Opt only works on the entire object, and doesn't respect sub-object selctions like most other modifiers would. After splitting and running it, it should preserve smoothing groups/hard edge placement, yeah - but if you mean custom tangent work you've done that you want to keep, it may not preserve that.
Thanks for reply, Kanni3d. My guess it's one of 3d max features that exists only on Help pages , not in reality. Not the first one, really 😁 . Wonder what people use for lods nowadays?
Depends what the LODs are for, but yeah I imagine they're mostly done in engine with tools like simplygon :) Otherwise, manual LODs for sensitive circumstances are usually just done in the same dcc
the regular optimize modifier works with subobject selection if thats any help. probably not though because RIP UV if you use the regular optimize modifier
As what I remember Optimize is an ancient anachronism from around 3dmax 2,5 . Messing UV and normals completely contrary to Blender . Not sure why it's still there.
Old modifiers are kept around just for backwards compatibility. Lots of longtime Autodesk customers have long archives of models, to support clients who need updates (think large architecture firms supporting huge multinationals) so they can pull up old Max files to update something or other.
To open a Max file, you need to evaluate each modifier in turn. So, they all have to be there.
Personally, I think these firms should just keep a specific machine as an archival tool, frozen to a specific OS and Max version. So they can manipulate old files, and so newer versions could drop backwards compat bloat. But that also presents its own problems ...
Can't you mask areas out in proOptimiser? I'm sure I remember that working
Yeah you can preserve a selection of vertices, or the inverse.
yeah, it's what help says but I couldn't make it work .
Add a Poly Select below ProOptimizer, Vertex mode, and select some verts. Then up in ProOptimizer, turn on the SubObject option, and recalculate.
Thanks a lot Eric. it works that way. Not a word about it in help documentation.
Great! I didn't even look at the help though, I just experimented with it a bit.