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

"Stop Remote Debugging" causes incorrect rending of 3d Object #308

Open
bryantAXS opened this issue May 30, 2018 · 3 comments
Open

"Stop Remote Debugging" causes incorrect rending of 3d Object #308

bryantAXS opened this issue May 30, 2018 · 3 comments

Comments

@bryantAXS
Copy link

bryantAXS commented May 30, 2018

Running Viro React 2.7.0

To be clear, this is only happening when I'm NOT remote debugging. When I am debugging, it's rendering fine. I first noticed the issue when downloading a version with Test Flight

Here's a video of the issue. https://cl.ly/3J0R230P401x

@bryantAXS
Copy link
Author

As an update, it looks like getBoundingBoxAsync on Viro3DObject is returning 0 values for some of the properties inside the boundingBox variable. Often they are all zero, sometimes one or two have values. Again, this is only happening when not remote debugging.

@bryantAXS
Copy link
Author

Another update, I wrapped getBoundingBoxAsync inside a short setTimeout and that seemed to have fixed the issue.

@radvani
Copy link
Contributor

radvani commented May 30, 2018

Hi @bryantAXS, thanks for this update. The timeout works, but is obviously not ideal. The underlying problem is that the bounding box is updated once per frame, so immediately after load it may be updated yet. We have a bug filed to fix this, and will target this for our next release. I will keep this issue open until then.

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