linked library object loses particle settings #45658

New Issue

jim ww smith · 2015-08-03T00:35:37+02:00

jim ww smith commented

2015-08-03 00:35:37 +02:00

System Information
Operating system and graphics card
OSX 10.10.4 - NVIDIA GeForce GTX 680 2048 MB

Blender Version
Broken: ( 2.75a c27589e )
Worked: ( 2.74 )

Short description of error
when opening a file with a 'local' linked library object, particle settings are lost. error message pops up identifying missing library settings.

Exact steps for others to reproduce the error
create object(character) with particle settings, save file.

create new file, link scene file with object(character), link object(character) to local scene. make linked library object 'local' in object properties. save file. close file.

re-open scene file with linked object(character). warning that particle settings are missing. linked library object(character) has no particle settings.

this is going to cause serious problems. i have a character with multiple particle systems, who will appear in multiple scenes. re-importing the character mesh every time i open a file defeats the purpose of linked libraries. character needs to be local to apply armature actions within local scene file. i have tested that this process works with previous versions ( 2.74 )

**System Information** Operating system and graphics card OSX 10.10.4 - NVIDIA GeForce GTX 680 2048 MB **Blender Version** Broken: ( 2.75a c27589e ) Worked: ( 2.74 ) **Short description of error** when opening a file with a 'local' linked library object, particle settings are lost. error message pops up identifying missing library settings. **Exact steps for others to reproduce the error** create object(character) with particle settings, save file. create new file, link scene file with object(character), link object(character) to local scene. make linked library object 'local' in object properties. save file. close file. re-open scene file with linked object(character). warning that particle settings are missing. linked library object(character) has no particle settings. this is going to cause serious problems. i have a character with multiple particle systems, who will appear in multiple scenes. re-importing the character mesh every time i open a file defeats the purpose of linked libraries. character needs to be local to apply armature actions within local scene file. i have tested that this process works with previous versions ( 2.74 )

jim ww smith commented

2015-08-03 00:35:37 +02:00

Changed status to: 'Open'

jim ww smith commented

2015-08-03 00:35:37 +02:00

Added subscriber: @JimwwSmith

perfection cat commented

2015-08-03 01:50:23 +02:00

Added subscriber: @sindra1961

perfection cat commented

2015-08-03 01:50:23 +02:00

I cannot reproduce this here.
Did you test it in the latest buildbot build(Download Latest Builds )?
version 2.75 (sub 3), branch b'master', commit date b'2015-08-01' b'02:37', hash b'49f8832', b'Release'

