Search Issue Tracker
By Design
Votes
0
Found in
5.3.1f1
Issue ID
764566
Regression
No
[FrameDebugger] Global shader parameter values get reset after exiting play mode
Steps to reproduce:
1) open users attached project
2) play scene 'GlobalIntReportingError'
3) capture a frame with the frame debuger
4) see that the cube is grey
5) quit the game with the "play button"
Expected: cube keeps its shader values until the debugger is closed
Actual: values get reset
Reproduced: 5.0.4f1, 5.3.1p3, 5.4.0b3
Comments (1)
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
- 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
- GameObject becomes gray when using HDRP and STP together on macOS
Aras
Dec 07, 2016 12:03
Yeah. The thing is, Frame Debugger never "captures" a frame.
It always just literally renders the frame up until your selected draw event, and then stops doing everything after it. And that is always done "in real time", the frame is always re-rendered in the process. That means if anything changes behind the scenes (shader variables, meshes, textures etc.), it is being immediately reflected in the frame debugger.
Which is sometimes what you want, but often what you don't want too... We haven't made any actual "capture the frame" functionality yet though :(