Search Issue Tracker
Fixed in -
Votes
0
Found in [Package]
7.1.5
Issue ID
1201806
Regression
Yes
[LWRP] Graphical shader artifacts appear in the Scene view when there are Tilemaps present
Steps to reproduce:
1. Open user's attached project "Be_Hero.zip"
2. Zoom out in the Scene view
3. LWRP shader artifacts appear on Tilemaps in Scene view
Expected results: graphical shader artifacts do not appear in the Scene view
Actual results: graphical shader artifacts appear in the Scene view on Tilemaps
Reproduced with: LWRP 7.1.5 (2019.3.0b4), LWRP 7.1.7 (2019.3.0f4, 2020.1.0a18)
Not reproducible with: LWRP 6.9.2 (2019.2.17f1), LWRP 7.0.1 (2019.3.0b3)
Could not test with 2017.4 and 2018.4 due to package errors in the console
Notes:
-Reproducible always on macOS, doesn't often reproduce on Windows 10
-Issue persists when using URP shaders as well
-Disabling the "Grid" GameObject under "Maps" in the Hierarchy window and enabling it again solves the issue
-After restarting Unity the issue is gone, however project must be unpacked again to reproduce
-User has reported that Unity crashes after disabling the "Grid" GameObject, but couldn't reproduce
Crash stacktrace:
0x00007FF7091E9692 (Unity) TransformVerticesInnerLoop<0,1,0>
0x00007FF70920AC91 (Unity) TransformVerticesStridedREF
0x00007FF707F92534 (Unity) TransformVertices
0x00007FF709DF9AC4 (Unity) TilemapRendererJobs::TilemapRendererGeometryJob::Execute
0x00007FF70925998D (Unity) JobQueue::Exec
0x00007FF70925A0ED (Unity) JobQueue::ExecuteJobFromHighPriorityStack
0x00007FF70925BC43 (Unity) JobQueue::ProcessJobs
0x00007FF709260FC6 (Unity) JobQueue::WorkLoop
0x00007FF7097AAFF3 (Unity) Thread::RunThreadWrapper
0x00007FFF669A7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FFF6736CED1 (ntdll) RtlUserThreadStart
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version -):
Fixed in 2020.1.0a26, backported to 2019.3
Resolution Note (fix version -):
Fixed in 2020.1.0b2
Resolution Note (fix version -):
Fixed in 2019.3.5f1