Error strange!

This is a READ-ONLY snapshot of the Godot Community Forums when TwistedTwigleg was the owner, which is hosted for archival reasons only. The current Godot Community Forums can be found here.

Some links may point to external websites, including the current Godot Community Forums. These websites are not associated with TwistedTwigleg.

Odin

May I ask what the error is? I don't know how to fix it? I need some help. Thank you!

cybereality

It's not an error in your code, it's an error from the engine. It sounds like perhaps you have a 3D node (like a Spatial) as a parent on a Node2D or Sprite. This is usually not an issue, but if you call certain functions that are meant for 2D when the object is 3D (or the other way around) it could cause problems.

Odin

Sorry Cyber, so far I've only done 2D, never done 3D. And I checked my project again. Still no node of 3D type. Is there any other possibility with this error Cyber?

Pixophir

There certainly are other possibilities, but without more information (can you post the scene somewhere if it has no further dependencies ?) we would be guessing.

From what I gather something tries to find a relative transform to a parent node and that something has no parent node.

Megalomaniak

I see you are mixing control node types and node 2D's that might have a similar problem to what @cybereality was referring to with mixing node 2D and node 3d/spatial.

Pixophir

Yes, maybe that something I mentioned just has no parent of type Node2D.

Interestingly, the method's declaration is:

Tranform2D get-relative-transform-to-parent(Node parent) const

but internally it checks if parent is a Node2D and produces the error if not. I don't quite understand why it produces the error and not just stop hiking up the tree when there's no node with a Transform2D.

Odin

This is a picture of the World scene. BG scene is Begin scene. Only when I switch the scene from the BG scene to the World scene it gives me that error, but the game still works fine. Before, when I used Godot 3.4, it didn't happen, but when I switched to Godot 3.5, I got this. Personally I guess the fault lies in the World scene, but I don't know exactly where.Please help. Thank you every body!

Pixophir

I honestly suspect this is just a debugging leftover that eluded QA before release :-)

Odin

The current fix is to follow the attached image. I tested it, and it's true that there are no more errors.

cybereality

Node is a base class, probably should only be used for extending new classes with code, not for visual objects.

Pixophir

@cybereality That was my intuitive reaction as well, but looking at the code the function does take a Node pointer argument, and the error message is printed by a macro that ensures that there's a correct return value. So it works when there are nodes in the tree that don't have a transform member.

I just don't understand why it throws that tantrum with a red error message.

cybereality

Node doesn't have a transform, though. It could take a pointer but that doesn't mean it's going to work. I mean, in theory, it shouldn't be an error, but that seems like the most likely cause. Also the Navigation2D has a huge yellow warning icon, that could be part of the problem as well.

Odin

The yellow icon warns that in the future Godot will not use Navigation2D node anymore, but will use Navigation2DServer.
It gives error with red lines because in our Tilemap node we have Navigation function, so for Godot 3.5 and above, if in Tilemap node with Navigation feature enabled, it is forced to be a child of navigation2D node. This may be something that doesn't make much sense in some situations, but in practice it has to be done to stop the error. Can't do anything else. Once again, thank you very much for your enthusiastic support! (^o)!

Pixophir

So the warning is unrelated.

The error message isn't exactly an error. It is just a message from a multi-purpose test-macro that some condition is met. But the function calling it has precautions for this condition, IOW, it works nevertheless.