Cubism SDK 5 R5 URP - TransparentPicking material remains assigned after initialization

Ellice

Environment

• Cubism SDK for Unity: 5 R5 (official unitypackage)
• Unity: 6000.0.46f1 and 6000.0.71f1
• Render Pipeline: Universal Render Pipeline (URP)
• Operating System: Windows 11 x64
• Brand new Unity project
• Official Cubism sample models

Steps to reproduce

1. Create a new Unity 6000 URP project.
2. Import the official Cubism SDK for Unity 5 R5.
3. Import an official Cubism sample model.
4. Drag the generated prefab into the scene.
5. Enter Play Mode.

Expected result

The Cubism model should render normally in both the Scene View and the Game View.

Actual result

The model is invisible in both the Scene View and the Game View. We can see that the Mesh Renderer's material has changed to "TransParentPicking".

Investigation

I traced the issue into CubismRenderer.SetupPickingMaterial().
During initialization, the following line is executed:

_meshRenderer.sharedMaterial = CubismBuiltinMaterials.TransparentPicking;

After that, ApplyMainTexture() is called, but it only updates the MaterialPropertyBlock.

While investigating the SDK source, I found that:

• _drawMaterial is assigned inside SetupPickingMaterial().
• I could not find any references to CubismRenderer.Material in the SDK source.
• I could not find where MeshRenderer.sharedMaterial is restored to the original rendering material.

As a temporary experiment, I commented out the following line:

_meshRenderer.sharedMaterial = CubismBuiltinMaterials.TransparentPicking;

After doing so, the model renders correctly.

Additional information

• The mesh is generated correctly.
• The textures are loaded correctly.
• The Cubism Core native plugin is loaded correctly.
• The same issue occurs with multiple official sample models.
• I also replaced all C# source files with the latest GitHub version (keeping the official Core DLL). The issue still occurs.
• The issue reproduces on both Unity 6000.0.46f1 and Unity 6000.0.71f1.

Question

Is this the expected behavior?

If so, could you explain where the original rendering material is expected to be restored?

If not, could this be a compatibility issue with Unity 6000 and URP?

Thanks for your reading, and I apologize for any errors that may have occurred during the tracking process.