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

Error Pops Every Time the Projects Get Started: Invalid node name for submenu, the following characters are not allowed with a Warning #84572

Closed
Lazy-Rabbit-2001 opened this issue Nov 7, 2023 · 2 comments

Comments

@Lazy-Rabbit-2001
Copy link
Contributor

Godot version

4.2 beta 5

System information

Windows 11, GLES3

Issue description

Everytime I started godot with a project, there is always an error:

Invalid node name for submenu, the following characters are not allowed:
. : @ / " %

with a warning:

drivers/gles3/rasterizer_scene_gles3.cpp:265 - Attempting to use a shader that requires tangents with a mesh that doesn't contain tangents. Ensure that meshes are imported with the 'ensure_tangents' option. If creating your own meshes, add an ARRAY_TANGENT array (when using ArrayMesh) or call generate_tangents() (when using SurfaceTool). (User)

Steps to reproduce

Open any project

Minimal reproduction project

Issue.zip

@Lazy-Rabbit-2001 Lazy-Rabbit-2001 changed the title Error Pops Every Time the Projects Get Started: Invalid node name for submenu, the following characters are not allowed and a Warning Error Pops Every Time the Projects Get Started: Invalid node name for submenu, the following characters are not allowed with a Warning Nov 7, 2023
@YuriSizov
Copy link
Contributor

YuriSizov commented Nov 7, 2023

While the warning is added by #84183, this shouldn't really happen. I guess we use a generated node name somewhere in the editor to set a submenu?

This needs to be looked into, might be a mistake. Although we can also allow the @ character, since a node can technically have it in its name, just not in any name a user can submit.

@AThousandShips
Copy link
Member

Closing in favour of:

Which describes the same issue

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

No branches or pull requests

3 participants