[MCPE-14297] Depth off in Gear VR version Created: 29/Apr/16  Updated: 02/Jun/16  Resolved: 02/Jun/16

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 0.14.2
Fix Version/s: None

Type: Bug
Reporter: Sandra Hiltz
Resolution: Works As Intended Votes: 0
Labels: None

Attachments: JPEG File default mode.JPG     JPEG File immersive mode.JPG    
Confirmation Status: Unconfirmed
Platform: Phone - Android - Samsung Other (Specify in description)

 Description   

When playing Minecraft PE in Gear VR full immersive mode the depth scaling is way off on the X & Y directions vs the Z direction, so height wise things look tall where expected but how far away is way off, for example I have a very large room in my game, playing it normally it looks very large, but in Gear VR immersive mode the room looks very small in comparison, maybe 1/3 to 1/4 the size expected. This also shows on stairs that look extremely steep due to the depth issue. Height scaling also seems somewhat off vs non immersive, no where to the extent of the X & Y direction depth, but things seem a bit shorter than expected.

This is on a Galaxy S7 edge in the consumer edition gear VR.



 Comments   
Comment by AMAN4700 [ 02/Jun/16 ]

This issue works as intended. If you have a request for Minecraft Pocket Edition, please go to the Minecraft Forums -> MCPE: Suggestions.

Comment by Sandra Hiltz [ 02/May/16 ]

Yup, I did turn on the 3d rendering mode right away when I started playing so that isn't the cause of it. I took pictures thru the gear VR lens with another phone and attached them to show how different the scale looks, both are standing in the same spot, I just tapped the touch pad to switch between default and immersive mode, as you can see thru the picture the immersive mode makes the room look tiny by comparison.

Comment by Nic Tierman [ 02/May/16 ]

3D rendering is disabled by default to preserve performance on lower spec devices. Did you try turning it on in the settings?

Generated at Sat Jan 11 15:03:12 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.