"Edit Poly" modifiers always ruin uv's from previous "unwrap UVW" modifier

[bksong]

Unless I collapse my modifier stack after unwrapping uv's, an edit poly modifier will destroy any unwrapping i've done.

I've always thought this was normal until other max users told me they dont get this problem. Anyone know why this would happen?

[Alfred.DeFlaminis]

Hello @bksong and welcome to the community,

This is very strange.  I'd like to check the file if possible, it's hard to guess what is happening based on the screenshots.  Just to be thorough, do you have the latest service packs?  

I can create a private folder for you if privacy is really important for this object, just say the word.  I'll do whatever I can to help you.

Best Regards,

[Alfred.DeFlaminis]

Hello @bksong,

I just wanted to follow up here, any progress on this issue?  Should I create a folder for you so I can check the file?  

Best Regards,

[bksong]

Hi Alfred, I'm so sorry for the ridiculously delayed response! I forgot about this thread. Actually had the same problem currently and ended up googling my own post coincidentally.

I recall it happening in my 2014,16, and 17 versions for pretty much any scene or project. I've attached a test scene with an example of the issue.

[Anonymous · Accepted solution]

I tried your test scene in 2018.3 and this issue doesn`t happen here. UV`s got nicely preserved between the two UVW-Unwrap modifiers.Even when adding additional edge-loops at the editPoly-modifier.

The 2018.x releases had a lot of fixes for UVW-Unwrap and it seems this defect was fixed in 2018.1.

MAXX-32192

Modeling: UVW

Fixed issue with UV's breaking when adding topology modifiers between UVW Unwraps.

[jibijib]

Just tried this on a scene in 2017 and it definitely does it. Edit Poly > Unwrap UVW > Edit Poly just creates a planar Z map, even without any modifications in the edit poly modifier. "Edit Poly" is a different modifier to "Editable Poly" though - shouldn't be any reason why it should do it though.

Must've slipped under the radar - is it fixed in 2018?

[Anonymous]

---

@jibijib wrote:

Just tried this on a scene in 2017 and it definitely does it. Edit Poly > Unwrap UVW > Edit Poly just creates a planar Z map, even without any modifications in the edit poly modifier. "Edit Poly" is a different modifier to "Editable Poly" though - shouldn't be any reason why it should do it though.

Must've slipped under the radar - is it fixed in 2018?

---

Indeed,it was fixed in 2018.1

[Anonymous]

I'm on Max 2018 and I'm still having this same issue. It actually worked fine in Max 2015 but it breaks my UVs in 2018. Just like jibijib said, it maps the entire object from the Z plane after unwrap uvw is re-applied

[Anonymous · Accepted solution]

---

@Anonymous wrote:

I'm on Max 2018 and I'm still having this same issue. It actually worked fine in Max 2015 but it breaks my UVs in 2018. Just like jibijib said, it maps the entire object from the Z plane after unwrap uvw is re-applied

---

It was fixed in 2018.1 and newer. Seems you are on 2018.0 the initial release.

Check the product version Main-Menu->Help->Autodesk Product Information->About 3dsmax.

[Anonymous]

It appears I am. Is there any way to update my version without re-installing the whole thing? I really don't wanna have to re-do all my keybinds and viewport layouts

[hagen.deloss · Accepted solution]

Hi everyone! 

I wanted summarize this issue and make a note that the issue has been resolved in 3DS Max 2018 update 1 and subsequent releases.

Users on previous releases of 3DS Max before 2018.1 were encountering their UV modifier edits resetting after applying an edit poly modifier on their object.

A potential solution to this issue is to download the most current Update of 3DS Max 2018 or 2019. You can do so by logging onto you Autodesk account and following these steps.

Thanks to everyone for helping to document this issue here, I hope this helps folks out 😄

[Anonymous]

Sorry to revive a possibly dead thread, I just wanted to add my two cents to the "Official" recap/answer to this problem. I've been having this issue as well, I'm running 3ds max 2017 (Don't really know what service pack and never been able to remember how to read it, my bad, but this is what I get from the maxVersion() command at least: #(19000, 48, 0)). Its been an issue bothering me for a week, but I think I found a solution to it!

In the edit poly modifier (if multiple edit poly's probably everyone) make sure to check "Preserve UV's" and make sure that the right channel is selected etc. Then after applying the unwrap modifier and seeing it break, hit "Reset UVWs" in the channel dropdown. It then seems to snap back to the unwrap that was present before.

I really don't wanna update to 2018 and later, love the big 3ds max button and quick access to recent projects too much XD

Hopefully, it's a working solution that can benefit someone having this issue 🙂

Edit: It does also seem to work even if you don't have the "Preserve UV" checked in the edit poly modifier.

[hagen.deloss]

@Anonymous

This is super useful information! I haven't encountered this issue, so I'm not able to confirm that it works seamlessly, but for those that are curious, You can find the save and reset UVW unwraps by following these steps.

1. Navigate to the UVW Unwrap Modifier in the Command Panel 
2. Select the dropdown tab Channel 
3. There is the Reset UVWs, Save and Load options

I have attached a screenshot of this UI element as well.

[Anonymous]

So I don't know if this will help recreate this, but my situation at least is as follows:

- I'm working on/modifying.FBX files of unknown origins (I've recently joined a project and some of the models need some touch-up. They are .fbx files but I have no idea what program they were originally modeled/unwrapped in.)

- The unwrap breaking is not completely consistent but mostly happens after I (moderately) adjust the poly count with an edit poly modifier, bridging, welding, cloning out more sub-objects etc.

If it is of any interest I could also send you a max file, maybe over private message, that contains a model I know has this issue on my end @hagen.deloss ?

[katie.manchester]

The brand new 2024 version is having this issue, wth, you'd think it would be long gone by now.