Skip to content
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

[nvidia / vulkan / explicit sync] completely unplayable explicit sync issues when playing minecraft 1.8.9 with gamescope #1701

Open
3 of 6 tasks
fxzzi opened this issue Jan 9, 2025 · 3 comments

Comments

@fxzzi
Copy link

fxzzi commented Jan 9, 2025

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

Recording_from_25.0109_11.26.09-scaled.mp4

as you can see from the above video, playing minecraft 1.8.9 with gamescope is unplayable.
The above video was shown using zink, where the issue is at its worst, but the issue also occurs on the native opengl, where the ui and environment flickers very briefly. Nowhere near as bad but its still an issue.

You can see in parts of the video the UI of the game starts disappearing, parts of the environment do not render, my character stops rendering at some point, the game completely freezes, only showing a mess of new frames on the top of the screen.

Steps To Reproduce

  1. Using prism launcher, create an instance of minecraft 1.8.9, enabling zink (or leave on default, the issue still occurs on opengl, just less severe).
  2. Enable gamescope as a wrapper command, the exact command used here was gamescope -f -W 2560 -H 1440 -w 2560 -h 1440 --force-grab-cursor -r 170 --force-windows-fullscreen --
  3. go into any singleplayer, multiplayer etc world and it should exhibit the insane flicker that I am having.

Hardware information

- Distro: "NixOS 25.05 (Warbler)
- CPU: Ryzen 5 5600x
- GPU: NVIDIA Geforce RTX 3070
- Driver Version: 565.77 (both open and closed kernel modules exhibit this issue)

Software information

- Desktop environment: Hyprland v0.46.2
- Session type: wayland
- Gamescope version: gamescope version 3.16.1 (gcc 14.2.1)
- Gamescope launch command(s): `-f -W 2560 -H 1440 -w 2560 -h 1440 --force-grab-cursor -r 170  --force-windows-fullscreen`

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

Video attached above showcases the very apparent issue

@matte-schwartz
Copy link

Have you tried #1671?

@fxzzi
Copy link
Author

fxzzi commented Jan 9, 2025

Hi,

just tried it right now. Seems to be no change with that env var set.

edit: that also only seems to change something for vulkan. I mentioned in the original post that a similar but much less severe version of this bug occurs on opengl too. Disabling gamescope and both work perfectly however.

@matte-schwartz
Copy link

Yes, it's only for Vulkan, but it was worth checking to make sure it didn't make it match OpenGL behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants