Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[glTF] Wrong object mesh when two objects have a same name without an import hint #92837

Closed
passivestar opened this issue Jun 6, 2024 · 2 comments · Fixed by #94020
Closed

Comments

@passivestar
Copy link
Contributor

Tested versions

v4.3.beta1.official [a4f2ea9]

System information

Godot v4.3.beta1 - macOS 14.4.1 - Vulkan (Forward+) - integrated Apple M1 Max - Apple M1 Max (10 Threads)

Issue description

Having two objects named Cube and Cube-col breaks the import:

Screen.Recording.mp4

Steps to reproduce

  1. Make a blend file with a Cube in it
  2. Export gltf and add it to scene in godot
  3. Change the cube geometry, and add a -col hint to it to make it Cube-col. Export and reimport in godot
  4. Add a new cube. It will get a name Cube
  5. When you reimport the scene in godot you'll see that both cubes are using the mesh of the first cube

Minimal reproduction project (MRP)

MRP_gltf_duplicate.zip

@AThousandShips

This comment was marked as outdated.

@AThousandShips AThousandShips closed this as not planned Won't fix, can't repro, duplicate, stale Jun 6, 2024
@passivestar
Copy link
Contributor Author

@AThousandShips In #72483 @rburing says that -col suffix specifically isn't removed if it would result in a name collision which I can confirm:

image

So it seems like this is a separate issue because this one isn't about a name collision but about broken import despite there not being any name collision after import is done (And also #72483 doesn't have any mention of wrong meshes being displayed in the viewport)

Also more info:

I just noticed that restarting the editor fixes this issue (even though clicking "Reimport" on gltf doesn't), which makes the MRP that I attached useless, you can only reproduce this by following the steps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants