material remapping work properly only the first time #48740

Closed
opened 2016-06-26 12:12:41 +02:00 by mathieu menuet · 11 comments

System Information
Win 7 x64

Blender Version
Broken: 2a69b09

Short description of error
Remapping an object's material work the first time, but switching back to original one won't work. It may change other object's material by the way.

Exact steps for others to reproduce the error
red.blend
green.blend
Download both files in one directory. Open green.blend and remap red material (linked) in outliner to green material. Red object becomes green, correct.
Now remap again this material to green, nothing happens. Sometime, the green object becomes red, but the red object will stay green forever.

**System Information** Win 7 x64 **Blender Version** Broken: 2a69b09 **Short description of error** Remapping an object's material work the first time, but switching back to original one won't work. It may change other object's material by the way. **Exact steps for others to reproduce the error** [red.blend](https://archive.blender.org/developer/F318698/red.blend) [green.blend](https://archive.blender.org/developer/F318699/green.blend) Download both files in one directory. Open green.blend and remap red material (linked) in outliner to green material. Red object becomes green, correct. Now remap again this material to green, nothing happens. Sometime, the green object becomes red, but the red object will stay green forever.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @bliblubli

Added subscriber: @bliblubli
Author

Trying to solve the problem with undo (instead of remapping again the other way) creates a lot of users (18 in my case) and make the object black without any material.

Trying to solve the problem with undo (instead of remapping again the other way) creates a lot of users (18 in my case) and make the object black without any material.

Added subscriber: @mont29

Added subscriber: @mont29
Bastien Montagne self-assigned this 2016-06-26 12:49:30 +02:00

Hrrrmmm… remapping linked data… not even sure I checked that use case! :P

Hrrrmmm… remapping linked data… not even sure I checked that use case! :P

Yeah, this should not be allowed, you cannot remap linked data usages that way, it's calling for problems (linked data is assumed 'frozen' and non-editable). Will add checks in code to prevent this to happen!

Yeah, this should not be allowed, you cannot remap linked data usages that way, it's calling for problems (linked data is assumed 'frozen' and non-editable). Will add checks in code to prevent this to happen!
Author

It's one solution. Maybe a better one for user would be to ask if he wants to edit the original file. Then changes could be saved to original data. Now that you have implemented a way to save specific datablocks to another .blend in the API, it should be doable?

It's one solution. Maybe a better one for user would be to ask if he wants to edit the original file. Then changes could be saved to original data. Now that you have implemented a way to save specific datablocks to another .blend in the API, it should be doable?

Would rather not do that - at all. Would make library handling even more complicated (and believe me, it’s already rather hairy code).

Library editing should be featured separately, as an addon e.g., which would simply launch another blender session with relevant library file etc.

Would rather not do that - at all. Would make library handling even more complicated (and believe me, it’s already rather hairy code). Library editing should be featured separately, as an addon e.g., which would simply launch another blender session with relevant library file etc.

This issue was referenced by e2c7ee7733

This issue was referenced by e2c7ee773311734450a229051673fbfea61b641a

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Author

Thanks for the fix. Problem with addons is that they are most of the time not so well maintained/programmed on the long run. They also tend to become slow when managing big amount of datas. And I'm pretty sure we will arrive to 3-4 addons doing the same job, none of them being fully featured
Trying to implement a custom addon as you said, I used the new operator to write datablock to an external .blend. It seems to erase everything else, to only keep the saved datablock. Am I doing something wrong or are you going to add the possibility to append later?
Regards

Thanks for the fix. Problem with addons is that they are most of the time not so well maintained/programmed on the long run. They also tend to become slow when managing big amount of datas. And I'm pretty sure we will arrive to 3-4 addons doing the same job, none of them being fully featured Trying to implement a custom addon as you said, I used the new operator to write datablock to an external .blend. It seems to erase everything else, to only keep the saved datablock. Am I doing something wrong or are you going to add the possibility to append later? Regards
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#48740
No description provided.