Summary:
I still have the same issue as #497 in the latest version.
The image of the stereo screen shrinks to 1/4 size in VR mode when I enable 4K display mode (and set the screen resolution to 4k). See also:
Google VR SDK version: v1.50.0 or later (reproduced with v1.170.0)
Unity version: 5.5 or later (reproduced with 2018.2.6f1)
Phone manufacturer, model, and O/S version: SONY XPERIA XZ Premium, Android O
Viewer manufacturer & model: Any cardboard viewer
Steps to reproduce the issue:
Enable 4k display mode (set preferredDisplayModeId for 4k display using Java plugin)
Set the screen resolution to 2160 x 3840 pixels in Unity
Workarounds:
I didn't have this issue when I was using gvr-unity-sdk v1.0.3. I had a workaround to avoid this issue until gvr-unity-sdk v1.40.0 by switching Distortion Correction from Native to Unity in GvrViewerMain. However, this workaround is not available from gvr-unity-sdk v1.50.0 which requires Unity 5.6 or later with the native integration.
Additional comments:
Unity 5.5 or later is not able to use VR mode with 4K display mode due to this issue.
I have been suffered from this issue for almost 2 years, so it will be very grateful if Google can fix it in the next version.
Summary: I still have the same issue as #497 in the latest version. The image of the stereo screen shrinks to 1/4 size in VR mode when I enable 4K display mode (and set the screen resolution to 4k). See also:
https://github.com/m-tukiok/UnityPluginDisplay4k#known-issue
Found using:
Steps to reproduce the issue:
Workarounds: I didn't have this issue when I was using gvr-unity-sdk v1.0.3. I had a workaround to avoid this issue until gvr-unity-sdk v1.40.0 by switching Distortion Correction from Native to Unity in GvrViewerMain. However, this workaround is not available from gvr-unity-sdk v1.50.0 which requires Unity 5.6 or later with the native integration.
Additional comments: Unity 5.5 or later is not able to use VR mode with 4K display mode due to this issue. I have been suffered from this issue for almost 2 years, so it will be very grateful if Google can fix it in the next version.