steam-for-linux VS SDL

Anyone else noticing this? I don't believe I'm going insane. For a while now my download speeds, regardless of chosen server, are always slower in the Linux client compared to in Windows. Is the only appropriate place to post about this here -> https://github.com/ValveSoftware/Steam-for-Linux ? Would be great to know that I'm not the only one being affected.

https://github.com/ValveSoftware/steam-for-linux/issues Its seems to be a problem happening only to Nvidia GPUs. Not only Mint but many other distros A temporary solution is to open Steam from the Terminal using "steam -vgui"

I just spent a few hours working on that problem that Steam takes very long to appear. I did not have xdg-desktop-portal-gnome installed, and Steam is the only application that has that problem, so it's not the one from the update forum post. What my (and probably your) problem is, is this one: https://github.com/ValveSoftware/steam-for-linux/issues/9780. Some bug where CEF gets stuck in a loop. When I executed steam --reset an error about steamwebhelper and glibc appeared like 50 times, each taking a few seconds.

Hey I had the same issue - are you running this on Linux? On my arch machine I had this problem and was able to resolve it via the advice in this thread: https://github.com/ValveSoftware/steam-for-linux/issues/9640

might be related #9805

Steam crashes at launch with libgudev 238 · Issue #9805 · ValveSoftware/steam-for-linux

Relevant open issue from 2014: https://github.com/ValveSoftware/steam-for-linux/issues/3372

The linked project doesn't use any ObjC files at all. SDL2 has a bunch of Cocoa files[1] so you did use Cocoa even if unknowingly.

[1] https://github.com/libsdl-org/SDL/tree/main/src/video/cocoa

Correct. It's explained here:

https://github.com/libsdl-org/SDL/pull/9345#issuecomment-201...

XWayland has special hooks into the compositors that normal wayland clients don't get.

Found about this through the release of SDL 3: https://github.com/libsdl-org/SDL/blob/main/build-scripts/SD...

https://github.com/libsdl-org/SDL/blob/main/include/SDL3/SDL_events.h

If that app ran in a 640x480 mode, memory accesses would be just as fast as the VGA applications 25 years ago, correct?

I think there's a lot more going on than that. Here's SDL's current pixel access code:

https://github.com/libsdl-org/SDL/blob/main/src/video/SDL_su...

We use the code examples throughout the article. The ellipsis characters "...." in the code were added by the author of the article. You can find the source files on the official GitHub of libsdl. In addition, each fragment has a reference to a specific area in the code. By the time this article is published, many errors will have already been fixed thanks to the issues we opened (for example, here and there). However, the links in the examples point exactly to the code you see in this article. Not only do we enjoy teasing developers but we also like making their projects a little bit better!

FetchContent_Declare(SDL2 GIT_REPOSITORY https://github.com/libsdl-org/SDL.git GIT_TAG release-2.28.3 ) FetchContent_MakeAvailable(SDL2)

It's not that difficult, I recently started learning to use graphics APIs myself. OpenGL is for linux, etc., directx for windows and vulkan for all platforms. I read through a bunch of forums yesterday and decided to go for vulkan (here is a link to the sdk) for my next small projects because it can run on all platforms. I would recommend to watch a basic tutorial series (like this one) for the graphics api itself to get an understanding of whats going on. And on top of that I use SDL2 for eventhandling and ImGui for the graphical user interface. Here is a link to a guide for setting up vulkan on your platform in case you would go for it.

SDL (which will be bumped to SDL3), straight from the authoritative https://github.com/libsdl-org/sdl