Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
6000.0.61f1
6000.2.10f1
6000.3.0b8
6000.4.0a4
Issue ID
UUM-125992
Regression
No
"Camera" component's FSR2 Mode override does not change the FSR2 Mode when the "Use FSR2 Custom Attributes" option is disabled in the "Camera" component
Steps to reproduce:
1. Open the attached “IN-122612_FSR2Test (2) (2).zip“ project (link in the internal comments)
2. Open the “OutdoorsScene”
3. Enter Play mode
4. Press the left mouse button on the Game view to change the FSR Mode and ScaleFactor (while observing the text displayed in the Game view)
Expected result: The FSR Mode changes with each click to 1, 2, 3 and 0 (it wraps around), and the ScaleFactor (and resolution) change to “0.600x0.600” (2304x1296), “0.500x0.500” (1920x1080), “0.400x0.400” (1536x864), and “0.700x0.700” (2688x1512) accordingly
Actual result: The FSR Mode changes with each click to 1, 2, 3 and 0 (it wraps around), but the ScaleFactor (and resolution) remain unchanged at “0.700x0.700” (2688x1512)
Reproducible with: 6000.0.61f1, 6000.2.10f1, 6000.3.0b8, 6000.4.0a4
Reproduced on: Windows 11 Pro (25H2)
Not reproduced on: No other environment tested
Workaround:
1. Select the “Main Camera” GameObject in the Hierarchy
2. In the Inspector, enable the “Use FSR2 Custom Attributes” option under the “Camera” component > “Rendering” > “HDRP Dynamic Resolution” > “AMD FidelityFX Super Resolution 2.0 (FSR2)” (disabling the option again will bring the ScaleFactor (and resolution) back to the one set in the current HDRP asset)
Notes:
- Reproducible in the Player
- Could not test with URP (FSR 2 is not yet supported in URP)
- When setting the Quality Mode for FSR2 in the HDRP asset, the correct mode is applied but the “Camera” component’s override is ignored. If you change the Quality Mode in the “Camera” component’s dropdown, it has no effect on the Game view and it just uses the HDRP asset’s value
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
Add comment