Color attributes in sculpt mode not showing in instance objects #101150
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#101150
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-5.15.0-47-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: GeForce GTX 670MX/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 418.226.00
Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-09-16 20:05, hash:
e108d67635
Worked: (newest version of Blender that worked as expected)
Short description of error
When sculpting an object its instance reflect the changes after the stroke, but not with color attributes, you have to go out of sculpt mode to see the color attributes.
Exact steps for others to reproduce the error
Grabación de pantalla desde 17-09-22 16:08:53.webm
One funny thing is that if you give the original object a mirror modifier, the changes to the instance are in real-time, not after the stroke, both for sculpt and for paint. But not when you sculpt or paint in the one without the modifier.
Grabación de pantalla desde 17-09-22 16:22:16.webm
Added subscriber: @TonatiuhdeSanJulian
Just to clarify I don't think that the expected behavior is real-time, because it start lagging a lot with HighPoly objects, The prefer behavior for me is to actualize the instance or the mirror object immediately after the stroke, like normal sculpt with instances, that way there is no lag while sculpting, only in the visual representation, but just wile the stroke is action.
I just discover that the smear brush and the color filters works as expected, see the video:
Grabación de pantalla desde 17-09-22 16:36:56.webm
Added subscribers: @JosephEagar, @JulienKaspar
Changed status from 'Needs Triage' to: 'Confirmed'
I can confirm this bug.
This seems to be the case ever since the feature was released in 3.2.
@JosephEagar Can you take a look at this?
The ideal behaviour here would be that after each stroke, the instanced obejcts will update, even with modifiers.
But addressing the real time updates when modifiers are involved are likely a general issue in sculpt mode. This would likely be tackeld separately.
After several hours of debugging, I fixed the crashes this situation can cause but, alas, I don't think I can fix the inconsistency in behavior. Whether the update happens in real time or after the stroke (or at all) is surprisingly complicated.
For example, dupli instances (e.g. instancing through collections) update in real time. But not data instances (alt-D). Unless the original object has a modifier, is not multires and is not in Dyntopo mode. Then it will be realtime. If Dyntopo is enabled dupli instances will still be updated, but data ones will not.
@JosephEagar the most problematic is the mirror or the array modifier been real-time, because it makes sculpt mode really slow with Highres meshes. And of course changes not showing at all.
As the title states, it makes sense to focus in this report on the following bug: Objects with linked object data do not update after a painting stroke.
The moment a regular sculpting operation or stroke is executed, the objects do update though. So this is not a severe issue.
Other issues, like that instances or objects with modifiers are updating in realtime and causing slow performance seems to be much more of a known issue that has been in Blender for many years. It's unrelated to this bug.
It's ok if this is too complex to fix for now. There are multiple issues like this. about a lack of support for sculpt mode with modifiers.
We can't do anything about the array modifier. Mirror modifiers are another matter though we don't have time for it at the moment (there are a number of things we need to fix with how sculpt mode works with mirror modifiers).
Anyway, the inconsistency in behavior has to do with what GPU meshes happen to be compatible with what the draw manager wants. If the fast internal sculpt draw mesh happens to be compatible with what the draw manger wants for an instance it will use it, otherwise it will use a normal draw mesh generated from the base mesh.