Search Issue Tracker
Fixed
Fixed in 6000.0.51f1, 6000.1.7f1, 6000.2.0b2, 7000.0.0a2
Votes
0
Found in
6000.0.47f1
6000.1.0b15
6000.2.0a9
7000.0.0a1
Issue ID
UUM-103220
Regression
Yes
CaptureScreenshotAsTexture fails when VR headset is connected and is inactive during Play Mode
Reproduction steps:
1. Open the attached project “ReproProject“
2. Open the scene “OutdoorsScene“
3. Make sure that the VR headset is connected (Do not activate headset by putting it on)
4. Enter Play Mode
5. Select “TakeScreenshot“ GameObject in the Hierarchy
6. In the Inspector window, click on the “Take Screenshot“ check mark
7. Observe the result in the Console
Expected result: The screenshot is taken, no errors in the Console
Actual result: Screenshot is not taken, error appears in the Console
Reproducible in: 2023.3.0a9, 6000.0.47f1, 6000.1.0b15, 6000.2.0a9
Not reproducible in: 2022.3.61f1, 2023.3.0a8
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Reproducible with: Oculus Quest 2 (Quest 2), CPU: Snapdragon XR2, GPU: Adreno 650, v72, OS: 12
Notes:
- When trying to save the screenshot, a null exception error for Texture2D appears if reproduction steps were followed (More information in the internal notes)
- The issue can be fixed by entering Play Mode with an inactive headset (following the reproduction steps), then activating the headset afterwards. The problem does not reoccur when deactivating the headset (by putting it down), after entering Play Mode with VR headset deactivated. The issue only reproduces when re-entering Play Mode with an inactive headset
- Also reproducible in Standalone Player (More information in the internal notes)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment