Parity: Block selection box corners are imprecise on renderdragon

1.16.200.57 is already listed in the "Affects Versions" list.

you can see the whole hitbox of a door when hovering over it from max distance as well

If you are on Windows 10 or Xbox on the latest version, the game is already running RenderDragon by default.

This issue is much worse in 1.16.201 Hotfix than what the original images on this report show. The image of the stair attached on 20/Apr/21 shows what it looks like in the current version.

Seems similar to MCPE-90780 and MCPE-31091.

The amount of outline visible appears to be different based on distance and/or angle:

It's fixed in 1.17.10.20

This Bug is Fixed in 1.17.10.21 it should be marked resolved.

Can confirm that it is fixed

This can still be reproduced with a spyglass.

affects 1.17.0

It being imprecise when looking through spyglass isn't a renderdragon specific issue. It also affects platforms that don't have renderdragon yet like Nintendo Switch and Mobile

Hey, not using spyglass here on the 1.17.0 update, and I still see it.

@unknown, you might be on to something because the spyglass issue even appears in the Java Edition (potentially giving a reason to remove "on renderdragon" and "Parity: " from the issue summary), but there's no telling if this is triggered by the same code just at different levels of precision. For example, looking through a spyglass shrinks the field of vision to levels previously impossible. This FOV would not typically appear in gameplay, and would be a disorienting nightmare to play with normally (just think of someone trying to play Minecraft with a 30° view of their environment), so it might have not been considered during development.

As for 1.17.0, the only areas where this cannot be reproduced is in the betas, which currently have the version number 1.17.10. With that, the change might be implemented in the next hotfix or some time later.

This bug *seems* to be patched in 1.17.10.21/22 but on java it can also be see. With a spyglass

Like MCPE-121533 this is fixed in 1.17.10 on Windows 10. However, you need to check if the bug is fixed on other platforms.

@unknown, this is still apparent in 1.18.31 with a low FOV​ (30.00°) or a spyglass.

30.00° FOV:

Spyglass:

19.0, still visible.

30.00° FOV:

Spyglass:

The bug is apparent as in the above comment in 1.19.2 (I don't think I need to continue to add screenshots).