Crash while sculpting with tablet using Dyntopo #106784

New Issue

Jeff-C-1 · 2023-04-11T07:39:48+02:00

Jeff-C-1 commented

2023-04-11 07:39:48 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41

Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: 1be25cfff18b
Worked: (newest version of Blender that worked as expected)

Short description of error
Blender Stalls when using any brush, while dyntopo is activated, using a tablet to sculpt then immediately orbiting the view with cursor over mesh, consistently. Will not crash using a mouse. Happens in both this version of blender and 3.4.1. But not earlier versions.

Exact steps for others to reproduce the error

Add object
Enable sculpt mode
Enable dyntopo
Use mouse to begin sculpting in any detailing type, and in subdivide/collapse. Works for hours.
Switch to using a tablet
Begin sculpting
If you sculpt the mesh using any brush and immediately after orbit view with alt+LMK (alt+Pen Tip tap) key, and the cursor is over the mesh, blender stalls.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.41 **Blender Version** Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash: `1be25cfff18b` Worked: (newest version of Blender that worked as expected) **Short description of error** Blender Stalls when using any brush, while dyntopo is activated, using a tablet to sculpt then immediately orbiting the view with cursor over mesh, consistently. Will not crash using a mouse. Happens in both this version of blender and 3.4.1. But not earlier versions. **Exact steps for others to reproduce the error** 1. Add object 2. Enable sculpt mode 3. Enable dyntopo 4. Use mouse to begin sculpting in any detailing type, and in subdivide/collapse. Works for hours. 5. Switch to using a tablet 6. Begin sculpting 7. If you sculpt the mesh using any brush and immediately after orbit view with alt+LMK (alt+Pen Tip tap) key, and the cursor is over the mesh, blender stalls.

Jeff-C-1 added the

labels 2023-04-11 07:39:49 +02:00

YimingWu commented

2023-04-11 13:38:02 +02:00

Couldn't reproduce the issue on 3.5 or 3.6, I'm on linux with a wacom device, could you tell us what tablet are you using?

Jeff-C-1 commented

2023-04-11 22:32:10 +02:00

@ChengduLittleA Thanks for the response.

After some more sleuthing, I found that if I shut-down Keypress OSD, no more crashing using a tablet with dyntopo enabled. Unfortunately, I cannot teach sculpting using Dyntopo without Keypress OSD active. Can we figure out why this is happening?

Blender setup:
I am using Industry standard shortcuts with a few modifications:
I have modified quite a few of the default brush bindings as well as the remesh and dyntopo keys.

All brushes mapped to the following keys t y u i o p, g h j k l, and c v b n m.
Remesh = CTRL+R, Remesh Res = SHIFT+R.
Dyntopo = CTRL+D, Dyntopo Resolution = SHIFT+D.
Default navigation keys of ALT+LMB = Orbit, ALT+MMB = Pan, ALT+RMB = Zoom.
I added the keyboard shortcut that allows for selecting other objects when sculpting and mapped this to CTRL+SHIFT+RMB.
And as you will see in the images below, I have the LMB mapped to the pen touching the tablet, the MMB to the lower button, and the RMB to the upper button on the pen.
I have click+tap set for all actions in the tablet settings, for the pen, to prevent accidental button presses.

Software Versions:
Keypress OSD v4.67.0 (I do not have anything mapped to the ALT+LMB nor LMB then ALT+LMB)
Wacom Intuos 4 Large tablet
Wacom Driver 6.3.41-1

Tablet Settings:

@ChengduLittleA Thanks for the response. After some more sleuthing, I found that if I shut-down Keypress OSD, no more crashing using a tablet with dyntopo enabled. Unfortunately, I cannot teach sculpting using Dyntopo without Keypress OSD active. Can we figure out why this is happening? Blender setup: I am using Industry standard shortcuts with a few modifications: I have modified quite a few of the default brush bindings as well as the remesh and dyntopo keys. * All brushes mapped to the following keys t y u i o p, g h j k l, and c v b n m. * Remesh = CTRL+R, Remesh Res = SHIFT+R. * Dyntopo = CTRL+D, Dyntopo Resolution = SHIFT+D. * Default navigation keys of ALT+LMB = Orbit, ALT+MMB = Pan, ALT+RMB = Zoom. * I added the keyboard shortcut that allows for selecting other objects when sculpting and mapped this to CTRL+SHIFT+RMB. * And as you will see in the images below, I have the LMB mapped to the pen touching the tablet, the MMB to the lower button, and the RMB to the upper button on the pen. * I have click+tap set for all actions in the tablet settings, for the pen, to prevent accidental button presses. Software Versions: Keypress OSD v4.67.0 (I do not have anything mapped to the ALT+LMB nor LMB then ALT+LMB) Wacom Intuos 4 Large tablet Wacom Driver 6.3.41-1 Tablet Settings: ![image](/attachments/d205fe6f-706d-4ee7-a437-80231a9fb12c) ![image](/attachments/592ae882-0e5f-4b64-b20e-37e3a4d0ebd7) ![image](/attachments/5bb34993-d764-4be7-8b03-1d9c37d7f0df)

