VR Scene Change

UnknownUser

Hello, everybody! Been working with Godot a couple of weeks, now, and I'm really loving it when I'm not hating it. Just spent a few hours trying to solve a raycast problem only to find that I had forgotten a minus sign, and my raycast was pointing in the wrong direction. C'est la frickin' vie, I guess.

Anyway, I'm experimenting with how to navigate between scenes. I figured out how to change scenes when I bring the controller close to a particular sphere. The problem is, when I change scenes, the controller doesn't track anymore. I have a feeling if I can get this nailed down, it will fill in some major holes in my knowledge of how the engine works.

My teleport and scene change are in my controller node. My ARVR initialization is in my "World" node:

extends Spatial

func _ready():
	var arvr_interface = ARVRServer.find_interface("OpenVR")
	if arvr_interface and arvr_interface.initialize():
		get_viewport().arvr = true
		get_viewport().hdr = false

Thanks in advanced for any smarter eyeballs than mine!

TwistedTwigleg

Welcome to the forums @SMcKelv!

It could be that changing scenes interrupts the ARVR thread, which could be breaking the VR tracking. Are you initializing the ARVR server on every scene? In the VR starter tutorial, I was able to reload the same scene and the controllers still worked, which may have been related to having the script always initialize VR. That said, I didn't try scene changing though, just reloading.

Does the Godot console show anything when changing scenes?

UnknownUser

I have a "main" script attached to the "World" node as the parent (please see code above) that initializes VR. It is present in both scenes. I detached the "main" script from World and put the code directly into the _ready of my controller in both scenes, and the controller mesh wasn't even visible, though it still interacted with the wall of my play area.

Am I doing something that is keeping the nodes from being able to communicate with each other? Am I supposed to be loading a sub-scene somehow, or do we just throw out the whole mess and start over each time? Perhaps I am not putting the right code with the right node script? Maybe the scene change mechanic should be in "main" somehow?

TwistedTwigleg

I don’t know, it worked fine when reloading the scene for me in the VR tutorial, and it is doing the same thing you have described. Maybe it’s a bug?

You could try a potential workaround of using background loading and see if that helps. That way, you could just instance the new scene, which may keep the controllers tracking. It sounds like it may be a bug though.