Skip to content

Conversation

@Happyrobot33
Copy link

Closes #96

Pretty simple fix, Assign the dummy gameobject created to a variable so we can destroy it once we are done with it

Copy link

@meenphie meenphie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no need to instantiate a dummy object and destroy it later. We can just make a local variable and directly set its parent to the _mainSceneCamera

@Happyrobot33
Copy link
Author

Fair enough, didn't want to be responsible for breaking anything in case the object being in scene mattered :)

Co-authored-by: Fairplex <31825109+Fairpl3x@users.noreply.github.com>
@Happyrobot33 Happyrobot33 requested a review from meenphie January 18, 2024 19:38
Copy link

@meenphie meenphie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good for me

@momo-the-monster
Copy link
Collaborator

It looks like this was fixed in SDK 3.5.1, though the release notes did not mention it. Thanks for your contribution! That's why there's a conflict in the ClientSimStackedVRCameraSystem.cs file above.

@github-actions github-actions bot locked and limited conversation to collaborators Jan 14, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Unwanted "New Game Object" in hierarchy

3 participants