image.png

16 KiB

image.png

29 KiB

image.png

30 KiB

image.png

22 KiB

Jeff-C-1 commented

2023-04-11 23:41:08 +02:00

@ChengduLittleA well... crashed again, but I was able to sculpt much longer without the input visualizer on. I am so confused. It is so random too. I am not sure what else to do or what else I can provide to help with debugging this issue.

YimingWu commented

2023-04-12 04:50:49 +02:00

@Jeff-C-1 If disabling Keypress OSD makes it work better, then you could do that for now. In blender there's also a small plugin Screencast Keys available for you to display key inputs without using separate software.

If you can, please share us the file that's causing the crash which you could reliably reproduce the issue, thanks!

@Jeff-C-1 If disabling Keypress OSD makes it work better, then you could do that for now. In blender there's also a small plugin [Screencast Keys](https://github.com/nutti/Screencast-Keys) available for you to display key inputs without using separate software. If you can, please share us the file that's causing the crash which you could reliably reproduce the issue, thanks!

Jeff-C-1 commented

2023-04-12 05:38:33 +02:00

@Jeff-C-1 If disabling Keypress OSD makes it work better, then you could do that for now. In blender there's also a small plugin Screencast Keys available for you to display key inputs without using separate software.

If you can, please share us the file that's causing the crash which you could reliably reproduce the issue, thanks!

Unfortunately, turning off the Screencast OSD did not prevent the crashes. It happens in every file where I enable Dyntopo and use my tablet. I have created 8 demo tiles trying to create the same asset but cannot complete the demo because of this issue. Seems to happen when I change the detail setting. I also used screencast keys addon, which is great only for blender. But I still get the crash.

It did not crash like this before 3.4.1. I demonstrated dyntopo to my students using a previous version without error.

I will try it on another computer to see if the issue is hardware specific and get back to you.

> @Jeff-C-1 If disabling Keypress OSD makes it work better, then you could do that for now. In blender there's also a small plugin [Screencast Keys](https://github.com/nutti/Screencast-Keys) available for you to display key inputs without using separate software. > > If you can, please share us the file that's causing the crash which you could reliably reproduce the issue, thanks! Unfortunately, turning off the Screencast OSD did not prevent the crashes. It happens in every file where I enable Dyntopo and use my tablet. I have created 8 demo tiles trying to create the same asset but cannot complete the demo because of this issue. Seems to happen when I change the detail setting. I also used screencast keys addon, which is great only for blender. But I still get the crash. It did not crash like this before 3.4.1. I demonstrated dyntopo to my students using a previous version without error. I will try it on another computer to see if the issue is hardware specific and get back to you.

YimingWu commented

2023-04-12 05:41:56 +02:00

@Jeff-C-1 it's best if we could have a file, or at least those crash logs to determine the issue.

@Jeff-C-1 it's best if we could have a file, or at least those [crash logs](https://docs.blender.org/manual/en/3.5/troubleshooting/crash.html) to determine the issue.

Jeff-C-1 commented

2023-04-16 23:23:53 +02:00

@ChengduLittleA unfortunately, it is never a crash. It is always a stall. Usually happens when using a low resolution.

I changed two things though and was finally able to completely create the video lesson of the sculpt for my students. I turned off Alt+LMB enumeration menu selection in the keyboard shortcuts, and worked in a larger size. I was creating a candle at 1" x 10". It would only begin to crash when subdividing the mesh using relative detail with a small number in relative detail. I have had issues in the past with blenders vertices welding at smaller scales so I tend to work much larger and scale my objects down later. But for some reason, I did not do it this way this time around. After I decided to work in 1m x 10m instead of 1" x 10", the refine method was able to subdivide and collapse almost instantaneously, with no hitches like it was having when using this same method at a lower scale. I am not sure if any of this made sense, but I do believe, much like welding does not work well at lower scales, maybe the refine method of dyntopo also does not work at smaller scales causing a complete stall of the program requiring a hard quit of the program every time. Then, the alt+lmb was killing me. Every time my mouse was over the object and I would paint then immediately use alt+penTap to orbit, it would go into stall. Not sure if it was the alt+penTap or the speed at which I was asking dyntopo to calculate the subdivisions at such a small scale.

I will reach out if this continues to be an issue. In the meantime, if you want my crash logs, I need help finding them. I am using the portable version of blender in industry standard shortcut mode with highly modified sculpting keyboard shortcuts.

