Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.1.3f1
2020.3
2021.1
2021.2
Issue ID
1342047
Regression
No
PhotoCapture has a very low framerate
How to reproduce:
1. Open the attached "Project.rar" project
2. Switch to UWP
3. Enter the PlayMode
4. Press "Start Capture"
Expected result: Frame capturing is instant
Actual result: Frame capturing takes between 0.6 and 2 seconds
Reproducible with: 2019.4.28f1, 2020.3.11f1, 2021.1.11f1, 2021.2.0a21
Notes:
- On Hololens 2 the capture between frames has a delay of around 3 seconds.
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
- Crash on GfxDeviceD3D12::AllocBottomLevelAccelerationStructure when using Raytracing
- The search icon in the "Searches" sections is blurry and inconsistent
- "RenderingCommandBuffer" error is thrown when switching to the tvOS platform
- Left side cog menu button is obstructed by the maximum Y value of the graph when editing a curve in the Particle System Curves
- "Property exceeds previous array size (64 vs 32)." warnings are thrown when switching from tvOS platform to a Standalone platform after restarting the Editor
Resolution Note (2022.1.X):
PhotoCapture is not meant for rapid frame capture. We suggest either using VideoCapture class or call into Windows.Media.Capture classes like LowLagPhotoCapture directly so that their usage is optimized for the required scenario.