Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
9.0.0, 8.1.0, 8.0.1, 7.1.8.
Issue ID
1242629
Regression
No
[HDRP] Auto exposure effects occur on entering/exiting in play mode with Sprite Shape controller
Auto exposure effects occur on entering/exiting in play mode with "Sprite Shape controller".
Steps to repro:
1. Create a new HDRP Project.
2. Windows > Package Manager > 2D SpriteShape > Install.
3. Gameobject > 2D Object > Sprite Shape.
4. Enter in Play mode.
Actual Result:
Auto exposure effects occur on entering/exiting in play mode.
Expected Result:
Auto exposure effects should not occur.
Reproducible in:
2020.2.0a10, 2020.1.0b8, 2019.3.0f3 with Package Version 9.0.0, 8.1.0, 8.0.1, 7.1.8.
Environment:
Occurring on Windows 10 & Mac 10.15
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
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
Resolution Note:
This is unfortunately expected.
The issue lies from the fact that we perform pre-exposure based on the exposure computed previous frame. For the first frame we don't have such exposure and we set an exposure texture that is "neutral" but cannot be correct for what is actually on screen, hence the exposure system will adapt starting from that neutral value.
A content specific workaround for an application that I can suggest to the user is: if you are able to identify what the a fixed exposure could be on the first frame, start the application with fixed exposure with the value that is correct for your starting point (this is specific to your application). After the first frame you can switch back to automatic mode and the automatic exposure system will work with a good starting point.