Search Issue Tracker
Fixed in 2022.3.3f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a16
Votes
1
Found in
2022.2.7f1
2022.3.3f1
2023.1.0b4
2023.2.0a3
Issue ID
UUM-29274
Regression
Yes
"webcamTexture.didUpdateThisFrame" returns "True" only for the first frame when the project is built for WebGL
How to reproduce:
1. Open the user-attached project “didUpdateThisFrameWebGLTest”
2. Open the Build Settings and click Build And Run for the WebGL Platform
3. Press F12 to open the Console in the browser
4. Observe the Console
Expected result: “webcamTexture.didUpdateThisFrame” returns “True” for some frames
Actual result: “webcamTexture.didUpdateThisFrame” returns “True” only for the first frame and then it returns only “False”
Reproducible with: 2022.2.0a12, 2022.2.7f1, 2023.1.0b4, 2023.2.0a3
Not reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.0a11
Reproducible on: Windows 11 Pro and Google Chrome
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 (fix version 2023.2):
Fixed webCamTexture.DidUpdateThisFrame not getting correctly updated