Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.29f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1368348
Regression
No
MeshTopology.Lines rendering inconsistency on some Windows hardware
How to reproduce:
1. Open the attached project "incorrect_Gridlines.zip"
2. Open Assets > Scenes > SampleScene.unity
3. Enter Play Mode
4. Observe the gridlines
Expected result: Gridlines are rendered correctly "Correct.png"
Actual result: Gridlines are rendered incorrectly "Incorrect.png"
Reproducible with: 2019.4.31f1, 2020.3.19f1, 2021.1.23f1, 2021.2.0b14, 2022.1.0a10
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
- “[In Project] Unknown filter “i”” message is thrown in Search window
- [Ubuntu] Asset Bundles Dropdowns Contain Empty Row in Inspector
- Symbols are generated for a third-party native plug-in with 'Shared Library Type' set to 'Executable' when building for Android
- "Search by Import Log Type" Icon Nearly Invisible in Light Theme (Project Window)
- [Android] Realtime Directional Light turns off when there is no realtime shadow caster in the view
Resolution Note:
This can be both By Design or Third Party Issue. The By Design part is that MeshTopology.Lines use the line primitives available in different graphics APIs, the Third Party Issue part is the way lines are drawn by HW. The line drawing is not specified strictly enough for it to always produce good looking lines, and the details of the specifications differ slightly per graphics API. For good looking graphical effects lines should not be used, but a mesh ought to be generated and drawn in the traditional way.