Search Issue Tracker
Won't Fix
Votes
2
Found in
2021.3.44f1
2022.3.50f1
6000.0.23f1
6000.1.0a7
Issue ID
UUM-83893
Regression
No
OnDemandRendering.willCurrentFrameRender returns incorrect values in the Player when UnityEngine.Rendering.OnDemandRendering.renderFrameInterval is greater than 1
How to reproduce:
1. Open the attached “IN-85132” project
2. Open the “SampleScene” scene
3. Enter Play mode
4. Observe the Game window
5. Build And Run the project (File → Build And Run)
6. Observe the built game window
Expected result: The cube appears in front of the camera in the built game window the same way it does in the editor Game window
Actual result: The cube does not appear in front of the camera in the built game window
Reproducible in: 2021.3.44f1, 2022.3.50f1, 6000.0.23f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note:
-When making the frame interval 1 the cube is positioned in front of the camera both in-editor and in a built project, however in the built project the cube has a pink texture
-The issue also reproduces when using Vulkan API
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 RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
- Scene view has Y coordinates of the Screen Position node flipped when some of the URP features are disabled
- Volumetric fog shader variants are missing from build when "Strict Shader Variant Matching" is disabled
- Unnecessary modifications clutter the Scene when using a RectTransform driven by a LayoutGroup in a Prefab
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.