Improve UI for rigid body collections #69628
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#69628
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: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 431.70
Blender Version
Broken: version: 2.81 (sub 5), branch: master, commit date: 2019-09-03 16:04, hash:
b3b59e3b56
Worked: (optional)
Short description of error
There's an undocumented nonsensical collections section in the rigid body options (just below the sensitivity settings)
unless this is it from the manual? If so, the description is about as clear as mud :) :
"Collision Groups
Allows rigid body collisions allocate on different groups (maximum 20)."
See above for the initial report.
The interface needs to be improved, the idea of "Collections" here is misleading, perhaps rename back to groups/layers.
Better tooltips are also needed to better describe what they do.
Added subscriber: @3di
Added subscriber: @Blendify
Rigid bodies can be configured to only be affected by certain collections. This is very briefly mentioned here: https://docs.blender.org/manual/en/latest/physics/rigid_body/world.html
Within Blender, the limit needs to be removed and converted to using named collections.
Currently I am not sure how it works, maybe collections are mapped as they appear in alphabetical order? Or this might not work at all currently?
Added subscriber: @WilliamReynish
Indeed, we probably should just use regular Collections here.
Added subscriber: @dfelinto
@dfelinto I would like some of your feedback here, in one sense this a todo, however, it really is broken/confusing how the user is to address the collection by name when there is only a finite binary option.
This issue was referenced by blender/documentation@6167
Changed status from 'Confirmed' to: 'Resolved'
Should this be kept open as a UI todo task?
From what I see, this has already been resolved because it is "documented".
But other issues like:
Can be registered in other tasks as To Do.
There's an undocumented nonsensical collections section in the rigid body options (just below the sensitivity settings)to Improve UI for rigid body collectionsChanged status from 'Resolved' to: 'Confirmed'
Added subscriber: @pauanyu_blender