I have a Area3d as a 3d button alternative that starts the game by setting player gravity scale to normal and you then free fall through a dropper course ( that all works fine ). When the dropper course ends, you are sent to a plinko game to gamble your score you got from dropper ( also all works fine ). However, when I then change the scene back to the dropper, the area3d acting as a button stops detecting my mouse entirely ( I have 3 func - mouse_entered, mouse_exited, and on area 3d input event ). If anyone knows a possible fix to this let me know, I can send code/screen shots/videos if needed.
If you are preloading or @export the PackedScene then you may have a cyclic dependency. For big scenes it’s often better to use load and/or @export_file.
Yes I am queue freeing then using change_scene_to_file, and the area 3d button is a child of that scene, but I am also queue freeing the area 3d itself after a second has pasted since I pressed it initially considering its already out of frame.
Sorry if I misunderstand, but I’m not using any packedscenes for these big scenes. I am using get_tree().change_scene_to_file(“res://scenes/plinko_main.tscn”) to change. Hope this properly responds to your question.
I might be wrong but I think you need to reconnect the signals after the node is reloaded.
And my backup answer is maybe some canvas layer is blocking your button once it’s reloaded.
If neither works, sorry I couldn’t be of more help.