Search Issue Tracker
Fixed in 5.1.14
Votes
0
Found in [Package]
5.7.2
Issue ID
1146586
Regression
Yes
[LWRP] DrawMeshNow returns wrong positions/scales when called from endCameraRendering hook
How to reproduce:
1. Open attached project
2. Open Scene scene
3. Enter the Play Mode
4. Move cursor around till you find a sphere
Reproducible with: 2019.1.0b6, 2019.1.0f2, 2019.2.0a13, 2019.3.0a1
Not reproducible with: 2017.4.26f1, 2018.3.14f1, 2019.1.0b5
Reproducible with 5.7.2 - 6.5.3 Lightweight RP packages
Not reproducible with 5.2.3 Lightweight RP package
Actual results: wrong positions and scales get returned
Expected results: correct positions and scales should be returned
Reproducible on both Windows and iMac
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
- [macOS] Editor window is not restored to previous position when launching the Editor and mouse cursor is on a different screen
- [Usability] Warning message in an Adaptive Probe Volume Component is not informative enough when Realtime Global Illumination is enabled
- Inspector for Adaptive Probe Volumes is not repainted when toggling Realtime Global Illumination setting in the Lighting Window
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
Resolution Note (fix version 5.1.14):
Fixed in package 6.7.0, backported to 5.1.14