I cannot reproduce this here. Did you test it in the latest buildbot build([Download Latest Builds ](https://builder.blender.org/download/))? version 2.75 (sub 3), branch b'master', commit date b'2015-08-01' b'02:37', hash b'49f8832', b'Release'

jim ww smith commented

2015-08-03 08:55:40 +02:00

tried latest build, still getting the same result. i did not see any other reports of this issue, so i saw no reason to assume it had been fixed. it does work under 2.74, but i am concerned about regression issues in re-saving new files with old versions.

perfection cat commented

2015-08-03 09:25:15 +02:00

The method that I confirmed may be wrong.
original.blend is an original file.
MakeLocal.blend is the result that tried this.

It is the procedure that I confirmed.
1.Run Blender.
2.Link the scene named OriginalScene from original.blend.
3.Choose local scene.
4.Link an object named originalCube from original.blend.
5.Carry out Make Local(All) in originalCube which linked to local Scene.
6.Save this in blend file, and load it again.
original.blend
MakeLocal.blend

The method that I confirmed may be wrong. original.blend is an original file. MakeLocal.blend is the result that tried this. It is the procedure that I confirmed. 1.Run Blender. 2.Link the scene named OriginalScene from original.blend. 3.Choose local scene. 4.Link an object named originalCube from original.blend. 5.Carry out Make Local(All) in originalCube which linked to local Scene. 6.Save this in blend file, and load it again. [original.blend](https://archive.blender.org/developer/F217904/original.blend) [MakeLocal.blend](https://archive.blender.org/developer/F217906/MakeLocal.blend)

jim ww smith commented

2015-08-03 23:21:24 +02:00

that description appears to be correct. i think the language of linked libraries is causing some confusion, so i will describe the use scenario. i have created a character in a file, with particle settings for multiple hair systems. i then create another file for an environment, and import the character as a linked scene file. from that scene file, i link the character to the environment scene. when i reload the environment file, the particle settings on the linked character object are lost.

Sergey Sharybin commented

2015-08-04 11:49:13 +02:00

Added subscribers: @ideasman42, @Sergey

Sergey Sharybin commented

2015-08-04 11:49:13 +02:00

I can not really reproduce the issue.

What exactly means "has no particle settings"?

@ideasman42, maybe you'll have more luck reproducing the issue?

I can not really reproduce the issue. What exactly means "has no particle settings"? @ideasman42, maybe you'll have more luck reproducing the issue?

jim ww smith commented

2015-08-04 20:00:54 +02:00

i get a LIB ERROR: Particle Settings: 'settings.name' missing from '/Path/To/Scene/File.blend', parent ''

this error is repeated for each of the particle settings.

this is on a character with multiple particle settings, all of which are now absent. i tested on a simple box with particle settings, imported into a simple scene, with the same result. perhaps it is a platform issue? the process is not new, i have been using it through multiple iterations of Blender. i considered maybe that it was an issue with corrupt preferences, as i did recently load my user preferences from my previous version, but i just reverted to default preferences, and the problem persists.

i have included the two sample files i created which exhibit this problem:

error test_01.blend

error test_import_01.blend

i get a LIB ERROR: Particle Settings: 'settings.name' missing from '/Path/To/Scene/File.blend', parent '<direct>' this error is repeated for each of the particle settings. this is on a character with multiple particle settings, all of which are now absent. i tested on a simple box with particle settings, imported into a simple scene, with the same result. perhaps it is a platform issue? the process is not new, i have been using it through multiple iterations of Blender. i considered maybe that it was an issue with corrupt preferences, as i did recently load my user preferences from my previous version, but i just reverted to default preferences, and the problem persists. i have included the two sample files i created which exhibit this problem: [error test_01.blend](https://archive.blender.org/developer/F219416/error_test_01.blend) [error test_import_01.blend](https://archive.blender.org/developer/F219417/error_test_import_01.blend)

perfection cat commented

2015-08-05 01:13:04 +02:00

You should have told object linked to local scene to have carried out 'make local'.
However, the object in the file which you attached is linked.
Why is it that it is different from your explanation?

You should have told object linked to local scene to have carried out 'make local'. However, the object in the file which you attached is linked. Why is it that it is different from your explanation?

jim ww smith commented

2015-08-05 01:40:04 +02:00

sorry, i thought that was clear. it is in the short description of the error. i cannot perform any actions on an object that is not local, as any armature modifiers would not function. library groups with armature proxies may be my only option now, but have proved problematic in the past, which is why i link the scene file, and link objects directly. it may be that i am using a deprecated process, but it used to work.

perfection cat commented

2015-08-05 02:52:19 +02:00

Will you put the snapshot every procedure what kind of procedure you operated it in to become clear?
Please use error test_01.blend which you attached.
I was not able to reproduce this problem even if I used error test_01.blend which you attached.

Will you put the snapshot every procedure what kind of procedure you operated it in to become clear? Please use error test_01.blend which you attached. I was not able to reproduce this problem even if I used error test_01.blend which you attached.

Julian Eisel commented

2015-08-14 18:45:37 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2015-08-14 18:45:37 +02:00

Has anyone been able to reproduce now?

Bastien Montagne commented

2015-08-21 17:05:53 +02:00

Added subscribers: @LukasTonne, @mont29

Bastien Montagne commented

2015-08-21 17:05:53 +02:00

I can confirm the issue, it’s caused by new usage of GHash in blend readcode (a8f6d51e) - that ghash is only filled with idname of linkable datablocks.

Now, particle settings are not linkable currently (not sure I understand why?). So core of the issue is that, when making local a linked object, its particlesettings remain linked - this shall not happen.

We can fix this in several ways (non of those being mutually exclusive):

Add non-linkable idname to read ghash (simplest solution, restores previous behavior, but allows for wrong things);
Make ParticleSettings linkable (do not see why they are not?)
In any case, I think we should try to add some check when localizing some linked data, to also systematically localize non-linkable datablocks used by that data?

@ideasman42, @Sergey (and maybe @LukasTonne too), what do you say?

I can confirm the issue, it’s caused by new usage of GHash in blend readcode (a8f6d51e) - that ghash is only filled with idname of **linkable** datablocks. Now, particle settings **are not** linkable currently (not sure I understand why?). So core of the issue is that, when making local a linked object, its particlesettings remain linked - this shall not happen. We can fix this in several ways (non of those being mutually exclusive): * Add non-linkable idname to read ghash (simplest solution, restores previous behavior, but allows for wrong things); * Make ParticleSettings linkable (do not see why they are not?) * In any case, I think we should try to add some check when localizing some linked data, to also systematically localize non-linkable datablocks used by that data? @ideasman42, @Sergey (and maybe @LukasTonne too), what do you say?

Bastien Montagne self-assigned this 2015-08-21 17:06:06 +02:00

Lukas Tönne commented

2015-08-21 17:26:47 +02:00

Removed subscriber: @LukasTonne

blender-admin commented

2015-08-21 18:31:23 +02:00

This issue was referenced by 7d0b29be69

This issue was referenced by 7d0b29be69393fc08d30c0753c63999a880c4247

Bastien Montagne commented

2015-08-21 18:31:42 +02:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2015-08-21 18:31:42 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

linked library object loses particle settings #45658