CharacterBody3D textures not displayed with Godot_v4.6-dev3_win64

Dad3353

I've suddenly become aware that I can no longer see the Texture of my CharacterBody3D objects with this latest version Godot_v4.6-dev3_win64, only the Armature and Collision shapes. When I load the same Project into Godot_v4.6-dev2_win64, all is well, I see the Mesh Texture correctly. I've looked everywhere, it seems, to see if there's a check-box I've accidently ticked, but to no avail. How can I revert to the Godot_v4.6-dev2_win64, correct, display using Godot_v4.6-dev3_win64, please..? Screenshots of each, below; it's the same creature in the same Project. Thanks in advance...

Tomcat

Dad3353 When I load the same Project into Godot_v4.6-dev2_win64, all is well, I see the Mesh Texture correctly.

Check that the mesh in dev3 is attached to the rig, just like in dev2.

Animation: Remove default skeleton path in MeshInstance3D (GH-112267).

If relying on the default skeleton_path in some scenes, users should manually re-specify the parent node as the NodePath, or they can enable the animation/compatibility/default_parent_skeleton_in_mesh_instance_3d project setting to restore the pre-4.6 behavior.

https://godotengine.org/article/dev-snapshot-godot-4-6-dev-3/#and-more

Dad3353

Tomcat ...
Thanks for that. I've reverted to 4.51, Stable for now; if this behaviour is due to the use of dev3, which is what is implied here, it's a bug that needs fixing, as it's inconceivable to go through all the Meshes that need attention. I'll swap over to dev3 to confirm that it does, indeed, 'fix' the issue, but it would make dev3 unusable for me until a fix in dev4 or such. Back shortly...

Edit : I can confirm that assigning the appropriate Skeleton, either by choosing from a list (a bit long to refresh...) or by 'dragging' the Skeleton to the Assign box, does fix the issue. Does this need 'Reporting', and, if so, by whom, and how..?

Tomcat

Dad3353 Does this need 'Reporting', and, if so, by whom, and how..?

https://godotengine.org/article/dev-snapshot-godot-4-6-dev-3/#bug-reports

Bug reports

As a tester, we encourage you to open bug reports if you experience issues with this release. Please check the existing issues on GitHub first, using the search function with relevant keywords, to ensure that the bug you experience is not already known.

In particular, any change that would cause a regression in your projects is very important to report (e.g. if something that worked fine in previous 4.x releases, but no longer works in this snapshot).

Dad3353

Tomcat

Thanks. Bug Report #112655 created; I'll continue with 4.5.1 Stable until there's resolution, one way or another. It's not a deal-breaker, as long as future versions do not have this 'feature'. To be continued..?

Tomcat

Dad3353 It's not a deal-breaker, as long as future versions do not have this 'feature'. To be continued..?

The developers can either fix the behavior or offer a workaround. But since the dev version is not intended for serious work, they may do nothing. I moved my current work to dev3.

Tomcat

The behavior of dev4 is the same as that of dev3 — the same problems. It seems that the developers are not going to change anything.