Object Group Reorder #40741

Closed
opened 2014-06-21 12:19:12 +02:00 by Philip Holzmann · 8 comments

System Information
Windows 7 64bit, 16 GB RAM, AMD 8 Cores 3.11 GHz, AMD Radeon HD 6450

Blender Version
Broken: (2.70a f93bc76)

Short description of error
In a hair particle system which renders a group, the objects are sometimes reordered after saving and reloading.

Exact steps for others to reproduce the error
test.blend
In the attached file in camera view, the big 'L' should be on the left side of the big 'R'. That's the way the file was saved.
But after reloading the file, they are sometimes swapped.

To correct the order, remove both little letters from the group, and then first add the little 'R' to the group and then the little 'L'. But after saving, the order is wrong again.

**System Information** Windows 7 64bit, 16 GB RAM, AMD 8 Cores 3.11 GHz, AMD Radeon HD 6450 **Blender Version** Broken: (2.70a f93bc76) **Short description of error** In a hair particle system which renders a group, the objects are sometimes reordered after saving and reloading. **Exact steps for others to reproduce the error** [test.blend](https://archive.blender.org/developer/F95124/test.blend) In the attached file in camera view, the big 'L' should be on the left side of the big 'R'. That's the way the file was saved. But after reloading the file, they are sometimes swapped. To correct the order, remove both little letters from the group, and then first add the little 'R' to the group and then the little 'L'. But after saving, the order is wrong again.

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @Foaly

Added subscriber: @Foaly
Lukas Tönne was assigned by Sergey Sharybin 2014-06-27 10:54:26 +02:00

Added subscribers: @LukasTonne, @Sergey

Added subscribers: @LukasTonne, @Sergey

@LukasTonne, is it something you're familiar with?

@LukasTonne, is it something you're familiar with?
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Member

This is a known limitation of the particle code: It uses objects from the group randomly, but in order to make that repeatable it must expect the group to have some fixed ordering in the first place. This is not well defined, rather than lists groups are conceptually sets, without a defined order (only our use of ListBase structs doesn't enforce the distinction). The dependency graph or other code may reshuffle groups.

A workaround for the problem is to enable the Use Count option, which defines its own ordering instead of relying on the group. This is the only feasible implementation of such group object selection anyway, the random group element picking just doesn't allow repeatable results.

This is a known limitation of the particle code: It uses objects from the group randomly, but in order to make that repeatable it must expect the group to have some fixed ordering in the first place. This is not well defined, rather than *lists* groups are conceptually *sets*, without a defined order (only our use of `ListBase` structs doesn't enforce the distinction). The dependency graph or other code may reshuffle groups. A workaround for the problem is to enable the **Use Count** option, which defines its own ordering instead of relying on the group. This is the only feasible implementation of such group object selection anyway, the random group element picking just doesn't allow repeatable results.

Thank you!
The use count option works. Now I don't have to recreate the groups every time I open my scene.

Thank you! The use count option works. Now I don't have to recreate the groups every time I open my scene.

Removed subscriber: @Foaly

Removed subscriber: @Foaly
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#40741
No description provided.