Search Issue Tracker
Fixed in 2017.2.0f3
Votes
1
Found in
5.6.0f3
Issue ID
896253
Regression
Yes
[Android] [GearVR] Cannot change Anti-aliasing settings in runtime
Steps to reproduce:
1) Download attached project '56f3AAIssue.zip' and open in Unity
2) Create OSIG file for testing device
3) Enable Gear VR Developer Mode
Settings >> Applications >> Application manager >> Gear VR Service >> Storage >> Manage Storage >> Developer Mode
4) Build and run 'AATest' scene on a device
5) Touch the screen to change AA level
Note: Look at the screen, AA level will not change after pressing on it
Reproduced with:
5.6.0f2, 5.6.0f3, 2017.0b1
Not reproduced with:
5.5.3p1, 5.6.0f1
Regression from:
5.6.0f2
DUT:
Samsung SM G925F (Galaxy S6 Edge), OS:6.0.1, CPU:arm64-v8a, GPU:Mali-T760, Build:samsung/zeroltexx/zerolte:6.0.1/MMB29K/G925FXXU5DQA7:user/release-keys
Note:
Works fine if Virtual Reality Supported is disabled
Fixed in : 5.6.1p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment