Search Issue Tracker
Fixed
Fixed in 2019.4.X
Votes
0
Found in
2019.4
2019.4.27f1
Issue ID
1338579
Regression
Yes
[Vulkan] ScreenCapture.CaptureScreenshot does not work in the Editor when using Vulkan and Color Space is set to Linear
How to reproduce:
1. Open the attached "1338579_Repro" project
2. Open the Scene "SampleScene"
3. Enter the Play Mode
4. Press "space"
Expected results: No errors are thrown, a screenshot is taken
Actual results: The "Failed to capture screen shot" error is thrown, no screenshot is taken
Reproducible with: 2019.4.6f1, 2019.4.27f1
Not reproducible with: 2019.4.5f1, 2020.2.0a1, 2020.3.11f1, 2021.1.9f1, 2021.2.0a18
Could not test with: 2018.4 because HDRP was not yet available
Notes:
- Reproducible only with Vulkan Graphics API
- Screenshot should be saved in the "%userprofile%\AppData\Local\Packages\<productname>" folder
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Issue is only in the 2019.4 stream
Resolution Note (fix version 2019.4):
ScreenCapture.CaptureScreenshot was always failing by mistake on Vulkan - this is now fixed.
Fixed in 2019.4.30f1