-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Fixed issue where hand joint lookup would throw dictionary exceptions for visualizers #10574
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Assets/MRTK/SDK/Features/UX/Scripts/RiggedHandVisualizer/RiggedHandVisualizer.cs
Show resolved
Hide resolved
|
|
||
| /// <summary> | ||
| /// Adds warnings to the nowarn line in the csc.rsp file located at the root of assets. Warning 618 and 649 are added to the nowarn line because if | ||
| /// Adds warnings to the nowarn line in the csc.rsp file located at the root of assets. Warning 414, 618 and 649 are added to the nowarn line because if |
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.
Do csc files work in subdirectories? Mostly, I'm wondering if we could put these warnings specifically in the root of the Oculus Integration Package folder instead of for the entire user's project, which seems a little heavy-handed.
|
The the visualizers are still null |
Overview
If the event data did not contain entries for all joints, the hand visualizer would throw an exception as it does a lookup on a hand joint which doesn't exist. This PR fixes that, stabilizing Oculus Visuals for 39.0 and beyond for 2019.
Also fixes #10409