-
-
Notifications
You must be signed in to change notification settings - Fork 34
Conversation
…nitialization Fixed platforms so they only return true outside of the editor
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
This PR needs a lot of cleaning up as it contains so many different changes unrelated to the Camera System update |
XRTK-Core/Packages/com.xrtk.core/Interfaces/CameraSystem/IMixedRealityCameraSystem.cs
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested and reviewed. Works for me.
XRTK-Core/Packages/com.xrtk.core/Definitions/CameraSystem/MixedRealityCameraSystemProfile.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Definitions/CameraSystem/MixedRealityCameraSystemProfile.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Interfaces/CameraSystem/IMixedRealityCameraDataProvider.cs
Show resolved
Hide resolved
/// </summary> | ||
float DefaultHeadHeight { get; } | ||
/// <param name="dataProvider"></param> | ||
void RegisterCameraDataProvider(IMixedRealityCameraDataProvider dataProvider); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am a bit surprised here. The way you implemented this reminds me a bit of how I did the diagnostics system and hands back then. But then we changed it and decided to not have custom registries in the systems for consistency with the how it's setup in other modules. What made you change your mind here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it was mainly bc of the event handlers we are using.
We're not using event handling for anything in the camera system afaik.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Idk I can go either way with this.
I'll look back at the Input and Diagnostics systems to see if we can do something similar.
The biggest difference is that the Diagnostics and Input Systems are Event Systems, while the Camera System is not. No one is listening for events here.
XRTK-Core/Packages/com.xrtk.core/Providers/CameraSystem/BaseCameraDataProvider.cs
Outdated
Show resolved
Hide resolved
cleaned up profile value assignments cleaned up magic numbers
...ages/com.xrtk.core/Inspectors/Profiles/BaseMixedRealityCameraDataProviderProfileInspector.cs
Outdated
Show resolved
Hide resolved
…RealityCameraDataProviderProfileInspector.cs
...ckages/com.xrtk.core/Definitions/Controllers/Simulation/Hands/SimulatedHandControllerPose.cs
Outdated
Show resolved
Hide resolved
...ckages/com.xrtk.core/Definitions/Controllers/Simulation/Hands/SimulatedHandControllerPose.cs
Outdated
Show resolved
Hide resolved
...ages/com.xrtk.core/Inspectors/Profiles/BaseMixedRealityCameraDataProviderProfileInspector.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Providers/Controllers/BaseController.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Providers/Controllers/BaseController.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Providers/Controllers/BaseControllerDataProvider.cs
Outdated
Show resolved
Hide resolved
...ore/Packages/com.xrtk.core/Providers/Controllers/Simulation/Hands/SimulatedHandController.cs
Outdated
Show resolved
Hide resolved
...ore/Packages/com.xrtk.core/Providers/Controllers/Simulation/Hands/SimulatedHandController.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Services/BoundarySystem/MixedRealityBoundarySystem.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Services/BoundarySystem/MixedRealityBoundarySystem.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Services/BoundarySystem/MixedRealityBoundarySystem.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Services/BoundarySystem/MixedRealityBoundarySystem.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Services/BoundarySystem/MixedRealityBoundarySystem.cs
Outdated
Show resolved
Hide resolved
XRTK-Core/Packages/com.xrtk.core/Services/DiagnosticsSystem/MixedRealityDiagnosticsSystem.cs
Outdated
Show resolved
Hide resolved
...Packages/com.xrtk.core/Services/SpatialAwarenessSystem/MixedRealitySpatialAwarenessSystem.cs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's good. I'd like to see some syntactic sugar for accessing camera position and rotation, as well as playspace transform in a later revision of the SDK.
XRTK - Mixed Reality Toolkit Change Request
Overview
Refactored the Camera System to have per platform data providers and settings on top of the global ones.
Target of the change:
Is this enhancement for:
Breaking Changes:
Are there any breaking changes included in this change that would prevent or cause issue for existing projects.
IMixedRealityCameraSystem
IMixedRealityDataProvider
, all of the original logic in the camera system was moved into theBaseCameraDataProvider
class.Submodule Changes
XRTK/com.xrtk.sdk#153
XRTK/com.xrtk.oculus#54
XRTK/com.xrtk.lumin#60
XRTK/com.xrtk.wmr#66
TODO
Tests should also include moving the playspace to ensure that both spatial awareness and teleportation is keeping the tracked objects in sync with the playspace.