Dynamic paint sub-steps samples only brush #102122

Closed
opened 2022-10-28 14:07:41 +02:00 by Damian · 7 comments

Simplified Report

  • An elongated subdivided plane act as a displacement dynamic paint canvas with the default settings.
  • An icosphere acts as a dynamic paint brush with the default settings.
  • The canvas is animated and the brush is fixed.
  • Play the animation and notice how sampling is too low, so only a few spots are painted.
  • Increase the sub-steps to any high number.
  • Notice that the sampling frequency doesn't change.

dynamicPaintSubSteps.blend

Original Report

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

Blender Version
Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: 0759f671ce
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

When adding more substeps to Dynamic paint, it seems it samples only Brush when it is animated, but does not take Canvas movement into account, so, instead of getting more smooth curve, I get a dashed line in my case.
image.png
in my scene, the disc is the Canvas and it is rotating. The brush is attached to the moving bar. Basically, this is a curve drawing machine, so the result should be a smooth continuous line.
the scene is also attached.
curve drawing.blend

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

## Simplified Report - An elongated subdivided plane act as a displacement dynamic paint canvas with the default settings. - An icosphere acts as a dynamic paint brush with the default settings. - The canvas is animated and the brush is fixed. - Play the animation and notice how sampling is too low, so only a few spots are painted. - Increase the sub-steps to any high number. - Notice that the sampling frequency doesn't change. [dynamicPaintSubSteps.blend](https://archive.blender.org/developer/F13789913/dynamicPaintSubSteps.blend) ## Original Report **System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 526.47 **Blender Version** Broken: version: 3.3.0, branch: master, commit date: 2022-09-06 15:39, hash: `0759f671ce` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] When adding more substeps to Dynamic paint, it seems it samples only Brush when it is animated, but does not take Canvas movement into account, so, instead of getting more smooth curve, I get a dashed line in my case. ![image.png](https://archive.blender.org/developer/F13789709/image.png) in my scene, the disc is the Canvas and it is rotating. The brush is attached to the moving bar. Basically, this is a curve drawing machine, so the result should be a smooth continuous line. the scene is also attached. [curve drawing.blend](https://archive.blender.org/developer/F13789754/curve_drawing.blend) **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]
Author

Added subscriber: @DamianWinnichenko

Added subscriber: @DamianWinnichenko
Member

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

Changed status from 'Needs Triage' to: 'Confirmed'
Omar Emara changed title from Dynamic paint substeps samples only brush to Dynamic paint sub-steps samples only brush 2022-10-28 14:39:13 +02:00
Author

I know, this usually should be avoided, but I want to add another little issue here.

The amount of sub-steps in Dynamic paint is hardcoded by a maximum of 20. Which could be not enough for some fast-moving objects like debris, water splashes, etc.
I would suggest increasing the hard limit to 128-ish while keeping the soft limit around 10-ish we have right now.

I know, this usually should be avoided, but I want to add another little issue here. The amount of sub-steps in Dynamic paint is hardcoded by a maximum of 20. Which could be not enough for some fast-moving objects like debris, water splashes, etc. I would suggest increasing the hard limit to 128-ish while keeping the soft limit around 10-ish we have right now.
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

Regarding substeps of brush vs. canvas:

In #84524#1096663, @lichtwerk wrote:
So after a bit of digging, this really seems like designed that way.
In code, only the brush objects are updated specifically for each subframe.

After all that digging, I found that this has been reported before, see #48797 (Dynamic Paint Sub-Steps not working when Canvas is moving).
Turns out, this was not considered a bug at that time either.

Not saying that this could not be supported, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior.
Afraid we have to close this as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Will merge into #48797

Regarding substeps of brush vs. canvas: > In #84524#1096663, @lichtwerk wrote: > So after a bit of digging, this really seems like designed that way. > In code, only the brush objects are updated specifically for each subframe. > > After all that digging, I found that this has been reported before, see #48797 (Dynamic Paint Sub-Steps not working when Canvas is moving). > Turns out, this was not considered a bug at that time either. > > Not saying that this could not be supported, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. > Afraid we have to close this as this bug tracker is only for bugs and errors. > > For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests > For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug Will merge into #48797
Member

Closed as duplicate of #48797

Closed as duplicate of #48797
Author

In #102122#1439608, @lichtwerk wrote:
Regarding substeps of brush vs. canvas:

In #84524#1096663, @lichtwerk wrote:
So after a bit of digging, this really seems like designed that way.
In code, only the brush objects are updated specifically for each subframe.

After all that digging, I found that this has been reported before, see #48797 (Dynamic Paint Sub-Steps not working when Canvas is moving).
Turns out, this was not considered a bug at that time either.

Not saying that this could not be supported, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior.
Afraid we have to close this as this bug tracker is only for bugs and errors.

For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Will merge into #48797

Okay then. thanks for the investigation!
For me it looked like a bug... anyway, I think this limitation must be stressed in the documentation as well to avoid frustration and misunderstanding...

Thanks again!

> In #102122#1439608, @lichtwerk wrote: > Regarding substeps of brush vs. canvas: > >> In #84524#1096663, @lichtwerk wrote: >> So after a bit of digging, this really seems like designed that way. >> In code, only the brush objects are updated specifically for each subframe. >> >> After all that digging, I found that this has been reported before, see #48797 (Dynamic Paint Sub-Steps not working when Canvas is moving). >> Turns out, this was not considered a bug at that time either. >> >> Not saying that this could not be supported, but the issue reported here is a request for modified/improved behavior and not a bug in current behavior. >> Afraid we have to close this as this bug tracker is only for bugs and errors. >> >> For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests >> For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug > > Will merge into #48797 Okay then. thanks for the investigation! For me it looked like a bug... anyway, I think this limitation must be stressed in the documentation as well to avoid frustration and misunderstanding... Thanks again!
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
3 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#102122
No description provided.