Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
5.3.3p3
Issue ID
779594
Regression
No
[GLLEGACY] Line Renderers using opaque materials cause Unity to hang with OpenGL2.
Line Renderers using opaque materials cause Unity to hang when the graphics API is switched to OpenGL2.
Repro steps:
1. Open attached project.
2. Switch the API to OpenGL2.
3. Open NewLineRenderer scene.
4. Unity hangs.
Expected outcome: Unity to not hang.
Notes:
- Not a regression, happens back in 5.3.3.p3 and managed to repro upwards to 5.4.0b9.
- Unity hangs just opening the scene in the editor; no need to press play.
- Reproduces using Default-Material and Default-Diffuse.
- Creating a line renderer with Default-Material assigned in OpenGL2 does not cause the issue - it occurs only when switching from a different API to OpenGL2.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The cursor moves into wrong place when renaming folder/asset
- Assertion error "(dx - width < padding) || (dy - height < padding)" when using Pack Preview
- [Memory Profiler] The EntryType.NativeAllocationSites_MemoryLabelIndex of snapshots only reports -1 or 0 instead of the MemLabel used for allocations made from any call site.
- [Vulkan] Artifacts appear in the Player when using Screen Space shadows with orthographic camera
- Errors OnGUIDepth changed & GUIUtility:ProcessEvent when opening Textures with Third Party App
Add comment