UV Mapping and MeshSmooth Modifier

#47

Thanks for your efforts, sounds exactly like I did.

Sounds like there is no other solution then splitting the mesh and relaxing the remaing distortions in the unwrap.

#48

Well, I don’t know if this is the only solution - I’ve heard you can also substitute the Turbosmooth for MeshSmooth and check “Old Mapping Method” or something like that on MS. If there are ANY other ways I’m gladly (and, hopefully, we will be) listening!

#49

I started to script the whole process and it works quite well most of the time, but with some objects it’s simply impossible to transfer the channel info data as the number of faces changes when using TS.
No idea why, working on it.

#50

Cool!! Does your script wprk with complex shapes?

#51

It’s quite easy to automate the splitting process, but think I need a few days more to work on it.

#52

Man… I feel I should study Maxscript a little more… The explanation Bobo gives in Max help are most complete. I wonder how the these people’s brain works - they must have a LOT of clockwork in there… :smiley:

#53

Not really.

It works in this case, but completely fails in others.
It’s still not able to remove stretchings, only distortions.

#54

Once again thanks scrimski and davius for providing the solution. I’m been trying to solve this problem for sometime now… by the way is this a software problem that Max have?

#55

Ok, here’s my script attempt. I’m not 100% done yet, but due to lack of time I can’t finish it atm, maybe it’s usefull for someone anyhow.

Tough still in beta stage, it does work quite well.
Quite good at removing distortion in most cases, fails in removing simple stretchings and sometimes doesn’t work at all(haven’T figured out why, sorry).
Feel free to use and to add features as you like, please report bugs, errors, suggestions to the mail adress listed in the script.

Workflow:

Select object, directly or via selection floater.
Object needs to unwrapped, otherwise the (non)existing or default UV layout is going to be used.
Attention: Keep in mind that the object is going to converted into an editMesh, everything in the stack is going to collapsed.

Options:
Keep flattened geometry: Offers the option to keep the UV layout as geometry, default is off
TS/MS Allows to choose between TurboSmooth or MeshSmooth, default is meshSmooth
Iterations: Number of Iteration to be used in Turbo- or MeshSmooth, default setting is 1 iteration
Isoline Display: Allows to switch on Isoline display for te Smooth modifer, default is off

This script is provided as is, use it at your own risk.

#56

This can be reduced a bit as follows:

  1. Create seams in your model (split edges or detach to element) in the same places where they are on your UV layout
  2. Apply MeshSmooth (TurboSmooth screws it up regardless, though to a lesser degree)
  3. Apply UV Unwrap
  4. Go back to your low-poly mesh and weld the seams

Should work :slight_smile: It did on my simple test case.

The really bad thing is that you can’t use render iterations and everytime you change the Meshsmooth settings it screws it up again. I wish Max would finally have with a GOOD SubD modifier. Or is this a problem with all 3D software? I doubt it…

#57

Hehe, can be reduced even more:

  1. Add an edit Poly modifier in you stack below the smooth
  2. select all edges, split them(yes, all of them)
  3. proceed with steps 6 and 7 like described by davius
  4. deactivate or delete the edit Poly modifier from step 1
#58

LOL! Sledge hammer approach!

#59

Hey guys,

Here’s another approach,

First make a copy of your object and remove the turbosmooth from that object, so you have an object with meshsmoothing applied to it and another without. Add an uvwmap to your smoothed object on top of your turbosmooth. Just leave it at planar. Click Acquire (located at the buttom). Select your unsmoothed model and choose relative.

I have only tried this with some dummy objects - but it seems to be working.

#60

Typically Max… always plenty of workarounds, but why doesn’t it ever work OK in the first place! :wip:

#61

But it works only with uvwmapped objects. If I have a unwrapped object then it don’t works. No?

#62

Trust me. I know what I’m doing.
I tried around a lot with this when unwrapping my (not so current anymore) WIP. Selecting+splitting all is mucho faster and easier then selecting edges by UV clusters and the effect is the same.

#63

Nice to see the conversation about this subject is still alive (and sad to realize that AD hasn’t fixed this yet…).

Bao, the method I explained (which wasn’t invented by me!) works with unwrapped objects as well. I liked the script scrimski wrote, maybe you should give it a try since it’s a faster way to solve the problem. It doesn’t work every time though (don’t know why…)

Jacobborsting method seems interesting, and can point to further research regarding the origins of the ominous mystery (hu-hummm…)!

#64

While posting on another forum, someone pointed out that this works flawlessly in lightwave.

I have the same problem in max and it’s bloody annoying!

#65

Is there a way to render out the isoline-only wireframe UV template?

#66

Tried that already?
http://forums.cgsociety.org/showpost.php?p=4962152&postcount=55