Hello, I'm new to Modo and I'm just beginning to test some features.  One thing I'd like to be able to so is subdivide a mesh while retaining the UV mapping.  Wings 3D can do this, so perhaps I'm spoiled by that, but I was surprised to find that Modo doesn't seem to save the UVs.  Is there any trick or script or something that can enable the desired result?

Should. Just hit the D key.

I sub V4 and weld the seams and she Keeps her UV's. If anyone asks why I would do that. It makes for better sculpting.

Thanks for the response, Tashar59.  I'm very, very new, right now.  At what point in the process should I use the D key?  What I've done is select the whole mesh, then use the subdivision function.  I tried each of the three available subdivision routines, and the all bolluxed the UVs nicely, unfortunately.

I'll be getting the Modo book that's out later this month.  Unfortunately, I haven't had time to wade through the training videos.  I need a book for reference.  :D

What sort of messed up? Hittin D seems to adjust the uvs reasonably well here.

Maybe an image with what your doing and the results may help us, help you.

Thats one GREAT feature Modo has. It saves the UV Mapping when U subD the model. I found this out the hard way. I used to UV Map my Armor Cars after I cut it up and it makes it SOOO HARD to UV Map. Now i UV Map it before I cut up the model to make the hard edges, cuves, bumps, etc etc, and it keeps the UV Mapping without any issues.

As Tashas59 said, show an image of what U found and see where is the issue.

Thankx

Here's an image of what's happening, and here's how I got there:

• Import Vicky 1 geometry into Modo.
• Select Items mode.
• Select the imported mesh.
• Under Commands: Subdivide, I've tried using SDS Subdivide, Smooth, and Faceted.  All three give the same basic problem with UVs.

I'm not sure where any use of the D key should fall in the above process.  or is the entire process incorrect?  If anyone can help, please advise.

Oh, and I'm using Modo version 301-22855.

Thanks.  :D

I imported a Victoria 4 model, hit D and it turned out just fine. Couldn't reproduce your issues. Of course sculpting that high poly model was impossible to begin with (least on my machine). You probably want to look into image based sculpting. It's basically sculpting using displacement maps rather than sculpting right into the geometry. You can achieve details with this that would be impossible otherwise since you would need a far too dense mesh. Also this should get rid of your UV issue.

The modo In Focus videos have a nice intro to image based sculpting. Basically the same as sculpting geometry, just need to set up a vector displacement map first.

Okay.  Here's what I've found out.  The attached image shows the UVs after subdivision.  The image on the left was exported as .eps from Modo.  The image on the right was exported from UV Mapper after exporting the geometry from Modo as .obj.  It looks like the UVs are fine, as long as I keep the object inside Modo, but they aren't being exported properly.  Which is bad for me, because I intend to use Modo primarily with and for Poser 7.

Is there any kind of update or patch for version 301?  Or some alternate method of .obj export, perhaps using a script of some kind?  Is there something I'm supposed to do within Modo prior to export, to somehow bake the UVs into place or bake the subdivision into the geometry?  Or is the UV export handling for .obj format simply knackered and all SNAFUBAR, so Cage is just out of luck?  What can I do to get correct UV export from Modo into Poser?

http://forums.luxology.com/discussion/topic.aspx?id=23281

http://forums.luxology.com/discussion/topic.aspx?id=23517

It looks like this is a known bug.  The solution is to avoid any "empty mesh layers" in Modo, when exporting.  Apparently I have one such, but I'm not sure how to remedy that.  I've opened a blank scene in Modo, then imported the Vicky 1 geometry without doing anything else.  What is this empty layer, why is it there, and how do I rid myself of it?  It sounds like that should fix the problem.

http://forums.luxology.com/discussion/topic.aspx?id=21951&show=empty%20mesh%20item

http://forums.luxology.com/discussion/topic.aspx?id=21319&show=empty%20mesh%20item

http://forums.luxology.com/discussion/topic.aspx?id=21115&show=empty%20mesh%20item

[ http://forums.luxology.com/discussion/topic.aspx?id=18194&show=empty%20mesh%20item

](http://forums.luxology.com/discussion/topic.aspx?id=18194&show=empty%20mesh%20item)

More on the same problem, just FYI.

Take a look at the object layers and delete any empty ones. Export your work as an obj. I've never had a problem with preserving uvs.

Thanks, Paloth.  It looks like this bug is new with version 301 and will more easily occur when a mesh is imported (apparently an empty mesh item/layer is automatically created when you do that).  So users of other versions or those who've built their geometries within Modo wouldn't encounter the problem, apparently.

I'm glad to have a solution, however!  Thanks, everyone!  :D

Well, actually that's not quite right either. I have no problems with my figures. I use 301.

I OPEN the figure I want to use and not IMPORT. So try opening your figure and subD and see what happens. That may be the difference why it works for some of us and dosen't for others.

Yes, importing puts the imported mesh, and any textures applied, in a new group in the item list. There's already an empty mesh there waiting for you to start modelling - it's just called mesh, and the label is greyed out to indicate that it's empty: right-click on that and select delete to get rid of it.

Wow.  I didn't know I could use open for a non-native file type.  I expected it to work like Wings, where you can open a Wings file but have to import .obj.  Interesting.  Cage, meet learning curve. 

Thank you!  :D

You don't have to do any scaling with import or export either. LOL