Linking in a group with hair particles and force field doesn't affect the hair particles. #36300

Closed
opened 2013-07-27 04:25:53 +02:00 by Reynante Martinez · 5 comments

%%%--- Operating System, Graphics card ---

OS: Windows 8
Graphics card: Inter HD Graphics 4000

- Blender version with error, and version that worked ---

Blender version used: 2.68.0 revision 58386 and 2.68.1 revision 58611 (from builder.blender.org)
Blender version it worked on: none

- Short description of error ---

Linking a group with hair particles and force field doesn't affect the linked object which contains the particle system.
However, appending that group affects the particle system.

I have this current directory hierarchy as follows:

  • hair_with_forcefield/
  • hair_with_forcefield/blends
  • hair_with_forcefield/blends/scene
  • hair_with_forcefield/blends/props

/props contains the 'carpet.blend' file which has a plane with hair particles on it (both in a group called 'carpet'), affected by a single Force Field.

/scene contains the 'scene.blend' file where the 'carpet' group from 'carpet.blend' will be linked/appended into.

When doing a 'link' of the carpet group into the scene file, the hair particles doesn't seem to be affected by the force at all, given the force field is part of the linked group.

However, doing an 'append' of the carpet group into the scene file, the hair particles are affected by the force field. But already is a local group within the scene file and not a referenced/linked group.

Often, it is best to 'link' Groups/Objects for better organization, UI response, and doing appending often defeats this purpose.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---
  1. Create the directory structures mentioned above.
  2. Create a file named 'carpet.blend' and save it in /props.
  3. With the 'carpet.blend' file active, create a simple plane, add a hair particle system, then add a force field to affect the hair particles, and increase the force field's strength.
  4. Select the plane with the particle system and the force field, press CTRL G to create a group and name the group 'carpet'.
  5. Create another Blender file named 'scene.blend' and save it in /scene.
  6. Link the 'carpet' group from '/props/carpet.blend' by pressing CTRL ALT O (or going to File > Link), then browse for the carpet.blend file, then under Groups, select 'carpet'
  7. It is now noticeable that the appearance of the particle system is not similar to that of the expected appearance from the original 'carpet.blend' file.
  8. On step #6 though, if, instead of linking, we did an append, it will work fine.
  • Reyn%%%
%%%--- Operating System, Graphics card --- OS: Windows 8 Graphics card: Inter HD Graphics 4000 - Blender version with error, and version that worked --- Blender version used: 2.68.0 revision 58386 and 2.68.1 revision 58611 (from builder.blender.org) Blender version it worked on: none - Short description of error --- Linking a group with hair particles and force field doesn't affect the linked object which contains the particle system. However, appending that group affects the particle system. I have this current directory hierarchy as follows: - hair_with_forcefield/ - hair_with_forcefield/blends - hair_with_forcefield/blends/scene - hair_with_forcefield/blends/props /props contains the 'carpet.blend' file which has a plane with hair particles on it (both in a group called 'carpet'), affected by a single Force Field. /scene contains the 'scene.blend' file where the 'carpet' group from 'carpet.blend' will be linked/appended into. When doing a 'link' of the carpet group into the scene file, the hair particles doesn't seem to be affected by the force at all, given the force field is part of the linked group. However, doing an 'append' of the carpet group into the scene file, the hair particles are affected by the force field. But already is a local group within the scene file and not a referenced/linked group. Often, it is best to 'link' Groups/Objects for better organization, UI response, and doing appending often defeats this purpose. - Steps for others to reproduce the error (preferably based on attached .blend file) --- 1. Create the directory structures mentioned above. 2. Create a file named 'carpet.blend' and save it in /props. 3. With the 'carpet.blend' file active, create a simple plane, add a hair particle system, then add a force field to affect the hair particles, and increase the force field's strength. 4. Select the plane with the particle system and the force field, press CTRL G to create a group and name the group 'carpet'. 5. Create another Blender file named 'scene.blend' and save it in /scene. 6. Link the 'carpet' group from '/props/carpet.blend' by pressing CTRL ALT O (or going to File > Link), then browse for the carpet.blend file, then under Groups, select 'carpet' 7. It is now noticeable that the appearance of the particle system is not similar to that of the expected appearance from the original 'carpet.blend' file. 8. On step #6 though, if, instead of linking, we did an append, it will work fine. - Reyn%%%

Changed status to: 'Open'

Changed status to: 'Open'
Member

%%%This is sort-of a duplicate of #35264 (the cause is the same): Force fields do not work in group instances. When linking the group with carpet mesh/particles + force field it also loads the individual objects of the group (they are in bpy.data), but they don't get linked into the scene themselves (linking is an ambiguous term here, the first usage meaning a copy of the data from another file, the latter meaning a "object base" in the scene that actually places an object in that scene).

Linking (not necessarily appending) the "Field" object explicitly into the scene file solves the issue, although it's not an optimal solution. It may be possible to solve the problem in a general way by allowing force field in group instances, but i cannot promise anything yet. Will have to see if it can be done cleanly without major hacks.%%%

%%%This is sort-of a duplicate of #35264 (the cause is the same): Force fields do not work in group instances. When linking the group with carpet mesh/particles + force field it also loads the individual objects of the group (they are in bpy.data), but they don't get linked into the scene themselves (linking is an ambiguous term here, the first usage meaning a copy of the data from another file, the latter meaning a "object base" in the scene that actually places an object in that scene). Linking (not necessarily appending) the "Field" object explicitly into the scene file solves the issue, although it's not an optimal solution. It may be possible to solve the problem in a general way by allowing force field in group instances, but i cannot promise anything yet. Will have to see if it can be done cleanly without major hacks.%%%

%%%Thanks so much, Lukas.

  • Reyn%%%
%%%Thanks so much, Lukas. - Reyn%%%
Member

%%%Closing this as a ToDo
http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Collisions

It not really possible to fix with the way effectors (force fields and colliders) are used atm. Duplis are also primarily a visual feature, although i agree it would be helpful to support this at least in group instances.%%%

%%%Closing this as a ToDo http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Tools#Collisions It not really possible to fix with the way effectors (force fields and colliders) are used atm. Duplis are also primarily a visual feature, although i agree it would be helpful to support this at least in group instances.%%%
Member

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
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
2 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#36300
No description provided.