Search Issue Tracker
Fixed in 5.0.X
Votes
1
Found in
4.2.0f4
Issue ID
553399
Regression
No
Changing quality settings in runtime works incorrectly
Changing quality settings in runtime results in material brightness change. Materials can become brighter or darker.
Tested device:
Samsung Galaxy S2 (GT-I9100) with Android 4.0.3
Unity Versions:
4.1.5f1 (ed5ea3281df6)
4.2.0f4 (38efbd14869d)
4.3.0a5 (796335dfc9e5)
Comments (1)
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
- [macOS] Rendering Debugger Volume's "Component" dropdown is opened with a big offset when "Component" field is set to any "Sample Scene"
- [iOS] Metal API validation error thrown when MSAAx2 and Depth&Color Texture are enabled
- Pressing “Open” button in Inspector > “High Quality Lines” Override throws “Item m_RenderPipelineSettings.supportHighQualityLineRendering not found” warning
- Overlays are immediately undocked when the Overlay is docked to the right side of Scene View and the Overlay's Handle is clicked
- Crash in PhysicsManager::IgnoreCollision when a GameObject with “Is Trigger” enabled enters a collision in a specific project
3d_Game_Ready
Sep 26, 2014 06:43
Not sure if it's related but users report a black screen (as good as a crash) when the anti-aliasing is changed at runtime. Devices affected: Galaxy Note 3, Galaxy S5, Motorolla Droid Maxx and the HTC One. I didn't pick it up on my personal test devices and luckily launched a beta version otherwise there'd be red faces in the office.