Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.1.0b7
Issue ID
916424
Regression
Yes
Enabling Frame Debugger and clicking on one of its drawcalls results in Game view not being rendered if Direct3D9 API is used
How to reproduce:
1. Open the attached "2017.1b7 FrameDebuggerBug" project
2. Go to File --> Build settings --> Player Settings and choose Direct3D9 as a default Graphics API
3. Go to Window --> Frame Debugger and enable it
4. Make sure the Game view window is visible and click on one of the drawcalls in the Frame Debugger list
Expected result: Clicking on an item from the list will show Game view as it appears including that drawcall
Actual result: Game view is not rendered
Notes:
1. When clicking on Camera.ImageEffects, Draw Dynamic and Camera.Render, Game view seems to be rendered okay
2. Not reproducible with other Graphics API's
Regression introduced in - 2017.1.0b2
Reproducible with - 2017.2.0a1, 2017.1.0b8, 2017.1.0b2
Not reproducible with - 2017.1.0b1, 5.6.1f1
Fixed in 2017.2.0b7
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Asset Labels and Asset Bundle controls are not available and Asset Labels section Label is not visible when a Preview is present or collapsed
- Editor Perforce login fails when Perforce shows a license expiry warning
- Assertion failed error in HDRP builds when enabling STP via script
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
Add comment