4 ms·

I also have no ideas how it works, but my guess would be that is actually translates exactly like that into games. Why would the mouse on the desktop have a lat

by ray023 2y ago

I also have no ideas how it works, but my guess would be that is actually translates exactly like that into games. Why would the mouse on the desktop have a latency that games do not have. Linux does not have a real fullscreen mode like Windows has (that I do not use anymore anyway for faster alt-tabbing). So my guess is, the cursor or mouse input gets into games very much the same way as it gets in the desktop.

gsich 2y ago
Hardware cursor might be used in games. You notice the difference on Windows if a GPU does not support it, even on the desktop.
zamalek 2y ago
Wayland has support for games completely taking over the GPU; notoriously critical for VR support. This is basically the same as Windows exclusive full screen. Wine/proton would need to support it, XWayland would need to support it (Wine/Proton are one major step away from native Wayland support: Vulkan), and finally the compositor would need to support it. Gnome is about the worst compositor that you could be testing any of this stuff on, they are comically hostile towards ideas not their own. The chances of this ever working on Gnome are near zero. KDE is pretty good for support, Hyprland seems to be trying to support every under the sun.
- debugnik 2y ago
  > notoriously critical for VR support. This is basically the same as Windows exclusive full screen. D3D12 dropped support for exclusive fullscreen, and I don't think headsets even go through DXGI but their own swap chain APIs. Why do VR games on Linux need the equivalent from the Wayland compositor?
  - account42 2y ago
    VR on X.Org also already bypasses the X server for the VR display.
  - ray023 2y ago
    Can I have the source for this? DX12 dropped exclujsive FS? Why does every game still has this as a option then? Or are you talking about VR specifically?
    - debugnik 2y ago
      Sure, I took it from the docs [1]. Games may show it as an option if the engine itself can support other GPU APIs and the devs working on the options menu don't know or care that this particular settings combination is misleading. [1]: https://learn.microsoft.com/en-us/windows/win32/direct3d12/swap-chains#transitioning-between-windowed-and-full-screen-modes https://learn.microsoft.com/en-us/windows/win32/direct3d12/s...
- NekkoDroid 2y ago
  > Gnome is about the worst compositor that you could be testing any of this stuff on, they are comically hostile towards ideas not their own. The chances of this ever working on Gnome are near zero. GNOME has supported direct scanout for fullscreen apps for a while and drm-lease was implemented not too long ago either.
- ray023 2y ago
  Did not know Wayland has exclusive FS.
  - zamalek 2y ago
    I doubt that Wine would actually request it. Some compositors also have "tearing mode," which is basically as good: the game gets full control of the presentation timing, so vsync/tearing would be determined by what the game wants to do.

by ray023 2y ago

gsich 2y ago

Hardware cursor might be used in games. You notice the difference on Windows if a GPU does not support it, even on the desktop.

zamalek 2y ago

Wayland has support for games completely taking over the GPU; notoriously critical for VR support. This is basically the same as Windows exclusive full screen. Wine/proton would need to support it, XWayland would need to support it (Wine/Proton are one major step away from native Wayland support: Vulkan), and finally the compositor would need to support it. Gnome is about the worst compositor that you could be testing any of this stuff on, they are comically hostile towards ideas not their own. The chances of this ever working on Gnome are near zero. KDE is pretty good for support, Hyprland seems to be trying to support every under the sun.

debugnik 2y ago
> notoriously critical for VR support. This is basically the same as Windows exclusive full screen. D3D12 dropped support for exclusive fullscreen, and I don't think headsets even go through DXGI but their own swap chain APIs. Why do VR games on Linux need the equivalent from the Wayland compositor?
- account42 2y ago
  VR on X.Org also already bypasses the X server for the VR display.
- ray023 2y ago
  Can I have the source for this? DX12 dropped exclujsive FS? Why does every game still has this as a option then? Or are you talking about VR specifically?
  - debugnik 2y ago
    Sure, I took it from the docs [1]. Games may show it as an option if the engine itself can support other GPU APIs and the devs working on the options menu don't know or care that this particular settings combination is misleading. [1]: https://learn.microsoft.com/en-us/windows/win32/direct3d12/swap-chains#transitioning-between-windowed-and-full-screen-modes https://learn.microsoft.com/en-us/windows/win32/direct3d12/s...
NekkoDroid 2y ago
> Gnome is about the worst compositor that you could be testing any of this stuff on, they are comically hostile towards ideas not their own. The chances of this ever working on Gnome are near zero. GNOME has supported direct scanout for fullscreen apps for a while and drm-lease was implemented not too long ago either.
ray023 2y ago
Did not know Wayland has exclusive FS.
- zamalek 2y ago
  I doubt that Wine would actually request it. Some compositors also have "tearing mode," which is basically as good: the game gets full control of the presentation timing, so vsync/tearing would be determined by what the game wants to do.