Skip to content
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

BelzierPointerRenderer briefly displays a LineRenderer customer tracer in the wrong location #1835

Closed
TheRealBobSmith opened this issue Jun 17, 2018 · 1 comment

Comments

@TheRealBobSmith
Copy link

Environment

  • Source of VRTK: Github
  • Version of VRTK: 3.2.1
  • Version of Unity3D: 2017.4.3f1
  • Hardware used: Oculus
  • SDK used: Oculus SDK

Steps to reproduce

Use an Empty game object with a LineRenderer as a BelzierPointerRenderer's Customer Tracer for teleporting. Frequently when teleporting, the Belizer tracer will flash briefly pointing at an incorrect location before immediately updating to the proper location, i.e. where the cursor is.

More explicitly, by teleporting from point X to point Y, then attempting to teleport to point Z, the Belzier tracer will flash briefly pointing towards point X before updating and pointing correctly to point Z. In other words, the curve will still briefly reflect the previous X->Y curve before updating to the current Y->Z curve.

This appears (my guess) to be caused by BelzierPointerRenderer's ToggleRenderer() function calling TogglePointerTracer(pointerState, actualState) prior to the Belzier curve is calculated to the appropriate target. Commenting out the TogglePointerTracer() call eliminates the issue.

Not sure if this part helps, but this issue appears to be specific to the LineRenderer. If I attach a Mesh Filter to the object with the LineRenderer, ONLY the line appears to exhibit this issue, while the associated mesh does not.

@thestonefox
Copy link
Member

Closing this as it's related to an older version of VRTK (v3.3) the master branch is now on VRTK v4. Feel free to request to reopen if the issue is still present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants