Search Issue Tracker
Won't Fix
Votes
3
Found in [Package]
2.0.0-preview.12
Issue ID
1228604
Regression
No
VectorUtils TessellatePath results in artifacts when stroke HalfThickness is set to zero
How to reproduce:
1. Open attached project "VectorGraphicsArtifacts.zip" and scene "SampleScene"
2. Enter Play mode
3. Observe Game view
Expected result: no artifacts are visible
Actual result: artifacts are visible
Reproducible with: 2019.3.9f1, 2020.1.0b4, 2020.2.0a5 (2.0.0-prev.7, 2.0.0-prev.12)
Could not test with: 2017.4 (package was not yet released), 2018.4.20f1 (2.0.0-prev.1), 2019.3.9f1 (2.0.0-prev.6) due to missing features
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- TextField cannot be edited in an extended Editor window when double-clicking it
- [VisionOS] visionos build do not add plugin or frameworks
- Mathf.Floor produces inconsistent results when processing Physics.Raycast.Point X coordinate
- Crash on CheckGameObjectsAndAddMissingRequiredComponents when opening a specific project
- Batch Mode and Cloud Build get stuck at 'Scanning for ADB Devices' when building for the Android or iOS platforms
Resolution Note:
Calling TessellatePath() generates geometry defined as triangles. Drawing line segments between these vertices will be subject to imprecisions and floating point errors if the stroke width is 0. A better approach would be to iterate through the bezier segments and subdivide it into fixed steps to generate the line segments.