Search Issue Tracker
Fixed
Fixed in 6000.2.0a7
Votes
2
Found in
6000.0.40f1
6000.1.0b7
6000.2.0a5
Issue ID
UUM-98147
Regression
No
ScalableBufferManager does not work correctly when MSAA is enabled and RenderGraph is enabled
How to reproduce:
1. Open the “RGResolution.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Move the Slider to the left
5. Observe the Game view
Expected results: The view gets more pixelated and the screen does not change its size
Actual results: The view zooms in towards the bottom-left corner
Reproducible in: 6000.0.40f1, 6000.1.0b7, 6000.2.0a5
Could not test in: 2022.3.58f1 (RenderGraph does not exist)
Reproduced on: Windows 11 Pro (24H2)
Not reproduced on: No other environment tested
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
- Particle System Renderer icon is missing in Animation window > Add Property context menu
- [Android] Legacy, TMP and UI Toolkit Input Field language toggle to some non-latin alphabet languages does not work with external keyboard
- Crash on keywords::LocalKeywordState::operator when calling ShaderUtil.GetPasskeywords with ShaderType.RayTracing set as the third parameter
- Inconsistent “Remove property” behavior when removing child properties in Animator window
- Scene View Camera overlay preview goes out of Scene View bounds when the Scene View is resized vertically
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.
As a general rule, we discourage the use of compatibility mode. Compatibility mode is intended to make porting a project to Render Graph easier, but is not intended to be a permanent feature, and will be deprecated in a future version.
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.