Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.0f3
Issue ID
900357
Regression
Yes
Setting the number of line segments of Line Renderer during playmode results in a few Assertion failed errors
How to reproduce:
1. Open the attached "LineRendererIssue" project
2. Open the "Main" scene and enter playmode
3. Press "F" key to create a line and hold down "G" key for it to follow you along (while pressing W,S,A,D keys)
4. Repeat the third step a few times (issue should appear a second time, most likely)
Expected result: New line is created and it follows along, no errors appear
Actual result: A few "Assertion failed on expression: 'curveT() >= GetRange()...' " and "Assertion failed on expression: 'curveT() >= m_Curve[lhs].time...' " errors appears
Reproducible with - 2017.1.0b1, 5.6.0p1, 5.5.3f1,
Not reproducible with - 5.4.5f1, 5.3.8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "No GUI Implemented" is displayed when using PhysicsMask with a CustomEditor
- "Report is from another project" popup warning is shown on domain reload when Project Auditor was previously ran in a different project
- Addressables Analyzer flags duplicate resource references from ScriptableObjects incorrectly when the corresponding field has been removed
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
Add comment