Feature Request XR Interactions with Additive Scenes

Right now, in order for a Simple XR Interactable to be found by the XR Interaction System, it needs to exist in the first, primary scene.

Even if you tell the SceneManager.SetActiveScene, the first scene in the list of loaded scenes is the one where the interaction system attempts to find objects.
This is easily reproducible at runtime by dragging objects between loaded scenes.

I'd like to have objects in additive-loaded scenes detectable by the interaction system for the sake of object management. Doing this now, the interaction system cannot detect them.

 

I think there is still something amiss. I see your point about the XR Interaction Manager and the reference to it on a XR Interaction, but that doesn't really answer why one scene works and the other doesn't.

The problem appears to occur in this method:

Code (CSharp):

1. int CheckCollidersBetweenPoints(Vector3 from, Vector3 to)
2.         {
3.             Array.Clear(m_RaycastHits, 0, k_MaxRaycastHits);
4.  
5.             // Cast from last point to next point to check if there are hits in between
6.             if (m_HitDetectionType == HitDetectionType.SphereCast && m_SphereCastRadius > 0f)
7.             {
8.                 return Physics.SphereCastNonAlloc(from, m_SphereCastRadius, (to - from).normalized,
9.                     m_RaycastHits, Vector3.Distance(to, from), raycastMask, raycastTriggerInteraction);
10.             }
11.  
12.             return Physics.RaycastNonAlloc(from, (to - from).normalized,
13.                 m_RaycastHits, Vector3.Distance(to, from), raycastMask, raycastTriggerInteraction);
14.         }

Right now I have 3 scenes in my hierarchy:

[game]
[scenery] <- active
[DontDestroyOnLoad]

I have my XR Interaction Manager in the DontDestroyOnLoad.

Previously, my [game] scene was set as active and my interaction was spawning in the [game] scene, but I recently messed around with some code that toggled the ActiveScene and shifted it to [scenery].

Now that [scenery] is considered active on load, all of the XR Interactions are spawning associated with that scene. No matter what I do, I cannot select the interaction now.

As soon as I drag it into the [game] scene, the interaction works immediately. If I drag it back into the [scenery] scene, it doesn't work.

 

The reference to the XR Interaction Manager is valid, regardless of scene the object is in

 

Also, it's not even based on the first scene in the hierarchy, it's based on the first scene that was loaded.

If I drag [scenery] to show first in the list, the interaction still does not hover.

with:

[scenery] <- active
[game]
[DontDestroyOnLoad]

I still need to drag my interaction into [game] that was loaded first in order to get these working.

 

I just recreated the scenario with multiple scenes and haven't been able to reproduce. I have a sinking suspicion that this is related to multiplayer and physics scenes

 

Yeah, just recreated the scenario with Mirror using the MultipleAdditiveScenes example.

Within this example, there's a physics scene separate from the default:
https://github.com/vis2k/Mirror/blo...pleAdditiveScenes/Scripts/PhysicsSimulator.cs

Using this MultipleAdditiveScenes example, if you add a VRInteraction to the added scene, it will fail

 

Hey, thanks for the reply! I did end up resolving it.
I had initially built my multiplayer tech around the MultipleAdditiveScenes demo because of the way I wanted to lay things out.

With that, came the example code that was adding the Scene with specific `LoadSceneParameters`.

These parameters would include this:
localPhysicsMode = LocalPhysicsMode.Physics3D

Once I removed the LocalPhysicsMode param from the scene params, my interactions started working more reliably.

I say more reliably, because now I can hover the object and detect. I still get some weird flicker / inconsistent physics, but it's at least detectable in some sense now and I can debug from here.

That was a really frustrating issue to debug though, holy moly