godotengine / godotengine/godot

Godot can't find the Node above when the node is part of the inherited scene

Open
#98,775 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug topic:core
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

mac Mini M1 with newest MacOS

### Issue description

I am trying to connect a signal to a function of a parent node in an inherited scene.
But, I am getting an error:
"Cannot get path of node as it is not in a scene tree."

### Steps to reproduce

Download the mrp and open the room 1 scene.
There will be a timer as a child of the "base component" node.
Try to connect the timer's timeout() signal to the parent's function "quick_check()".
An error will be printed.

You can also go to room 2 node and try to add the timer from the beginning and connect it to the parent's "quick_check()" function and the same error will appear.

Once launched, the game works as expected, at least for now…

https://github.com/user-attachments/assets/774b98d0-e804-4b06-b16b-0c8f55295944

### Minimal reproduction project (MRP)

[cant-find-the-node-above.zip](https://github.com/user-attachments/files/17608397/cant-find-the-node-above.zip)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by opening the attached cant-find-the-node-above.zip project and reproducing the signal connection error in room 1 and room 2. Trace the editor path used to connect a Timer timeout signal to the inherited parent function; done means the connection succeeds without the scene-tree error and the resulting project still runs correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
godot
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.