Subdivision: GPU Subdivision shows corrupt geometry on high polycount objects #94881

New Issue

Garek · 2022-01-13T15:06:21+01:00

Garek commented

2022-01-13 15:06:21 +01:00

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-11 23:26, hash: ef5d01d98f
Worked: never

Short description of error
When mesh have high polycount GPU Subdivision option shows corrupt geometry (lost, mangled geometry etc.). Generally objects with loose geometry will trigger issue easier. When using Simple type instead of Catmull-Clark issue does not shown but increasing polycount by subdividing in edit mode will trigger it again.
Also note that using mesh with less polycount but higher subdivision surface modifier level will not show issue even when resulting polycount is higher.

Exact steps for others to reproduce the error

Open attached file. There is subdivided cube with loose geometry (8 times subdivided only loose geometry), cube (8 times) and Suzanne (5 times).
Make sure GPU Subdivision is checked in preferences
Add Subdivision Surface modifier to any object.
Uncheck GPU Subdivision in preferences to see correct mesh.
GPU subdivision corruption.blend

**System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: AMD Radeon HD 7800 Series ATI Technologies Inc. 4.5.14831 Core Profile Context 21.5.2 27.20.20903.8001 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-11 23:26, hash: `ef5d01d98f` Worked: never **Short description of error** When mesh have high polycount `GPU Subdivision` option shows corrupt geometry (lost, mangled geometry etc.). Generally objects with loose geometry will trigger issue easier. When using `Simple` type instead of `Catmull-Clark` issue does not shown but increasing polycount by subdividing in edit mode will trigger it again. Also note that using mesh with less polycount but higher subdivision surface modifier level will not show issue even when resulting polycount is higher. **Exact steps for others to reproduce the error** 1. Open attached file. There is subdivided cube with loose geometry (8 times subdivided only loose geometry), cube (8 times) and Suzanne (5 times). 2. Make sure `GPU Subdivision` is checked in preferences 3. Add `Subdivision Surface` modifier to any object. 5. Uncheck `GPU Subdivision` in preferences to see correct mesh. [GPU subdivision corruption.blend](https://archive.blender.org/developer/F12803761/GPU_subdivision_corruption.blend)

Garek commented

2022-01-13 15:06:21 +01:00

Added subscriber: @Garek

Garek commented

2022-01-13 15:07:59 +01:00

Will not confirm myself on the off chance it's some driver/GPU issue or something.

Garek changed title from ~~Subdivision:~~ to Subdivision: GPU Subdivision shows corrupt geometry on high polycount objects

2022-01-13 15:10:04 +01:00

Pratik Borhade commented

2022-01-14 07:43:34 +01:00

Added subscriber: @PratikPB2123

Kévin Dietrich commented

2022-01-14 12:14:28 +01:00

Added subscribers: @Jeroen-Bakker, @kevindietrich

Kévin Dietrich commented

2022-01-14 12:14:28 +01:00

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

Kévin Dietrich commented

2022-01-14 12:14:28 +01:00

I cannot reproduce (using an NVidia card). @Jeroen-Bakker can you try to reproduce this on an AMD card, please?

Garek commented

2022-01-15 18:32:52 +01:00

I experimented with Advanced options of modifier later at the time and was convinced it's same bug but apparently unchecking Use Limit Surface is separate bug that triggers on geometry even with low polycount. I mistaken them since this bug sometimes collapses geometry too. I filed a separate bugreport #94936.
To note: with this bug when geometry disappears viewport doesn't lag as if there is no geometry at all (it takes me dozens of seconds to add modifier).

I experimented with Advanced options of modifier later at the time and was convinced it's same bug but apparently unchecking Use Limit Surface is separate bug that triggers on geometry even with low polycount. I mistaken them since this bug sometimes collapses geometry too. I filed a separate bugreport #94936. To note: with this bug when geometry disappears viewport doesn't lag as if there is no geometry at all (it takes me dozens of seconds to add modifier).

Garek commented

2022-01-15 18:46:44 +01:00

Also another note: it's possible issue shown only with loose geometry such as Suzanne (but not always), deleting eyes for her didn't trigger issue. All other cases without loose geometry that I tested but later deleted (don't want to upload 200+ mb file) maybe just #94936.

Jesse Yurkovich commented

2022-01-16 22:53:22 +01:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2022-01-16 22:53:22 +01:00

I also cannot reproduce when using a 1070 nVidia card. However, a very old AMD FirePro W2100 shows what's been demonstrated here so perhaps is related to AMD (or at least the older ones).

blender-admin commented

2022-02-16 16:55:35 +01:00

This issue was referenced by c5dcfb63d9

This issue was referenced by c5dcfb63d9e40138f03c135346bfa779abcb0e58

Kévin Dietrich commented

2022-02-17 13:14:40 +01:00

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

Kévin Dietrich closed this issue

2022-02-17 13:14:40 +01:00

Kévin Dietrich self-assigned this 2022-02-17 13:14:40 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Subdivision: GPU Subdivision shows corrupt geometry on high polycount objects #94881