Search Issue Tracker
Fixed in 2017.2.0f3
Won't Fix in 2017.2.X
Votes
1
Found in
2017.2.0b2
Issue ID
928598
Regression
Yes
The errors appear, when GameObject has a child with ParticleSystem which is rotated along the y-axis to -180 and is moved
Reproduction steps:
1. Open the attached project;
2. Open the scene "test";
3. Enter Play mode;
4. Click the arrows on the keyboard;
5. Observe the Console window;
Actual result: the errors appear in the Console window:
Assertion failed: Assertion failed on expression: 'CompareApproximately(det, 1.0F, .005f)'
Assertion failed: Assertion failed on expression: 'fRoot >= Vector3f::epsilon'
Assertion failed: Quaternion To Matrix conversion failed because input Quaternion is invalid {-1.#IND00, -1.#IND00, -1.#IND00, -1.#IND00} l=-1.#IND00
Expected result: the errors should not appear.
Note: the errors appear only when GameObject has a child with Particle System which is rotated along the y-axis to -180 and this GameObject is moving. If the y-axis is set to less or more than -180, the errors do not appear.
Reproduced with: 2017.2.0b1, 2017.2.0b2
Not reproducible with: 5.6.2p2, 2017.1.0f3, 2017.2.0a4
Regression introduced with 2017.2.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Add comment