Search Issue Tracker
By Design
By Design in 2020.3.X
Votes
0
Found in
2020.3.44f1
Issue ID
UUM-13233
Regression
No
ScreenCapture CaptureScreenshotAsTexture failed to generate texture when Game view has high custom resolution
How to reproduce:
1. Open attached project "ScreenshotBugStripped.zip" and scene "SampleScene"
2. Enter Play mode
3. In Game View, set Custom Resolution to 3000x3000 pixels
4. Press 'Space' bar key
5. Observe Console window
Expected result: "No Error" is printed
Actual result: "CaptureScreenshotAsTexture" failed is printed
Reproducible with: 2018.4.26f1, 2019.4.6f1, 2020.1.0f1, 2020.2.0a18
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
- 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
Resolution Note:
In repro project `ScreenCapture.CaptureScreenshotAsTexture` is called straight away inside Update. This violates official API docs requirement for waiting for the end of frame rendering, e.g., utilizing WaiForEndOfFrame. Which is highlighted by error message in console:
CaptureScreenshotAsTexture() failed to generate texture! Was method called before the 'end of frame' state was reached?
Resolution Note (2020.3.X):
In repro project `ScreenCapture.CaptureScreenshotAsTexture` is called straight away inside Update. This violates official API docs requirement for waiting for the end of frame rendering, e.g., utilizing WaiForEndOfFrame. Which is highlighted by error message in console:
CaptureScreenshotAsTexture() failed to generate texture! Was method called before the 'end of frame' state was reached?