Multires not preserving visibility state when switching levels #122243

New Issue

TheRedWaxPolice · 2024-05-25T00:02:59+02:00

TheRedWaxPolice commented

2024-05-25 00:02:59 +02:00

System Information
Operating system: Win 10

Blender Version
Broken: blender-4.2.0-alpha+main.d960b922b311-windows.amd64-release
Worked: No idea...

Short description of error
Not sure if it's a bug or limitation, but the multires doesn't properly preserve the visibility state of the mesh when you switch levels or when you turn off/on the modifier in the viewport...

Exact steps for others to reproduce the error
Add multires to the cube, go to sculpt mode, choose the box hide tool and hide part of the mesh...
Switch to the lower subdivision levels and then go up again, or just turn off and then turn on the modifier....
As you can see, the visibility state is not restored as it was before...

See:

**System Information** Operating system: Win 10 **Blender Version** Broken: blender-4.2.0-alpha+main.d960b922b311-windows.amd64-release Worked: No idea... **Short description of error** Not sure if it's a bug or limitation, but the multires doesn't properly preserve the visibility state of the mesh when you switch levels or when you turn off/on the modifier in the viewport... **Exact steps for others to reproduce the error** Add multires to the cube, go to sculpt mode, choose the box hide tool and hide part of the mesh... Switch to the lower subdivision levels and then go up again, or just turn off and then turn on the modifier.... As you can see, the visibility state is not restored as it was before... See: <video controls="" src="https://projects.blender.org/attachments/5d3c82f5-fd71-4752-a70e-d694437dbb0e"></video>

blender_Q94ucMhL8T.mp4

1.6 MiB

TheRedWaxPolice added the

labels 2024-05-25 00:03:00 +02:00

Sean Kim commented

2024-05-25 00:59:23 +02:00

As far as I can tell this has exhibited weird behavior since 2.80 at least - I'm inclined to think that this is a limitation, but I don't have enough historical knowledge to say definitively without looking further into the code.

TheRedWaxPolice commented

2024-05-25 01:34:22 +02:00

As far as I can tell this has exhibited weird behavior since 2.80 at least - I'm inclined to think that this is a limitation, but I don't have enough historical knowledge to say definitively without looking further into the code.

I just found out that it worked fine in 2.79... 🤔

So, regression, right?

> As far as I can tell this has exhibited weird behavior since 2.80 at least - I'm inclined to think that this is a limitation, but I don't have enough historical knowledge to say definitively without looking further into the code. I just found out that it worked fine in 2.79... 🤔 <video controls="" src="https://projects.blender.org/attachments/0b68a55e-6223-4876-8f79-81f964e4128d"></video> So, regression, right?

blender_5uEx9Zf0VI.mp4

933 KiB

Sean Kim commented

2024-05-25 01:38:36 +02:00

Seems like it, though certainly not a recent one if it broke between 2.79 and 2.80

👍 1

Sean Kim referenced this issue

2024-05-25 01:40:41 +02:00

Multiresolution Issues #107118

Pratik Borhade commented

2024-05-25 08:43:08 +02:00

I can confirm