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
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Resolution Note (fix version 5.1.14):
Fixed in package 6.7.0, backported to 5.1.14