Overwriting asset library with newer version does not work #113397

New Issue

LOIC BRAMOULLE · 2023-10-07T19:07:46+02:00

LOIC BRAMOULLE commented

2023-10-07 19:07:46 +02:00

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23

Blender Version
Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-06 20:19, hash: c8c6f62cf3a3
Worked: (newest version of Blender that worked as expected)

Short description of error
If you update a library, new assets do not appear, and renamed ones are corrupted & crash blender on use.

Exact steps for others to reproduce the error

Have a library
update this library on disk (extract a zip, replaces the blend & cat & texture files making this library)
now in blender, new assets do not appear, and the ones that had their named changed in the new version are corrupted, no thumbnail, and crash blender on usage.

What is crazy is that this bug persists even if deleting the V1 library from both blender paths, and disk, extracting the V2, installing it again in Path. So blender keeps in memory the V1 library and corrupts the V2, even if all trace has been removed between both instals.
The only workaround to update a library seems to be to extract the V2 at a different location on disk : o

I'm the creator of Smartify Nodes that's currently the best selling product on blender market, and in a bit of panic as I did expect an asset library to just update without keeping this strange memory of the previous files, that corrupts the new blend file.

Here is two zip files I prepared with simple assets, that allows to reproduce the bug. as described above, instal V1 by uziping and adding fodler to Path, check library, then overrite on disk by extracting V2: library corrupted.

So the source file for V2 looks correct like this:

But once updated over the V1 that doesn't have the purple, and have red not yet renamed to orange, the V2 is corrupted like this:

Many thanks for any help, I'm not sure what's the best workaround for right now, as telling customers to delete previous verison and instal in another location seems very confusing.

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23 **Blender Version** Broken: version: 3.6.3 Release Candidate, branch: blender-v3.6-release, commit date: 2023-09-06 20:19, hash: `c8c6f62cf3a3` Worked: (newest version of Blender that worked as expected) **Short description of error** If you update a library, new assets do not appear, and renamed ones are corrupted & crash blender on use. **Exact steps for others to reproduce the error** - Have a library - update this library on disk (extract a zip, replaces the blend & cat & texture files making this library) - now in blender, new assets do not appear, and the ones that had their named changed in the new version are corrupted, no thumbnail, and crash blender on usage. What is crazy is that this bug persists even if deleting the V1 library from both blender paths, and disk, extracting the V2, installing it again in Path. So blender keeps in memory the V1 library and corrupts the V2, even if all trace has been removed between both instals. The only workaround to update a library seems to be to extract the V2 **at a different location on disk** : o I'm the creator of Smartify Nodes that's currently the best selling product on blender market, and in a bit of panic as I did expect an asset library to just update without keeping this strange memory of the previous files, that corrupts the new blend file. Here is two zip files I prepared with simple assets, that allows to reproduce the bug. as described above, instal V1 by uziping and adding fodler to Path, check library, then overrite on disk by extracting V2: library corrupted. So the source file for V2 looks correct like this: ![image](/attachments/5c726a10-571d-49e6-bb68-0d1b7eda3825) But once updated over the V1 that doesn't have the purple, and have red not yet renamed to orange, the V2 is corrupted like this: ![image](/attachments/edaa5c3e-2c0e-435b-8f1b-f51fd57b1612) Many thanks for any help, I'm not sure what's the best workaround for right now, as telling customers to delete previous verison and instal in another location seems very confusing.

ASSET LIB BUG_v1.zip

771 KiB

ASSET LIB BUG_v2.zip

884 KiB

image.png

148 KiB

image.png

86 KiB

LOIC BRAMOULLE added the

labels 2023-10-07 19:07:47 +02:00

LOIC BRAMOULLE commented

2023-10-07 20:09:53 +02:00

So the only/best workaround I found at the moment, was adding the version number to the library folder. so then it's zipped, shared, unzipped, and instead of overwritting the previous version (and corrupting it) it unzzips to an other folder.
Then in blender it's just editign the Path to have this version number (the new fodler) and that doesn't create the bug, as it's a different fodler.
It's one more step to update, but at least it adds this version number visible in browser for the user to know which one is installed currently, and be able to swap to previous version if ever useful.

So the only/best workaround I found at the moment, was adding the version number to the library folder. so then it's zipped, shared, unzipped, and instead of overwritting the previous version (and corrupting it) it unzzips to an other folder. Then in blender it's just editign the Path to have this version number (the new fodler) and that doesn't create the bug, as it's a different fodler. It's one more step to update, but at least it adds this version number visible in browser for the user to know which one is installed currently, and be able to swap to previous version if ever useful.

Iliya Katushenock added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Overwriting asset library with newer version does not work #113397