@ChengduLittleA unfortunately, it is never a crash. It is always a stall. Usually happens when using a low resolution. I changed two things though and was finally able to completely create the video lesson of the sculpt for my students. I turned off Alt+LMB enumeration menu selection in the keyboard shortcuts, and worked in a larger size. I was creating a candle at 1" x 10". It would only begin to crash when subdividing the mesh using relative detail with a small number in relative detail. I have had issues in the past with blenders vertices welding at smaller scales so I tend to work much larger and scale my objects down later. But for some reason, I did not do it this way this time around. After I decided to work in 1m x 10m instead of 1" x 10", the refine method was able to subdivide and collapse almost instantaneously, with no hitches like it was having when using this same method at a lower scale. I am not sure if any of this made sense, but I do believe, much like welding does not work well at lower scales, maybe the refine method of dyntopo also does not work at smaller scales causing a complete stall of the program requiring a hard quit of the program every time. Then, the alt+lmb was killing me. Every time my mouse was over the object and I would paint then immediately use alt+penTap to orbit, it would go into stall. Not sure if it was the alt+penTap or the speed at which I was asking dyntopo to calculate the subdivisions at such a small scale. I will reach out if this continues to be an issue. In the meantime, if you want my crash logs, I need help finding them. I am using the portable version of blender in industry standard shortcut mode with highly modified sculpting keyboard shortcuts.

Jeff-C-1 commented

2023-04-16 23:24:57 +02:00

Also, I updated my graphics card driver due to new release two days ago. Maybe that did the trick? I went with the Game Ready NVIDIA drivers instead of the Studio version.

YimingWu commented

2023-04-17 09:29:27 +02:00

We probably need more input from graphic guys here.

The only erroneous "lag" I've encountered related to a driver issue is to have a shader subroutine exit while locks in place, and sometimes a zero-length draw call would cause that as well. I'm pretty much sure it's not the case here.

We probably need more input from graphic guys here. The only erroneous "lag" I've encountered related to a driver issue is to have a shader subroutine exit while locks in place, and sometimes a zero-length draw call would cause that as well. I'm pretty much sure it's not the case here.

Pratik Borhade commented

2023-04-25 06:56:14 +02:00

Hi, does switching tablet API help?: Edit > Preference > Input > tablet API
Upgrade tablet drivers, see if that makes difference.
Run blender with --debug-wintab argument, does it capture any errors related to freeze?
This issue could be related to #94963

Hi, does switching tablet API help?: `Edit > Preference > Input > tablet API` Upgrade tablet drivers, see if that makes difference. Run blender with `--debug-wintab` argument, does it capture any errors related to freeze? This issue could be related to #94963

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-04-25 06:56:24 +02:00

Pratik Borhade commented

2023-05-25 07:05:48 +02:00

Hi, any updates here?

Pratik Borhade commented

2023-06-09 06:06:30 +02:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

Pratik Borhade closed this issue

2023-06-09 06:06:32 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-06-09 06:06:34 +02:00

Jeff-C-1 commented

2023-11-14 00:02:24 +01:00

Issue still stands. I have many students who reported the same issue. Only when the brush settings are set to relative or brush detail, with subdivide and collapse enabled. If it is only Subdivide, not collapse, everything is good.

Issue still stands. I have many students who reported the same issue. Only when the brush settings are set to relative or brush detail, with subdivide and collapse enabled. If it is only Subdivide, not collapse, everything is good. ![image](/attachments/d44703c3-ab20-4ec9-a7c4-f21619600ab6)

image.png

171 KiB

Jeff-C-1 reopened this issue

2023-11-14 00:02:27 +01:00

Blender Bot added

and removed

labels 2023-11-14 00:02:28 +01:00

Philipp Oeser commented

2024-01-02 13:18:03 +01:00

Sorry this has been lying around a bit... Also cannot reproduce here.

We now have the primary report description a bit out of sync with the added information from later comments.
Could we try to put these in the very first comment, too?

Since sizes of objects and sizes of brush detail seem to be relevant, could you share a .blend file that triggers this easily (maybe having a bit extreme values here so we get to a freeze more reliably)

Sorry this has been lying around a bit... Also cannot reproduce here. We now have the primary report description a bit out of sync with the added information from later comments. Could we try to put these in the very first comment, too? Since sizes of objects and sizes of brush detail seem to be relevant, could you share a .blend file that triggers this easily (maybe having a bit extreme values here so we get to a freeze more reliably)

Philipp Oeser added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-01-02 13:18:13 +01:00

Philipp Oeser commented

2024-01-18 11:41:30 +01:00

poke ^

Philipp Oeser commented

2024-02-26 09:11:14 +01:00

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.

Philipp Oeser closed this issue

2024-02-26 09:11:20 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-02-26 09:11:22 +01:00

Sign in to join this conversation.