-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Fix DeveloperError when zooming in 2D #1437
Conversation
… crash when attempting to normalize the zero vector during translation in 2D.
Conflicts: CHANGES.md
Can we add a unit test to verify that this doesn't break again? |
@mramato This is ready. |
If you use the mouse to zoom-in as close as possible, and then call the camera |
That is by design. The |
Okay, we can save that discussion for a camera API review further down the line. |
Fix DeveloperError when zooming in 2D
Chrome Canary recently added `navigator.hardwareConcurrency` which exposes the number of physical cores on the client. This is a simple change to expose that value (or a default if not defined) on `FeatureDetection`. I chose 3 as the fallback because according to Steam's hardware survey (http://store.steampowered.com/hwsurvey/) (2 cpus 47.26% 4 cpus 44.94%) This will be handy when we do #1437 (probably post 1.0), but is useful immediately for `Primitive` creation.
Fixes #1432.
Fix developer error when zooming creates an invalid frustum. Also fix crash when attempting to normalize the zero vector during translation in 2D.