Feature: Excluding Objects in Live Connect

[aaronvark]

Is there any method (or plan) to exclude specific objects from transferring to Resonite, for instance using a specific component, or adding them to some sort of active exclusion list? This applies specifically to the live connection mode.

We're currently working on a (very early WIP) system that pulls object information for specific objects (those with tags in root, single-depth component information from there), and replicating that on the client side (in Unity, but planned also for Unreal, Godot, etc.). It would be very useful if the Unity SDK had some way to exclude the spawned object from then also replicating back to Resonite (which would cause duplicates, and potentially infinite looping).

Our system lives between Resonite and other clients, and the Unity SDK is currently connecting direct to Resonite. This setup might change in the future, as we're just experimenting with which setups are possible & interesting to try.

[Frooxius]

We can add some way to exclude objects potentially, but they'd have to marked before you start love mode and you'd have to make them as children of the excluded hierarchy from the start too.

It will also create some weirdness - what if you unmark them?

What are your use cases for this? That might help understand what are you trying to achive.

[aaronvark]

The primary use-case is bi-directional creation & interaction. Keeping them contained within a subhierarchy in root would be a workable solution tbh, as we'll create the objects in that state, and wouldn't ever "un-mark" them (as they are representations of objects created in Resonite).

To further elaborate: we'd have people in Resonite modifying a world, and people in Unity (and eventually other engines too probably) both experiencing & interacting with that world (and the UnitySDK would allow for pretty far-reaching editing as well). The world from the Unity side gets represented in Resonite, partially live (we'd probably sync the static world elements once only), and the Resonite-created objects get re-created in Unity.

[Frooxius]

Hmm I see. We don't support bi-directional creation right now, so if that's a pre-requisite, we'd need to implement that first.

[aaronvark]

We're currently doing the Resonite -> Unity part ourselves using ResoniteLink, so even without support within the UnitySDK directly it would be a helpful workaround.