Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
Votes
0
Found in
2018.2.8f1
Issue ID
1093178
Regression
No
The draw call count changes after moving the mouse into Game View when a Camera is rendering to a RenderTexture
Repro steps:
1. Open attached project "FrameDebuggerTest"
2. Open scene "Sample Scene"
3. Enter Play Mode
4. Main Menu -> Window -> Analysis -> Frame Debugger
5. Click "Enable" in the Frame Debugger's window
6. Move the mouse to the Game View
7. Observe the Frame Debugger Window
Actual: The draw call count changes until you press something in the Frame Debugger Window
Reproducible with: 2017.2.5f1, 2017.3.0a6, 2017.4.17f1, 2018.2.19f1, 2018.3.0f2, 2019.1.0a12
Notes:
- This kind of behavior can also be observed when moving the slider which is at the top of Frame Debugger Window to the far left
Fixed in: 2019.2.0a1
Backported to: 2018.3.3f1, 2019.1.0a14
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
Add comment