Search Issue Tracker
Fixed
Fixed in 6000.3.4f1, 6000.4.0b5, 6000.5.0a5
Votes
2
Found in
6000.3.0f1
6000.4.0a5
6000.5.0a3
Issue ID
UUM-130075
Regression
No
Error "Failed loading overlay "FPS Limit"!" is present when MainToolbarSlider min value greater than 0
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. In the Toolbar context menu select “FPS Limit“ (3 dots on the right side of Play Mode and Pause Play Mode buttons)
4. Observe the Console
Expected result: No Errors exist
Actual result: Error “Failed loading overlay "FPS Limit"!“ is present
Reproducible with: 6000.3.0f1, 6000.4.0a5, 6000.5.0a3
Could not test with: 6000.0.63f1 (Assets\Scripts\Toolbar.cs(7,19): error CS0246: The type or namespace name 'MainToolbarElement' could not be found)
Testing environment: Windows 10 Enterprise 21H2
Not reproducible 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
- 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 6000.4.0b5):
Fixed in 6000.4.0b5
Resolution Note (fix version 6000.3.4f1):
Fixed in 6000.3.4f1