Search Issue Tracker
Fixed
Fixed in 6000.0.1f1
Votes
0
Found in
2023.3.0b9
6000.0.0b11
Issue ID
UUM-59115
Regression
No
Game/Scene View flickers when using multiframe rendering API
Note: this issue was originally reported to the Recorder team but can be reproduced when using only the multiframe API without the Recorder package.
Reproduction steps:
- Open the attached [^2023.3.0a17_hdrp_accumbug.zip] project
- Open the {{OutdoorsScene}} scene
- Select the {{Main Camera}} GameObject
- In the {{FrameManager}} component's context menu, select the {{Start Recording}} option
Expected result:
The Scene View and GameView windows should display the rendered content of the scene without any artifacts or unexpected behaviors
Actual result:
The Scene View and Game View windows start flickering black/white and the images recorded on disk are incorrect.
NOTES
The issue only seems to happen when specific values are used with the multiframe API. Notably:
- {{Samples}} = 2
- {{shutterInterval}} <= 0.5
- {{shutterFullyOpen}} > 0
- {{shutterBeginsClosing}} < 1
The problem might still be happening with other values but I've found this combination to be the most visible/obvious.
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
- UI Builder Data Path Source List starts flickering and scrolling when trying to select the last item in the list
- Crash on ProcessSceneBeforeExport when analyzing selected Addressables rules in a specific project
- HDR images are compressed incorrectly with default settings on Android Platform
- Crash with multiple stack traces when painting detail on Terrain with a highly detailed Prefab
- Crash on mono_object_handle_isinst_mbyref_raw when SerializedReference points to a struct implementing ISerializationCallbackReceiver whose first field is a UnityEngine.Object
Resolution Note (fix version 6000.0.1f1):
The flickering was indeed a bug in the way we handle sequences where the weight of the first frame is zero.
However, given the parameters of the user in the repro project, the expected output is just black: only two time-samples are used and given the shutter profile parameters, both samples have a weight of zero.