Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.3.X
Votes
1
Found in
2018.2.10f1
Issue ID
1086548
Regression
No
RenderToCubemap offsets shadows when the material on the mesh has GPU Instancing enabled
How to reproduce:
1. Open attached project "CubeMap.zip" and scene "SampleScene"
2. Enter Play mode
3. While the Game view is active press "Spacebar" ("Spacebar" renders the CubeMap)
4. Stop Play mode
5. In Project window -> Assets, double-click "capture" image and observe it (refresh asset folder if the "capture" image is not seen)
Expected result: a cube map is captured without any casualties
Actual result: the shadows of the cubemap are offset and seen through other poles
Reproducible with: 2018.1.9f2, 2018.3.0b6, 2019.1.0a5
Could not test with: 2017.2.4f1, 2017.4.13f1 (due to RenderToCubemap requiring different arguments)
Comments (1)
-
RichardTVDM
Oct 24, 2018 13:11
This same issue also affects mesh in the resulting CubeMap.
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
- “Assertion failed on expression” errors thrown when undoing Nodes creation with keyboard shortcut
- Crash on various stack traces when using Texture2D.CreateExternalTexture() while rendering
- Clicking on section text in Node Library > Context folder throws NullReferenceException errors
- Node Library window sections text in Context folder are not visible when Editor is set to Light Theme
- "Scene Depth Difference" Node has an input Port which is called Position WS, directly referring to the World Space Position, when only the View Space Position can reflect if the object's depth is below or above the Plane
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a8
Resolution Note (fix version 2020.3):
Fixed in 2020.3.21f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.32f1