Dyntopo detail size drawing with Shift + D seems broken #83623

New Issue

Metin Seven · 2020-12-10T11:30:02+01:00

Metin Seven commented

2020-12-10 11:30:02 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-12-09 01:29, hash: 9b11a7776f
Worked: At least a few alpha versions ago

Short description of error
Dyntopo size control with Shift + D seems broken.
The first time I tried, the gizmo simply froze and the Resolution value didn't change after mouse movement.
After installing the latest GeForce Studio Driver — version 457.30 — I tried again. The gizmo casts infinite lines, but I noticed that the Resolution value does change after mouse movement.

Exact steps for others to reproduce the error

Enter Sculpt Mode.
Activate Dyntopo.
Switch to Constant Detail mode.
Press Shift + D.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 460.79 **Blender Version** Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-12-09 01:29, hash: `9b11a7776f` Worked: At least a few alpha versions ago **Short description of error** Dyntopo size control with Shift + D seems broken. The first time I tried, the gizmo simply froze and the Resolution value didn't change after mouse movement. After installing the latest GeForce Studio Driver — version 457.30 — I tried again. The gizmo casts infinite lines, but I noticed that the Resolution value does change after mouse movement. **Exact steps for others to reproduce the error** 1. Enter Sculpt Mode. 2. Activate Dyntopo. 3. Switch to Constant Detail mode. 4. Press Shift + D.

Metin Seven commented

2020-12-10 11:30:02 +01:00

Added subscriber: @MetinSeven-1

blender-admin commented

2020-12-10 11:30:02 +01:00

#86695 was marked as duplicate of this issue

blender-admin commented

2020-12-10 11:30:02 +01:00

#84221 was marked as duplicate of this issue

Metin Seven commented

2020-12-10 12:52:33 +01:00

Addendum:

In a new Blender session, the gizmo behaved differently: directional lines were coming from the gizmo, showing change during mouse movement, but no Resolution value change.

