Announcement

Collapse
No announcement yet.

SDL2 Reverts Its Wayland Preference - Goes Back To X11 Default

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • RealNC
    replied
    Originally posted by Myownfriend View Post
    That person who created that issue even states that they only noticed the input lag in Retroarch and some in the discussion believe it's a Retroarch issue.
    The issue is that retroarch tries to reduce latency. Other games or game-like just use whatever they're given, in this case 4 swapchain images. In retroarch you can configure the swapchain size. But it doesn't work in this case. Even if you set it to 2, you get 4.

    Leave a comment:


  • bug77
    replied
    Originally posted by Volta View Post

    It turns out mediocre nvidia driver is still POS and software like Steam were not updated to Wayland, yet. You could at least read the article.
    You could, but then you'd stumble upon "libwayland event overflow, libdecor not handling plugin load failures", which would interfere with ranting.

    Leave a comment:


  • ColdDistance
    replied
    Originally posted by mangeek View Post

    NVIDIA's Linux strategy has failed so spectacularly that it's causing collateral damage to the rest of the open-source ecosystem. I think NVIDIA really needs to cooperate with and support the Nouveau team, or get a fully-functional open-source Vulkan driver out there. We need something, they can still keep their proprietary driver for corporate support, GRID VDI, and other big money projects. I just want to be able to use their products in a reasonable way that doesn't make me jump through hoops or bend my system into some alternate universe.
    NVIDIA must be forced to embrace a dual support like the AMD one.

    Leave a comment:


  • Weasel
    replied
    Originally posted by Myownfriend View Post
    Not even remotely. Plus you're really not qualified to say what design decisions are or aren't asinine. You don't code. You took credit for fixing some stuff because you pointed out some bugs but other people fixed them.
    Why does it matter if he codes? Design decisions that matter if you code are those internal to a project, not to an end user. If a design decision impacts end user then nobody gives a shit if he can code or not.

    In fact that's probably the issue here, since Wayland developers (those who develop the protocol I mean) are a bunch of retards who thinks the world revolves around their computing needs and reject any sensible feature request that other users want out of their display server/protocol because they use it on X11.

    Claiming "it's not needed" makes them a bunch of lunatic fringe fucks.

    Leave a comment:


  • MrCooper
    replied
    Originally posted by RealNC View Post
    Wayland is still not viable, even with open source drivers. Look at this nonsense:

    https://gitlab.freedesktop.org/mesa/mesa/-/issues/6249
    That's a Mesa issue, not a Wayland one.

    Originally posted by abu_shawarib View Post
    Is it me or did everyone just ignored the mentioned bug in libwayland?
    It's more like a missing feature than a bug per se, though it makes avoiding accidental disconnects of unresponsive clients tricky for Wayland compositors.

    Originally posted by billyswong View Post

    CSD supporters probably don't think one may want to move / resize windows for hanged / busy applications.
    A decent Wayland compositor should allow moving surfaces of unresponsive clients, e.g. mutter does by dragging the mouse while holding the Super key (or via the Alt-Space menu).

    Resizing a Wayland surface requires active involvement of the client, so that couldn't work with SSD either.

    Leave a comment:


  • Myownfriend
    replied
    Originally posted by birdie View Post
    I'll repeat this for the 50th time. That link doesn't add anything to the conversation. In what way, shape, or form do you think that's proving that Wayland's design decisions are asinine?

    Originally posted by birdie View Post
    Wayland is held back by its asinine design decisions and asinine implementations.
    Not even remotely. Plus you're really not qualified to say what design decisions are or aren't asinine. You don't code. You took credit for fixing some stuff because you pointed out some bugs but other people fixed them.

    Originally posted by birdie
    Linux users: "We can hate and we love it so much!!!!!!!"
    Linux users: "It's always something other than us and Linux itself who's responsible for all our issues!!!"

    Pathetic as ever.
    How is your sweet baby Nvidia not a huge part of the barrier to Wayland adoption? Is it Wayland's poor design that's preventing OBS from working in Wayland on their hardware? Nvidia's driver doesn't support EGL_NATIVE_RENDERABLE.

    EGL is not part of Wayland or even really a part of Unix. It's a Khronos standard that's been around since 2003 that's used by Wayland, X11, Mir, Android, and even Blackberry 10. Nvidia themselves have contributed extensions to the standard. EGL_NATIVE_RENDERABLE has been part of the standard from the very first version. Of the aforementioned things that use EGL, X11 is the only one that predates it.

    Are you suggesting that Nvidia isn't at fault for not supporting a property and that it's actually Wayland and OBS's fault for using a standardized API used by a bunch of other people that was already already supported by many drivers?

    Wayland compositors currently can't support blue light rejection features in a Wayland session on Nvidia hardware. This is because Nvidia's driver doesn't support the GAMMA_LUT DRM property. They can do it in Xorg through XRANDR which is handled by the driver. In most drivers, this changes the DRM properties, in Nvidia's driver it changes a private set of properties.

    People on Nvidia cards have looked at stuff like that and thought they must be Wayland limitations, but they're not. They're the result of bad support for Linux and EGL by Nvidia. They just mainly effect Wayland sessions. I saw mainly because Nvidia's lack of support for dma-buf and some EGL extensions prevented Firefox's Webrender and WebGL acceleration from working in both Wayland and X11 sessions for awhile.

    Originally posted by birdie
    Linux users: "We've chosen an obscure open source OS, one of many, but the whole world owes us because of this choice!!!!"


    The last thing I mentioned isn't an issue with supporting an OS, it's an issue with supporting the kernel. But you're claiming that Linux OSs are obscure. How? They're deployed on not just a lot of servers but also at FX houses. It's being used by a handheld system made by one of the biggest companies in gaming and it's mentioned in all the coverage of it. I'm not gonna include Android and Chrome OS devices but those use Linux, too.

    You'll probably claim that "Yea, well yea but if went up to a random person on the street they wouldn't know what Linux is". Many also wouldn't know what Nvidia is. That doesn't really matter though. The reality is that Nvidia and Linux are both big and important to the world of computing.

    Most importantly when talking about Nvidia and Linux, Nvidia's makes their own development boards for their Tegra chips that run Ubuntu and even they don't use the drivers that we're given on desktop.

    Originally posted by birdie
    13 likes from freeloaders/haters.
    You made an account (multiple accounts) on this site, a site about Linux and open source news, and have made countless posts about your extreme distaste for Linux users and the open source community. How are you calling us haters?

    And how are we freeloaders? Many of us payed for Nvidia's fucking hardware and many who haven't would be willing to if it worked properly with the software they want to run.

    OSS community: Here you go. You can use this OS and software for free. Sorry for any issues you might have on your Nvidia card. We just wish Nvidia would work with us more.
    birdie: You fucking hateful, scumbag, freeloaders. You should be lucky Nvidia works with you at all. You think they owe you something just because they use Ubuntu on their Jetson boards? Nobody even knows who you guys are.
    also birdie: *uses Fedora*
    Last edited by Myownfriend; 19 April 2022, 07:10 AM.

    Leave a comment:


  • -MacNuke-
    replied
    Originally posted by RealNC View Post
    Wayland is still not viable, even with open source drivers. Look at this nonsense:
    https://gitlab.freedesktop.org/mesa/mesa/-/issues/6249
    It's impossible to write games without input lag.
    With the way things have been going these last 5 years or so, it appears The Year Of The Wayland Desktop will probably arrive in about 20 years.
    Fun to see that the result of the tests linked in the issue shows that a modern, composited desktop on Xorg is way slower than a Wayland desktop.
    Last edited by -MacNuke-; 19 April 2022, 05:15 AM.

    Leave a comment:


  • birdie
    replied
    Originally posted by writequit View Post

    No, we just say fuck you NVIDIA and buy AMD instead, why does it upset you so much?
    That's all you can? That makes you a bunch of arseholes.

    Leave a comment:


  • dragon321
    replied
    Originally posted by Raka555 View Post

    Yeah, it is clearly not ready.
    13 years are not enough to get this garbage stable ...
    Wayland protocol is stable since 2012. If we talk about implememntations then it's not like X11 is flawless. Some X11 issues are present since this protocol was created over 30 years ago and some can't be even fixed without breaking compatibility.

    What is more SDL developers pretty clearly stated that their Wayland implementation is stable.

    Originally posted by Raka555 View Post

    Or even just close it ...
    Even with SSD you can't close hanged application just by clicking close button. This button is not supposed to kill application so if application is not reacting to events then it won't react to this button either.

    Leave a comment:


  • Raka555
    replied
    Originally posted by billyswong View Post

    CSD supporters probably don't think one may want to move / resize windows for hanged / busy applications. Or they don't think an application may be busy or hanged.
    Or even just close it ...

    Leave a comment:

Working...
X