|Attention||Topic was automatically imported from the old Question2Answer platform.|
I’ve been working on my project for some time now and I ran into an issue with these errors which I’m about to mention in a second. The first error for some reason started to happen after I added an “Area” node to my scene. I was basically trying to create a warp that goes to the next scene or “level”. The second error I still have no idea what its trying to refer to since there is no Stack Trace. The errors are below and also the scenes do load fine, its just the errors occur randomly and it bothers me a bit. Could this be a bug(s)?
C Error: Condition ’ !f ’ is true. returned: ERR_CANT_OPEN
C Source: scene\resources\texture.cpp:424
C Function: StreamTexture::_load_data
(NOTE: the level does load but since it seems to possibly point to a texture then I have no idea since I made sure all materials and textures were fixed and setup properly)
C Error: Condition ’ !body_in && !E ’ is true.
C Source: scene\3d\area.cpp:160
C Function: Area::_body_inout
-The first error shows a stack trace on one of my scripts which this never caused an error until the whole adding an area and making it change scene when colliding. Trace points to “get_tree().change_Scene()” as the culprit however it worked fine before.
extends VBoxContainer #THIS IS A SCRIPT FOR THE MAIN MENU TO SEE IF WE ARE GOING TO STAR THE GAME UP OR OTHER OPTIONS func _on_NewGameBtn_pressed(): #CHANGE TO THE FIRST LEVEL OR SCREEN get_tree().change_scene("res://SCENES/RealmOfDreams.tscn") pass
Code for Area(3D):
extends Area # class member variables go here, for example: # var a = 2 # var b = "textvar" func _physics_process(delta): var bodies = get_overlapping_bodies() for body in bodies: if(body.name == "Player"): get_tree().change_scene("res://SCENES/ROD_Chamber.tscn")
Okay guys so I manage to solve the second error with the !body_in && !E ’ is true. It seems the issue with this error was that “Monitoring” was still true even though the scene has switched. What I did was in code set it to false before I switch to the next scene and the error has finally disappeared. The only one that stands now is the first one which I’m still trying to tackle but if anyone can help me out that would be great. I’m just glad I got one of the errors out of the way, its a great joy.
UPDATE: So I clicked on the .tscn file of my level and everytime I do that the “Error: Condition ’ !f ’ is true. returned: ERRCANTOPEN” shows up. I’ve literally tried everything I could since it seems to possibly be related to a texture. I tried re-importing all my textures, re-add them to the appropriate materials, remove each model/scene instance in the level to see if one of them would be the culprit, and I checked the code. I’m not sure what to make of this, perhaps it is a bug but then I can load the other level I made just fine. It’s very strange and just a headache to find out. If only these errors were more descriptive on where exactly and what exactly is causing the issue.
zzxyr88 | 2018-03-27 03:35