Dyntopo resolution don't work when using anchored or drag dot stroke methods #58389

Closed
opened 2018-12-01 02:46:18 +01:00 by Juan Romero · 8 comments

While in sculpt mode, dyntopo activated, resolution works for any given refine method but when anchored or drag dot stroke methods are used, the brush resolution stops working and reamains at a fixed resolution even though the resolution value is changed. It seems as if dyntopo is deactivated when chosing anchored or drag dot stroke methods

While in sculpt mode, dyntopo activated, resolution works for any given refine method but when anchored or drag dot stroke methods are used, the brush resolution stops working and reamains at a fixed resolution even though the resolution value is changed. It seems as if dyntopo is deactivated when chosing anchored or drag dot stroke methods
Author

Added subscriber: @JuanRomero

Added subscriber: @JuanRomero
Juan Romero changed title from Dyntopo resolution don't work when using a texture brush to Dyntopo resolution don't work when using anchored or drag dot stroke methods 2018-12-01 02:56:31 +01:00

Added subscriber: @ZedDB

Added subscriber: @ZedDB

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sebastian Parborg self-assigned this 2019-01-04 13:43:32 +01:00

Those two methods can not easily be implemented with dynamic topology. We would have to tessellate the mesh and undo the tessellation right after if the user moves the position of the stroke.
Dynatopo were not built for these kinds of situations. So this is more of a feature request: https://blender.community/c/rightclickselect/

Those two methods can not easily be implemented with dynamic topology. We would have to tessellate the mesh and undo the tessellation right after if the user moves the position of the stroke. Dynatopo were not built for these kinds of situations. So this is more of a feature request: https://blender.community/c/rightclickselect/
Author

Fine, then. A bit of a shame because those are very useful methods for esculpting with alphas. Anyway, wouldn't it be better if at least they had a small warning or text beside stating "no dyntopo stroke" or something?

Fine, then. A bit of a shame because those are very useful methods for esculpting with alphas. Anyway, wouldn't it be better if at least they had a small warning or text beside stating "no dyntopo stroke" or something?

I'm not saying that it absolutely couldn't be implemented, it's just that this is not really a bug but a limitation in how dynatopo works.
(So it is working as intended, just not in the way a user would want it to)

Because of this, fixing it will not be a priority during the stabilization of the 2.8 beta.

So my suggestion to you:

  1. Create a nice proposal of features that you want in blender sculpt mode over at rightclickselect
  2. Iterate a few times with the community and drum up support for your requested features
  3. When the proposal has gained enough support a developer will have a nice list of what to improve/implement

I think this is the best way for you to get what you want. Unless you want to program it in yourself.

I'm not saying that it absolutely couldn't be implemented, it's just that this is not really a bug but a limitation in how dynatopo works. (So it is working as intended, just not in the way a user would want it to) Because of this, fixing it will not be a priority during the stabilization of the 2.8 beta. So my suggestion to you: 1. Create a nice proposal of features that you want in blender sculpt mode over at rightclickselect 2. Iterate a few times with the community and drum up support for your requested features 3. When the proposal has gained enough support a developer will have a nice list of what to improve/implement I think this is the best way for you to get what you want. Unless you want to program it in yourself.

Added subscriber: @jemian

Added subscriber: @jemian

That's a real bad , because it's a very easy way to create terrain. If the anchored point doesn't create a detail size dyntopo under the brush I don't see what it's good for.

That's a real bad , because it's a very easy way to create terrain. If the anchored point doesn't create a detail size dyntopo under the brush I don't see what it's good for.
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#58389
No description provided.