Search Issue Tracker
Duplicate
Votes
2
Found in
2017.3.0p2
Issue ID
995199
Regression
No
(Crash) ScreenCapture.CaptureScreenshotAsTexture captures random region
To reproduce:
1. Open the project, attached by the user ("ScreenCaptureIssue.zip")
2. In the top menu bar, select Capture -> CaptureScreenshot
3. Observe the newly created image in the Project browser (needs a project refresh with Ctrl + R)
4. In the top menu bar, select Capture -> CaptureScreenshotAsTexture
5. Observe the created texture
Expected: both methods capture the same region of the game view
Reproduced in 2017.3.0a7, 2017.3.0p2, 2017.3.1f1, 2018.10b5
Could not test in earlier versions, CaptureScreenshotAsTexture method was introduced only in 2017.3.0a7
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
This is a duplicate of issue #1053476