Action assigned to an object is unlinked when performing user_remap() #104576

New Issue

Félix · 2023-02-10T15:58:28+01:00

Félix commented

2023-02-10 15:58:28 +01:00

System Information
Operating system: Linux-5.15.0-60-generic-x86_64-with-glibc2.35 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03

Blender Version
Broken: version: 3.3.3, branch: master, commit date: 2023-01-17 08:40, hash: rB8d94aeb604fa
Worked: (newest version of Blender that worked as expected)

Short description of error
Using user_remap() of an object with an linked action doesn't remap the action, it is simply unlinked.

Exact steps for others to reproduce the error

Open the given .blend
Run the command in the python console
Click on the 3D view to refresh the display
Select the cylinder
The action has been unassigned from the datablock

PS: The refresh of the different areas is not processed, like the 3D View or the outliner until we refresh them by click or display mode toggle. This is a minor issue but can be treated as well.

**System Information** Operating system: Linux-5.15.0-60-generic-x86_64-with-glibc2.35 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.161.03 **Blender Version** Broken: version: 3.3.3, branch: master, commit date: 2023-01-17 08:40, hash: `rB8d94aeb604fa` Worked: (newest version of Blender that worked as expected) **Short description of error** Using `user_remap()` of an object with an linked action doesn't remap the action, it is simply unlinked. **Exact steps for others to reproduce the error** - Open the given `.blend` - Run the command in the python console - Click on the 3D view to refresh the display - Select the cylinder - The action has been unassigned from the datablock PS: The refresh of the different areas is not processed, like the 3D View or the outliner until we refresh them by click or display mode toggle. This is a minor issue but can be treated as well.

User_remap_action.blend

100 KiB

Félix added the

labels 2023-02-10 15:58:29 +01:00

Philipp Oeser commented

2023-02-13 14:42:14 +01:00

Since the usages of the object are remapped, I would actually think this is expected behavior?

So, whereever the former object ID was used (collection membership, targets in modifiers/constraints, ...), now the new object is used. That does not mean though that the action gets "transferred" (since the action is still tied to the old object datablock)? You simply get, whichever action was tied to the new object beforehand.

Is there anything pointing to the behavior you would like to see in the documentation? Or is it behaving like that for any other datablocks?

@mont29 : I dont think this is what one should expect from user_remap()?

Since the usages of the **object** are remapped, I would actually think this is expected behavior? So, whereever the former object ID was used (collection membership, targets in modifiers/constraints, ...), now the new object is used. That does not mean though that the action gets "transferred" (since the action is still tied to the old object datablock)? You simply get, whichever action was tied to the new object beforehand. Is there anything pointing to the behavior you would like to see in the documentation? Or is it behaving like that for any other datablocks? @mont29 : I dont think this is what one should expect from `user_remap()`?

Philipp Oeser added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-02-13 14:42:26 +01:00

Bastien Montagne commented

2023-02-13 15:33:05 +01:00

This is indeed expected behavior, the Action ID is used by the Object, not using the Object, so it is unaffected by the remapping of usages from old object to new one.

This is indeed expected behavior, the Action ID is **used** by the Object, not **using** the Object, so it is unaffected by the remapping of usages from old object to new one.

Bastien Montagne closed this issue

2023-02-13 15:33:07 +01:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2023-02-13 15:33:07 +01:00

Sign in to join this conversation.