[Feature Request] Enable ObjectInColliderCondition have multiple TriggerObject

[AronSchaub]

ObjectInColliderCondition could work with a MultipleScene ObjectProperty. It currently only has a single SingleRefObject:

VR-Builder/Source/Core/Runtime/Conditions/ObjectInColliderCondition.cs

Line 43 in 0f94a59

public SingleScenePropertyReference<ColliderWithTriggerProperty> TriggerObject { get; set; }

you would just need to loop through all:

VR-Builder/Source/Core/Runtime/Conditions/ObjectInColliderCondition.cs

Line 135 in 0f94a59

counter += Data.TriggerObject.Value.IsTransformInsideTrigger(sceneObject.GameObject.transform) ? 1 : 0;

you can then put a warning, that for the fast forward the first in list will be used.

[poetter-sebastian]

Heya Thanks for the feature request.

This could be a nice "good first issue".

[stgrosshh]

ObjectInColliderCondition could work with a MultipleScene ObjectProperty. It currently only has a single SingleRefObject:

VR-Builder/Source/Core/Runtime/Conditions/ObjectInColliderCondition.cs

Line 43 in 0f94a59

public SingleScenePropertyReference TriggerObject { get; set; }
you would just need to loop through all:

VR-Builder/Source/Core/Runtime/Conditions/ObjectInColliderCondition.cs

Line 135 in 0f94a59

counter += Data.TriggerObject.Value.IsTransformInsideTrigger(sceneObject.GameObject.transform) ? 1 : 0;
you can then put a warning, that for the fast forward the first in list will be used.

What would be the use case for that and how would you decide how many of the TargetObjects have to go in which TriggerObject?

[poetter-sebastian]

@stgrosshh an use case could be a two handed tool.

[AronSchaub]

The use case is simply that I want to have the possibility to put multiple objects into multiple possible snap zones without the need for multiple conditions.