mojira.dev
MCPE-98861

Significant input delay on devices with Render Dragon

Mojang Studios Note

Update 28 Sep 2023: The 1.20.30 update introduced a new "Improved Input Response" option on Windows which the developers hope will resolve the issue for the many users experiencing this issue. The team is investigating solutions for additional platforms to be added in the future.

Update 16 June 2023: Thank you for your patience while we continue to work on a solution for this ongoing issue. Please be assured that we have not forgotten about this bug, and hope to have a solution that will resolve the issue for you without the need for workarounds. We will keep you updated as soon as we have some more news in the changelogs which are published with each update.

This comment also provides a potential workaround for players by adjusting the V-Sync setting manually, which you might find useful.

Simply put, input lag appears to be much much worse in this new beta. Try swinging your view around with a mouse and you will see that your input is delayed even more than it was before this beta. Please do fix this issue in the next beta so Windows 10 getting Render Dragon won't cause issues.

Notes: This seems to be an issue related to Vsync.


Additional information from MCPE-169538 to aid in reproducing:
As already mentioned in a comment of this bug, the engine for Minecraft Bedrock Edition has a fixed frame delay set which leads to noticeable input delay, more prominent the less frames are rendered.

To confirm this, I used RivaTuner to set the framerate to 1 FPS. Now it will be made easily visible that every input you do, will be delayed by 4 frames / 4 seconds. Using the ingame framerate limiter and setting it to 10, a similar delay will be noticed between native limit and RivaTuner limit. This problem therefore is clearly an ingame issue that must be fixed for reducing input delays.

In other versions of Minecraft like Java Edition every input update arrives at the very next frame.


Linked issues

BDS-10412 Camera Movement/Looking Around Resolved BDS-10472 weird bug where if i have my power plugged in my minecraft character doesnt move well Resolved BDS-10503 Input lag/ Input Delay Resolved BDS-10524 Mouse input and screen are not synced Resolved BDS-10785 Reaction Time Resolved

Attachments

Comments 273

LightKnight2311

A way I tested it out was dragging a block in a chest. You can see the input delay as the block is really far behind the cursor. If the input delay was fixed, the block wouldn't be as far behind the cursor.

This relates to MCPE-85756

LightKnight2311

Yeah kinda. However, the input delay discussed in that bug report is mostly because of vsync. If your monitor has a refresh-rate of 60hz, you will experience some input delay. If you have a 144hz or 240hz monitor, you will notice less input delay. This beta, however, is where the input delay is far worse than it should be. The input in 1.16.40 is relatively normal.

Even with vsync off, there is still input delay. Vsync does improve the issue but does not completely fix it.

Is much worse on Windows 10 with 1.16.100.59

263 more comments

If you're still experiencing this or a similar issue, then please create a new report. Please make sure to include the following information:

Steps to Reproduce:
1. (Explain what needs to be done for the issue to happen)
2.
3.

Observed Results:
(Briefly describe what happens)

Expected Results:
(Briefly describe what should happen)

Please also attach any needed commands, add-ons/behavior packs, data packs, resource packs, screenshots, videos, or worlds needed to help reproduce the issue.

Refer to the Bug Tracker Guidelines for more information about how to write helpful bug reports. Bug reports with insufficient information may be closed as Incomplete.

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

Still affects 1.21.23...

This is not fixed, currently affecting from my knowledge both Android versions using gamepad input and PC version. Playing both most recent versions, and I've tested the preview ones too. I don't know why the bot marked this as fixed, but it isnt.
 
 
 

 

I've opened a new bug report regarding this issue with all the important details here MCPE-186474

Can the developers or moderators PLEASE clarify why the status of this issue was changed to "resolved" even though there is no fix version?

Update 1.20.30.20 Preview, the most recent update listed as a "fix version", was released in August 3, 2023, and it DID NOT fix the issue, as reported by several users. The status of this issue was changed to "resolved" in September 4, 2024, 13 months after 1.20.30.20 Preview. No changelog of any update after 1.20.30.20 Preview mentions this issue.

LightKnight2311

(Unassigned)

404775

Confirmed

Multiple

RenderDragon

1.20.0.20 Preview, 1.19.20.22 Preview, 1.17.11 Hotfix, 1.17.10, 1.17.10.21 Beta, ..., 1.20.73 Hotfix, 1.21.10.22 Preview, 1.20.81 Hotfix, 1.21.0, 1.21.21 Hotfix

1.20.30.20 Preview, 1.16.220.51 Beta, 1.20.30

Retrieved