this post was submitted on 04 Oct 2023
16 points (100.0% liked)

Godot

5876 readers
13 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Links

Other Communities

Rules

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

!roguelikedev@programming.dev

Credits

founded 1 year ago
MODERATORS
 

I have had this happen with two scenes by now. These scenes consist of a large tilemap with multiple layers, a player and thats it. The scenes inherit from a LevelBase class I wrote, but that is so simple. that it can't be the problem. LevelBase just has a open_pause_menu() function and nothing else. Does anyone know why this might be happening?

EDIT: Forgot to translate the message. It says "scene file 'office.tscn' seems to be invalid or faulty."

you are viewing a single comment's thread
view the rest of the comments
[โ€“] Zarr@lemmy.world 4 points 1 year ago (1 children)

I'd been having issues with this myself recently. I assume you're in Godot 4.1? I tracked the issue down to being cyclic references in GDScript. As an example from what you've provided, you may have LevelBase referring to the Player script, and then the Player script referring to LevelBase. This only seems to be a problem with the type hinting in GDScript like the following:

var player:PlayerClass

Removing the hinting may fix it. As for the bug, you can read some more on it here: https://github.com/godotengine/godot/issues/80877

As a side note, I've noticed that 4.1 has this issue worse than 4.0. In 4.0 it just unbinds the script from the scene, and allows you to rebind it again. But in 4.1 it causes the error message, making you unable to open the scene.

[โ€“] Smorty@lemmy.blahaj.zone 1 points 1 year ago

I'm using the latest Dec build, but it was a problem before that.