3dsmax 2018 crashes with UVW Map modifier application

[grue1970]

i'm getting the issue now as well.  i will import from revit, work with it etc... in 2017.  then i opened in 2018, resaved the file and started working with it.  what happens is, i detached a few walls, reset xform, collapsed to edit mesh.  all is well, i mad sure to set all polys as the same material id and then added uvw map which defaults to real-world-units. finally i switch from planar to box and CRASH no CER report or anything just max disappears!

Your post has been made into a thread by @hagen.deloss: the old thread can be found here

[JGallagherP3A]

Make everything an editable poly as soon as you import from Revit and it wont happen. Not a solution, but it works at least.

[Diffus3d]

Hello @grue1970,

Just reading back through the thread, if you turn off snapping before you switch map types, does it help?  What if it's on an Edit Poly?   I wonder if @hagen.deloss has seen any updates to this in the tracker.  

Best Regards,

Alfred

[hagen.deloss · Accepted solution]

Hi @grue1970

Thanks for posting your issue in the forums! I'm looking in the internal database, and it says that this issue was resolved in 2018 update 4, have you installed that yet? 

It also looks like this issue can be sidestepped if you apply an edit poly modifier onto the object, as opposed to an edit mesh modifier, as @JGallagherP3A mentioned.

I tried to reproduce on a sphere with the steps outlined and couldn't replicate the issue, if the above steps don't help, would you mind attaching a file you are encountering this issue with so I can test on it?

Thanks for looping me in @Diffus3d I really appreciate it 😄

Please select the Accept as Solution button if a post solves your issue or answers your question.

[Diffus3d]

Happy to help in any way Hagen!   Thanks for the update on that one too!  

Best,

Alfred

[grue1970]

thanks all.  i will try the convert to edit poly and i'll look at the update to see if i have it.  i don't see any updates when i check via the help menu.  the version i have is 2018Update, 20.0 - 20.3.0.3149.

also i opened the original file again (i had done a save as with a new name) and in that file i tried exactly the same things to cause the crash and NO CRASH! ha. oh well.  i will try the edit poly thing the next time. i'll just log it in my mind that it can crash with uvwmap modifiers and ctrl-s before i do that unless it's geometry i created 🙂

here are the steps i did which resulted in the crash and then no crash just now ha.

1. open file
2. isolated revit mesh
mesh had been imported, reset xform, uvwmap applied previously
and still on the stack
3. detached walls, with the uvwmap still on the stack
4. new walls object no longer had correct mapping
it was extremely large like it had been on inital import
after having reset xform - ie mapping behaved as though
it was 1200% scale
5. existed isolation mode
6. saved file to desktop
7. selected new walls object, it did not have uvwmap
8. changed material to another material i the scene
9. added uvwmap, it was set to planar, changed to box - NO CRASH!?

[hagen.deloss]

Hi @grue1970

If you log into your Autodesk account on the website, you can download the most recent update package in your product management portal, here is what mine looks like.

Let me know if you aren't seeing 2018.4 on your list!

I guess it's a good thing that you didn't experience another crash with your older file...though it does make it harder to find the root cause haha.

Lets see if updating clears this issue up and go from there!

Please select the Accept as Solution button if a post solves your issue or answers your question.

[grue1970]

thanks. so i have to open autodesk desktop app, i see in there an update dated dec 5, 2017.  i'm currently downloading that. i would guess that if i see that update in the desktop  app, then i must not have it installed.  hm. so otherwise you can't just go to check for updates anymore within the program/help/about?  that's OK. or maybe it's diff because i'm on a business account anyway it is updating!

[hagen.deloss]

@grue1970

I hope the update helps with the issue you are experiencing, keep me updated if not!