Skip to content

🐞 Loop β‰₯1.4 lags and sometimes holds inputs hostage in MinecraftΒ #1001

@Endy3032

Description

@Endy3032

Bug Description

Just updated Loop to 1.4.1 today and noticed some weird behavior while playing Minecraft. When moving the mouse while holding down LMB and W/A/S/D, the mouse will lag around significantly as if something is holding the input data hostage until a bit later, making the camera snap around instead of moving smoothly. Sometimes the W/A/S/D key and/or LMB will also be "stuck" down despite already being released, making the character move continuously in a direction and/or breaking blocks continuously without any user input. This does not happen in v1.3.

Affected Scope

Performance

Steps to Reproduce

  1. Load Minecraft up and set a very high FPS limit (in my case w/ shaders on, 250FPS or Unlimited both work, the higher the difference between the actual fps and the fps limit the higher chance it happens, sometimes switching between 250 and ∞ triggers the bug immediately)
  2. Hold down LMB and move the mouse around
  3. Keep LMB held down and start moving randomly with WASD
  4. Notice how the camera starts spazzing out and lag-snaps to different positions trying to catch up with the mouse movement

Reproducibility

Often (β‰₯70%)

Expected vs Actual Behavior

Expected: the cursor and the camera to move around smoothly with no hiccups

Actual: the camera lags around and sometimes inputs are held hostage

Screen Recordings / Screenshots

c1.mov
c2.mov

also notice the second clip at ~0:06 i did not press s but the s seemingly got delayed from minecraft to raycast turning the search from loop to loops, and later in the same clip raycast sometimes didnt open immediately while the bug is happening

Severity

Major (workaround exists)

macOS Version

Tahoe 26.2

Loop Version

Version 1.4.1 (1677)

Did You Try the Development Build?

No

Additional Context

Happens on both Logitech M720 (bluetooth and unifying) and trackpad so not a hardware issue
Can not reproduce when using Loop 1.3 or when Loop is not running
The issue is also present on the oldest gh actions artifact that is still downloadable
Switching between 250fps and unlimited usually activates the bug right after

Final Checks

  • My issue is written in English.
  • My issue title is descriptive.
  • This is a single bug (multiple bugs should be reported individually).
  • I have looked to see if this is a duplicate of another bug report.
  • I can help with further investigation.
  • I can help with developing a fix for this issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions