mojira.dev

Veka0

Assigned

No issues.

Reported

MCPE-173926 Minimizing Android Minecraft application breaks deferred pipeline auto exposure Fixed MCPE-173922 Flickering shadow artefacts on Android deferred pipeline Fixed MCPE-173919 Black sun when using deferred pipeline technical preview Fixed MCPE-173914 Android version renders at reduced resolution Invalid

Comments

Just found out that this seems to be an issue with games on Samsung devices in general and not with Minecraft in particular. After following the steps described here (installing Game Booster Plus extension and setting resolution to 100%) it fixed the issue on my device. This post also mentions the same problem, all games published on Google Play run at reduced resolution on Samsung devices by default.

I used a graphics debugger to capture a frame of the game and check it's framebuffer resolution. It was also visible on screenshots of the game, as they are not pixel perfect and instead look slightly blurred. Not just the edges of polygons but textures as well. Additionaly just now I checked with Samsung's feature GPUWatch which overlays GPU information on screen, including framebuffer resolution, and the result was the same - reduced resolution. I can attach debugger capture and/or screenshots with GPUWatch enabled if this can help.

Added example pack and updated steps to reproduce

Added new images and videos from different devices to the report. Also, I tried editing shaders and I think I found a fix for this bug, at least it completely solved it for my device. Although I'm not sure if I can post material file here or include shader code snippets. Please let me know if and how I can post this information here.


Reply from @unknown:
Yes, you can include code snippets here. Simply edit the Description and paste a short code snippet into it, and/or provide a description of your edits. (You can delete this entire comment when you do that).

@magwar my device supports OGLES 3 and the game is running with that version, you can tell that because of ESSL_310 in the debug text and the graphics debugger showed "#version 310 es" in shader source. Video was captured on a flat world, but I tried making new flat worlds a few more times and got the same result. This bug appears to be quite common on android devices, I've seen a few examples of it from other people, I can ask them to provide device model and/or screenshots with debug information if this helps. I should also mention that I've gotten it working 2 or 3 times out of 20 or 30 that I tried joining a world, it seemed to happen randomly and on the next join it would break again.

Edited to include windows platform