Dyntopo finding non-existent vertex data #100957

New Issue

Ovionis · 2022-09-10T07:31:52+02:00

Ovionis commented

2022-09-10 07:31:52 +02:00

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95

Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-09-07 19:33, hash: 0a32f6b76a

Short description of error
In sculpt mode, if you click the checkbox for Dyntopo, you will be given a warning about it not preserving certain vertex data, which you then have to click Ok to ignore.
If you leave sculpt mode with Dyntopo enabled, then you enter sculpt mode again for the object, Dyntopo will be disabled again with a warning in the status bar telling you vertex data was found so it disabled Dyntopo.

This happens despite the mesh not having any vertex data. No Vertex Data/UVs/Materials/Attributes/etc
Add any new mesh object, and disable or delete the UVs to get what's supposed to be a clean mesh.

**System Information** Operating system: Windows-10-10.0.19042-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.95 **Blender Version** Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-09-07 19:33, hash: `0a32f6b76a` **Short description of error** In sculpt mode, if you click the checkbox for Dyntopo, you will be given a warning about it not preserving certain vertex data, which you then have to click Ok to ignore. If you leave sculpt mode with Dyntopo enabled, then you enter sculpt mode again for the object, Dyntopo will be disabled again with a warning in the status bar telling you vertex data was found so it disabled Dyntopo. This happens despite the mesh not having any vertex data. No Vertex Data/UVs/Materials/Attributes/etc Add any new mesh object, and disable or delete the UVs to get what's supposed to be a clean mesh.

Ovionis commented

2022-09-10 07:31:52 +02:00

Added subscriber: @Phigon

blender-admin commented

2022-09-10 07:31:52 +02:00

#103891 was marked as duplicate of this issue

blender-admin commented

2022-09-10 07:31:52 +02:00

#102852 was marked as duplicate of this issue

TheRedWaxPolice commented

2022-09-10 17:42:22 +02:00

Added subscriber: @TheRedWaxPolice

Omar Emara commented

2022-09-12 12:21:45 +02:00

Added subscriber: @OmarEmaraDev

Omar Emara commented

2022-09-12 12:21:45 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Omar Emara commented

2022-09-12 12:21:45 +02:00

It seems there is a custom data layer of type bool that goes by the name of .hide_vert. But I am not sure how it should be handled, maybe a special warning could be added for this particular layer. Tagging the module for more information.

It seems there is a custom data layer of type bool that goes by the name of `.hide_vert`. But I am not sure how it should be handled, maybe a special warning could be added for this particular layer. Tagging the module for more information.

Julien Kaspar commented

2022-09-12 16:11:52 +02:00

Added subscribers: @HooglyBoogly, @JulienKaspar

Julien Kaspar commented

2022-09-12 16:11:52 +02:00

@HooglyBoogly You have more information on this?

Hans Goudey commented

2022-09-12 17:13:12 +02:00

After D15937, this will only happen when part of the mesh is hidden at least. But it probably makes sense to disable the warning for the hide attributes in particular.

After [D15937](https://archive.blender.org/developer/D15937), this will only happen when part of the mesh is hidden at least. But it probably makes sense to disable the warning for the hide attributes in particular.

Hans Goudey commented

2022-09-13 16:43:01 +02:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'