Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b1
Issue ID
923425
Regression
Yes
[Vulkan][Regression] Artifacts in Standalone player when Frame Debugger is attached
Steps to repro:
1. Open attached project and 't1' scene;
2. Go to Build Settings (File -> Build Settings);
3. Check 'Development Build' and 'Autoconnect Profiler';
4. Click 'Build And Run';
5. Choose build location and click 'Save';
6. In the Player configuration window select 'Windowed' flag and click 'Play!'
7. In Editor select Frame Debugger tab and click 'Enable';
8. Click once on Player window;
9. In FrameDebugger window select RenderForward.RenderLoopJob calls;
10. Observe standalone player window.
Expected result:
Scene is rendered in debug mode without artifacts (see attached expected.png screenshot).
Actual result:
Artifacts appear in standalone player (see attached actual.png screenshot).
Regression introduced in Unity 2017.2.0.
Notes:
- Reproducible in 2017.2.0b1, 2017.1.0a1;
- Not reproducible in 2017.1.0f1, 5.6.1p2;
- Reproducible only in standalone build and only on Vulkan graphics API; not reproducible for other graphics APIs.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Add comment