Initial stroke delay - clay strips #110794

Open
opened 2023-08-04 14:43:53 +02:00 by Daniel Aubert · 10 comments

System Information
Operating system: Windows-10-10.0.22621-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98

Blender Version
Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: 8bda729ef4dc
Worked: (newest version of Blender that worked as expected)

Short description of error
When you start a stroke in sculpt mode with the clay strips brush, it takes some movement for it to start registering. Previous versions of Blender didn't have this problem. See video to understand better (sorry for the low audio volume, if you can, wear headphones or raise the volume).

Exact steps for others to reproduce the error
Just start a stroke with clay strips, it will take a drag to appear. It can be reproduced in default room.

**System Information** Operating system: Windows-10-10.0.22621-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 535.98 **Blender Version** Broken: version: 3.6.1, branch: blender-v3.6-release, commit date: 2023-07-17 12:50, hash: `8bda729ef4dc` Worked: (newest version of Blender that worked as expected) **Short description of error** When you start a stroke in sculpt mode with the clay strips brush, it takes some movement for it to start registering. Previous versions of Blender didn't have this problem. See video to understand better (sorry for the low audio volume, if you can, wear headphones or raise the volume). **Exact steps for others to reproduce the error** Just start a stroke with clay strips, it will take a drag to appear. It can be reproduced in default room.
Daniel Aubert added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-04 14:43:53 +02:00
Author

I think the video didn't upload. Here it is in youtube: https://youtu.be/Y-IQiyD5zIw

I think the video didn't upload. Here it is in youtube: [](https://youtu.be/Y-IQiyD5zIw) https://youtu.be/Y-IQiyD5zIw
Member

Can confirm it's becoming this way between 3.3 and 3.5.

Not sure if it's entirely intentional since the clay brush is square-looking and the longer initial stroke may give it a better direction hint so there won't be a random twist at the beginning due to mouse position jitter.

Can confirm it's becoming this way between 3.3 and 3.5. Not sure if it's entirely intentional since the clay brush is square-looking and the longer initial stroke may give it a better direction hint so there won't be a random twist at the beginning due to mouse position jitter.

I have the same problem since version 3.6 +. It sometimes won't even lay down strokes for me until I lift the pen and retry the spot and then it adds displacement unexpectedly. I can open the same file in 3.5 and the clay strips works as expected.

Thank you in advance to the developers looking into this. ❤️

I have the same problem since version 3.6 +. It sometimes won't even lay down strokes for me until I lift the pen and retry the spot and then it adds displacement unexpectedly. I can open the same file in 3.5 and the clay strips works as expected. Thank you in advance to the developers looking into this. ❤️
Member

Yeah I can confirm this. It's less noticeable with radius pressure sensitivity and low pressure.
But it's definitely too noticeable otherwise.

Yeah I can confirm this. It's less noticeable with radius pressure sensitivity and low pressure. But it's definitely too noticeable otherwise.
Julien Kaspar added
Status
Confirmed
Type
Bug
and removed
Status
Needs Info from Developers
Type
Report
labels 2023-08-28 17:38:18 +02:00
Member

I talked with @Sergey. It would be good to check what the minimum needed distance is to reliably calculate the direction of the brush. Right now it just seems way to high.

I talked with @Sergey. It would be good to check what the minimum needed distance is to reliably calculate the direction of the brush. Right now it just seems way to high.

I talked with @Sergey. It would be good to check what the minimum needed distance is to reliably calculate the direction of the brush. Right now it just seems way to high.

Hi Julien,

Is this something you want us users to check?

If so, how would we go about checking the distance as you mentioned?

Forgive me I'm new at this. Maybe your comment was towards other developers... 😅

> I talked with @Sergey. It would be good to check what the minimum needed distance is to reliably calculate the direction of the brush. Right now it just seems way to high. Hi Julien, Is this something you want us users to check? If so, how would we go about checking the distance as you mentioned? Forgive me I'm new at this. Maybe your comment was towards other developers... 😅
Member

@JulienKaspar I would suggest also scale that value with interface scale factor too, that way we adapt better with high dpi situations.

@JulienKaspar I would suggest also scale that value with interface scale factor too, that way we adapt better with high dpi situations.
Member

@Claudio-Setti Yes sorry. That comment was more towards the developers on how we should approach a fix.
@ChengduLittleA Taking dpi into account is a good note!

@Claudio-Setti Yes sorry. That comment was more towards the developers on how we should approach a fix. @ChengduLittleA Taking dpi into account is a good note!

I opened a problem #112194 a while ago. I just tested with 3.2 and it didn't happen. Version 3.3 seems to be have a bit of this problem but a lot less severe. So it seems to be also something that happens after 3.2.

I opened a problem https://projects.blender.org/blender/blender/issues/112194 a while ago. I just tested with 3.2 and it didn't happen. Version 3.3 seems to be have a bit of this problem but a lot less severe. So it seems to be also something that happens after 3.2.

After a thorough test on the clay strips in version 3.6.4, the same erratic behaviours present in previous versions of 3.6 persist. Additionally, I observed a noticeable delay when using the control-z command to undo a stroke.

After a thorough test on the clay strips in version 3.6.4, the same erratic behaviours present in previous versions of 3.6 persist. Additionally, I observed a noticeable delay when using the control-z command to undo a stroke.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#110794
No description provided.