when importing .gltf with separate meshes, naming of imported meshes is unintuitive and different than what it was in < 3.4

[Rbetik]

Godot version

3.4

System information

Mac OS Mojave 10.14.4

Issue description

When importing .gltf with option 'import with separate objects ' resulting .mesh files are named as 'scene name' + default type from 3d editor instead of custom name as it was in previous versions

Steps to reproduce

1. import .gltf with separate objects
2. look at names of resulting .mesh files

Minimal reproduction project

weight_paint_import_bug

Edited: Url was incorrect.

[fire]

Can you give an example what you want it to be if you can change the name?

[Rbetik]

How it worked in 3.3.4 (and below ) seemed pretty intuitive, mesh name was the same as name of meshinstance class in .gltf scene, which is the same as name of object in 3d modeling tool.

[betalars]

Can replicate, went here to make this an issue myself.

I get, that this behavior might help when users do messy naming conventions, but it breaks your project, when you are using previously established proper naming conventions.

Also: I would add that the use legacy names checkbox seems to not be working right now. (I would assume this is intended so users may keep the naming convention as it previously worked)

Please fix this ASAP. I was just in the process of updating all my meshes and import files to use a good naming scheme so I can find everything and now I have to redo that entirely. Not looking forward to having to redo that process again.

[betalars]

Can you give an example what you want it to be if you can change the name?

I think the change is fine and I think I will adjust my naming convention to fit the new system (well I have to anyway, because I cannot wait for the fix). I just think the Checkbox should work so users can keep their existing conventions.

This being said: I think I have a slight preference for using the old scheme as default and have the checkbox be relabelled to something like "Include root file name"

[joeyeroq]

This change is not fine, the gltf file name should not be part (a prefix) of the mesh name. This change has unfortunately has spilled over to the godot 4 version and hopefully will be reversed.

[Calinou]

This is a regression from #49120 (which is a 3.x backport of a larger feature). See #45545 and #47074 for original PRs against the master branch that modify relevant files.

In the 3.x branch, use_legacy_names is true by default:

godot/editor/import/resource_importer_scene.cpp

Line 1076 in f11bed2

r_options->push_back(ImportOption(PropertyInfo(Variant::BOOL, "nodes/use_legacy_names"), true));

However, I can see that it's forcibly set to false for files that do not have an existing .import file (not to be confused with the top-level .import/ folder):

godot/editor/editor_file_system.cpp

Line 1695 in f11bed2

params["nodes/use_legacy_names"] = false;

[betalars]

However, I can see that it's forcibly set to false for files that do not have an existing .import file (not to be confused with the top-level .import/ folder):

Is there a way to override that for users?

[Calinou]

Is there a way to override that for users?

Select the glTF file in the FileSystem dock, go to the Import dock, check Use Legacy Names and click Reimport:

I can confirm that it's disabled for newly imported glTF scenes, as I said above.

[betalars]

I can confirm that it's disabled for newly imported glTF scenes, as I said above.

Just to confirm: this means if I first imported an glTF with an older version of godot, that checkbox can work, but if I used godot 3.4 for adding that file to my project the legacy-names checkbox won't work no matter what.

Because currently it is not working no matter what for me right now...

[akien-mga]

See #55796, there was indeed a regression in 3.4-stable which made the nodes/use_legacy_names option not functional, since it wouldn't see the regex module as available.

This was fixed by #54911 which is included in 3.4.1.

You can either reimport models with 3.4.1 RC 2 or 3.3.4 stable and they should have the legacy names, unless the option is disabled.

[RockyMadio]

Thank you.

Those compression options will make the meshes load faster during runtime?

[Calinou]

Those compression options will make the meshes load faster during runtime?

Mesh compression is mostly about improving rendering performance and reducing battery usage on mobile platforms. It's unlikely to affect loading times.

[RockyMadio]

Is this issue already solved in the new/current build?

[Calinou]

Is this issue already solved in the new/current build?

No, see #56447.

[RockyMadio]

No, see #56447.

Thank you