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
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Add comment