Addendum: In a new Blender session, the gizmo behaved differently: directional lines were coming from the gizmo, showing change during mouse movement, but no Resolution value change. ![image.png](https://archive.blender.org/developer/F9500042/image.png)

Metin Seven commented

2020-12-10 13:03:36 +01:00

Addendum 2:

Installed the latest GeForce Studio Driver — version 457.30 — and tried again. The lines issue remains as described in my previous post, but I noticed that the Resolution value does change.

I guess this makes it a visual gizmo issue, not a functional issue.

Addendum 2: Installed the latest GeForce Studio Driver — version 457.30 — and tried again. The lines issue remains as described in my previous post, but I noticed that the Resolution value does change. I guess this makes it a visual gizmo issue, not a functional issue.

Philipp Oeser commented

2020-12-10 14:55:57 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-12-10 14:55:57 +01:00

Cannot reproduce here

**System Information**
Operating system: Linux-5.9.11-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits
Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01
version: 2.92.0 Alpha, branch: master, commit date: 2020-12-10 13:35, hash: `rBefb741b280f2`

Cannot reproduce here ``` **System Information** Operating system: Linux-5.9.11-200.fc33.x86_64-x86_64-with-fedora-33-Thirty_Three 64 Bits Graphics card: GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 455.45.01 version: 2.92.0 Alpha, branch: master, commit date: 2020-12-10 13:35, hash: `rBefb741b280f2` ```

serge commented

2020-12-11 00:24:12 +01:00

Added subscriber: @rpserge

serge commented

2020-12-11 00:24:12 +01:00

just got the same

just got the same ![image.png](https://archive.blender.org/developer/F9501012/image.png)

TheRedWaxPolice commented

2020-12-11 04:47:06 +01:00

Added subscriber: @TheRedWaxPolice

TheRedWaxPolice commented

2020-12-11 04:47:06 +01:00

In #83623#1072522, @MetinSeven-1 wrote:
The lines issue remains as described in my previous post, but I noticed that the Resolution value does change.

I have those line issues too yeah, but the resolution value in the UI only changes when I mouse hover on it.... 🤔

2020-12-11_04-35-44.mp4

> In #83623#1072522, @MetinSeven-1 wrote: > The lines issue remains as described in my previous post, but I noticed that the Resolution value does change. I have those line issues too yeah, but the resolution value in the UI only changes when I mouse hover on it.... 🤔 [2020-12-11_04-35-44.mp4](https://archive.blender.org/developer/F9502159/2020-12-11_04-35-44.mp4)

Metin Seven commented

2020-12-11 09:09:23 +01:00

Thanks for the confirmation guys. For a moment I was afraid it was a unique issue on my PC. 😅

Raimund Klink commented

2020-12-14 16:17:21 +01:00

Added subscriber: @Raimund58

Raimund Klink commented

2020-12-14 16:17:21 +01:00

I couldn't reproduce it.
But the lines go over the triangle

system-info.txt

I couldn't reproduce it. But the lines go over the triangle ![2020-12-14 16_08_23-Window.png](https://archive.blender.org/developer/F9508331/2020-12-14_16_08_23-Window.png) ![2020-12-14 16_10_04-Window.png](https://archive.blender.org/developer/F9508330/2020-12-14_16_10_04-Window.png) [system-info.txt](https://archive.blender.org/developer/F9508334/system-info.txt)

Evan Wilson commented

2020-12-14 18:04:03 +01:00

Added subscriber: @EAW

Evan Wilson commented

2020-12-14 18:04:03 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Evan Wilson commented

2020-12-14 18:04:03 +01:00

I can reproduce 100% of the time, but only when using blender_factory_startup.cmd.

Regular startup/blender_debug_cpu.cmd doesn't have the issue.

I figured out a way to sometimes reproduce it while using blender_debug_log.cmd.

(NOTE) Exact steps for others to reproduce the error

1. Lauch Blender using blender_debug_log.cmd.
2. Click Sculpting template on the splash screen.
**3.**In the Properties editor on the right side, switch from Render Properties to Active tool and Workspace settings.
4. Click the Dyntopo checkbox,

a. but only out of the corner of your eye since this is like the 4th time trying, since you want to be thorough and test all the .cmd files, so by this time you aren't really paying full attention.
5. Slightly move your mouse so that it fully covers the Dynotopo checkbox, but don't notice that you have done this.
6. See that the Cursor checkbox is checked.
7. Let self doubt sink in as you think "Wait, did I check the cursor checkbox instead?"
8. Uncheck the Cursor checkbox.
9. Recheck the Cursor checkbox.
10. Click the triangle to expand the Dynotopo menu.
11. Switch to Constant Detail.
12. Place your mouse cusor over the mesh and press Shift-D.

NOTE: Steps 4a through 7 are optional.

80% of the time, it will produce the Lines to Infinity!!!™.

10% of the time it won't reproduce the bug.

Once I got the triangle overlap that @Raimund58 shows above.

Another time, like @rpserge , I got Lines to ~~Infinity!!!~~ a single point whose location is determined by the distance of the cursor from the center of the mesh in Screenspace™ or LtaspwlidbtdotcftcotmiS™ for short.

I cannot reproduce when using blender_debug_log.cmd without steps of clicking the Cursor checkbox off and on.

version: 2.92.0 Alpha, branch: master, commit date: 2020-12-12 18:07, hash: 4797c13e8f, type: Release
OS: Windows-10-10.0.19041.630-SP0 64 Bits
GPU: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35
CPU: i7-950 @3.07 GHz SSE2 SSE3 SSE41 Detailed Specs
RAM: 8.00 GB

I can reproduce 100% of the time, but only when using `blender_factory_startup.cmd`. ![T83623_2.92_12.12.2020_hash_4797c13e8f3a.png](https://archive.blender.org/developer/F9508358/T83623_2.92_12.12.2020_hash_4797c13e8f3a.png) Regular startup/`blender_debug_cpu.cmd` doesn't have the issue. ![T83623_2.92_12.12.2020_hash_4797c13e8f3a_debug_gpu.png](https://archive.blender.org/developer/F9508360/T83623_2.92_12.12.2020_hash_4797c13e8f3a_debug_gpu.png) I figured out a way to *sometimes* reproduce it while using `blender_debug_log.cmd`. (NOTE) **Exact steps for others to reproduce the error** **1.** Lauch Blender using `blender_debug_log.cmd`. **2.** Click `Sculpting` template on the splash screen. **3.**In the `Properties` editor on the right side, switch from `Render Properties` to `Active tool and Workspace settings`. **4.** Click the `Dyntopo` checkbox, - **a.** *but only out of the corner of your eye since this is like the 4th time trying, since you want to be thorough and test all the `.cmd` files, so by this time you aren't __really__ paying full attention.* **5.** *Slightly move your mouse so that it fully covers the `Dynotopo` checkbox, but __don't__ notice that you have done this.* **6.** S*ee that the `Cursor` checkbox is checked.* **7.** *Let self doubt sink in as you think "Wait, did I check the cursor checkbox instead?"* **8.** Uncheck the `Cursor` checkbox. **9.** Recheck the `Cursor` checkbox. **10.** Click the triangle to expand the `Dynotopo` menu. **11.** Switch to `Constant Detail`. **12.** Place your mouse cusor over the mesh and press `Shift-D`. NOTE: Steps 4a through 7 are optional. 80% of the time, it will produce the ***Lines to Infinity!!!™***. 10% of the time it won't reproduce the bug. Once I got the triangle overlap that @Raimund58 shows above. ![T83623_2.92_12.12.2020_hash_4797c13e8f3a_debug_log_crop.png](https://archive.blender.org/developer/F9508437/T83623_2.92_12.12.2020_hash_4797c13e8f3a_debug_log_crop.png) Another time, like @rpserge , I got ***Lines to ~~Infinity!!!~~ a single point whose location is determined by the distance of the cursor from the center of the mesh in Screenspace™*** or ***LtaspwlidbtdotcftcotmiS™*** for short. ![Center_screen.png](https://archive.blender.org/developer/F9508445/Center_screen.png) ![Center_screen_center.png](https://archive.blender.org/developer/F9508447/Center_screen_center.png) ![Center_screen_center_v2.png](https://archive.blender.org/developer/F9508449/Center_screen_center_v2.png) I cannot reproduce when using `blender_debug_log.cmd` without steps of clicking the `Cursor` checkbox off and on. --- version: 2.92.0 Alpha, branch: master, commit date: 2020-12-12 18:07, hash: 4797c13e8f3a, type: Release OS: Windows-10-10.0.19041.630-SP0 64 Bits GPU: GeForce GTX 470/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35 CPU: i7-950 @3.07 GHz SSE2 SSE3 SSE41 Detailed Specs RAM: 8.00 GB

Metin Seven commented

2020-12-14 18:40:09 +01:00

In the previous build I had no issues with the Shift + D gizmo, but in the latest build (December 14, 17:06:03 - 010f44b855 , Windows 64 bit) it happened again.

In the previous build I had no issues with the Shift + D gizmo, but in the latest build (December 14, 17:06:03 - 010f44b855ca , Windows 64 bit) it happened again. ![image.png](https://archive.blender.org/developer/F9508565/image.png)

Pablo Dobarro commented

2020-12-28 22:53:59 +01:00

Added subscriber: @Phigon

Ovionis commented

2020-12-30 05:39:32 +01:00

In my earlier report, I said it happens from the start.
When I went to use this in my file, it was bugged so I reloaded Blender and saw it correctly. I then went to sample my mesh's resolution (ctrl+click), and thought it just mis-sampled it, so I cancelled. I then retried it and saw the thing was glitched.
As in, it wasn't glitched from the start of my Blender, it just started later.
I tried resetting and doing the same thing but this time it was just regular start-glitched 2 or 3 more times.

In my earlier report, I said it happens from the start. When I went to use this in my file, it was bugged so I reloaded Blender and saw it correctly. I then went to sample my mesh's resolution (ctrl+click), and thought it just mis-sampled it, so I cancelled. I then retried it and saw the thing was glitched. As in, it wasn't glitched from the start of my Blender, it just started later. I tried resetting and doing the same thing but this time it was just regular start-glitched 2 or 3 more times.

Metin Seven commented

2020-12-30 10:26:42 +01:00

Yes, the issues are inconsistent and have different visual anomalies.

Metin Seven commented

2021-03-03 15:41:41 +01:00

Just a little update: I'm still encountering this. Hope there will be some time left to fix it soon, @pablodp606. Thanks.

Metin Seven commented

2021-03-03 15:43:22 +01:00

Added subscriber: @PabloDobarro

Philipp Oeser changed title from ~~Dyntopo size control with Shift + D seems broken~~ to Dyntopo detail size drawing with Shift + D seems broken

2021-03-18 15:30:52 +01:00

Philipp Oeser commented

2021-03-18 15:32:17 +01:00

Added subscriber: @zNight

Vyacheslav Kobozev commented

2021-04-27 22:23:39 +02:00

Added subscriber: @Vyach

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Dyntopo detail size drawing with Shift + D seems broken #83623