Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
2017.1.0b5
Issue ID
911311
Regression
Yes
[Daydream] Changing AA at runtime causes screen to freeze
1. Steps to reproduce
1. Open attached project
2. Build to Daydream compatible device
3. Observe freeze when the Anti-Aliasing is changed*
* AA cycles trough (0, 2, 4, 8) every few seconds automatically
Expected behaviour: AA setting successfully changed during runtime
Actual behaviour: Rendering/screen freezes upon AA change
Reproduced on: 2017.1.0b4, 2017.1.0b5
Not reproduced on: 2017.1.0b3
Regression introduced in: 2017.1.0b4
Devices under testing:
Reproduced with:
Google Pixel, OS:7.1.2, CPU:arm64-v8a, GPU:Adreno (TM) 530, Build:google/sailfish/sailfish:7.1.1/NOF26V/3636322:user/release-keys
Not reproduced with:
Samsung Galaxy S6 Edge+, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zenltexx/zenlte:7.0/NRD90M/G928FXXS3CQD3:user/release-keys
Fixed in: 2017.2.0b1
Backported to: 5.6.2p1, 2017.1.0f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
- Display issues in VideoPlayer when using Screen.SetResolution on certain Google Pixel devices
- Crash on Texture::TextureIDMapInsert when opening a specific project
- Null reference exceptions occur when ScriptableObjects saved in the same .asset file are referenced in runtime
Add comment