-
-
Notifications
You must be signed in to change notification settings - Fork 969
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(macos): Mouse input broken in-game #2550
Merged
ReenigneArcher
merged 22 commits into
LizardByte:master
from
Hazer:fix/macos-mouse-3d-move
Jun 12, 2024
Merged
fix(macos): Mouse input broken in-game #2550
ReenigneArcher
merged 22 commits into
LizardByte:master
from
Hazer:fix/macos-mouse-3d-move
Jun 12, 2024
+308
−75
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2550 +/- ##
=========================================
+ Coverage 7.98% 9.69% +1.70%
=========================================
Files 88 88
Lines 18039 18070 +31
Branches 8596 8605 +9
=========================================
+ Hits 1441 1752 +311
+ Misses 15828 13491 -2337
- Partials 770 2827 +2057
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Hazer
force-pushed
the
fix/macos-mouse-3d-move
branch
2 times, most recently
from
May 21, 2024 18:30
4c56f31
to
70a2223
Compare
Hazer
force-pushed
the
fix/macos-mouse-3d-move
branch
13 times, most recently
from
May 23, 2024 09:50
30ad1a9
to
aa16e27
Compare
Hazer
force-pushed
the
fix/macos-mouse-3d-move
branch
5 times, most recently
from
May 27, 2024 19:18
8b63136
to
8388a43
Compare
Rebase with #2606 before moving from draft |
Hazer
force-pushed
the
fix/macos-mouse-3d-move
branch
from
June 3, 2024 23:32
8388a43
to
f23f409
Compare
Hazer
force-pushed
the
fix/macos-mouse-3d-move
branch
from
June 3, 2024 23:40
bffa1b3
to
695f06f
Compare
11 tasks
Hazer
force-pushed
the
fix/macos-mouse-3d-move
branch
from
June 12, 2024 00:01
373ef2c
to
24b9db0
Compare
Co-authored-by: ReenigneArcher <[email protected]>
ReenigneArcher
force-pushed
the
fix/macos-mouse-3d-move
branch
from
June 12, 2024 20:01
caeb553
to
84183af
Compare
BayLee4
added a commit
to BayLee4/Sunshine
that referenced
this pull request
Sep 27, 2024
This reverts commit 02ddbef.
BayLee4
added a commit
to BayLee4/Sunshine
that referenced
this pull request
Sep 27, 2024
10 tasks
KuleRucket
pushed a commit
to KuleRucket/Sunshine
that referenced
this pull request
Oct 9, 2024
Co-authored-by: ReenigneArcher <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This issue was initially reported on Discord
Basically, we have 2 main issues:
The behavior can be reproduced on Minecraft Java Edition and Tomb Raider. FPS games are mostly prone, some games may not really have issues, but I bet most 3D FPS are failing.
Screenshot
bug:
fixed:
Issues Fixed or Closed
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.