-
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Games are slow to start or crash #23
Comments
Looks like something malicious. @ivan-hc, please take notice. |
Reported. |
@kenderipa You only have this issue with the appimage right? Can you try with conty as well? I've used the appimage with BeamNG (proton) and CS2 (native) and haven't had issues. |
With conty.sh it looks exactly the same. |
because this AppImage is based on conty.sh, to bundle this Arch Linux container into an AppImage allow to use AppImage-specific features, such as .config and .home directories that prevent creation of dotfiles in your $HOME directory. I have choosen Conty because its the only portable Arch Linux that I have found that supports 3d hardware accelleration (if you use Nvidia, like me, you will have a slower startup, because Conty creates and saves a layout with portable Nvidia drivers, as Flatpak does). |
So no remedy for this porblem? Because yes, I'm using nVidia. |
Really, your issue seems to be similar to #15 and I don't think its an issue with the Nvidia drivers, in your cases. If the issue is only with third-paty games (not the native ones) I don't really know what is the solution, @Samueru-sama is the expert of Steam here, also if this repo have my name, the 80% of the tests and improvements come from him. In the meantime, would you try to run them using my Bottles AppImage instead? https://github.com/ivan-hc/Bottles-appimage |
The issue is with native games, too. |
I also just tested project wingman (proton) and it works without issues. @kenderipa What are the specs of your PC? besides nvidia being an issue the other thing that comes to mind is that the appimage uses more ram. |
I have 32 gigs of it :) |
So this issue should be moved to https://github.com/Kron4ek/Conty Also, I don't know what version of Nvidia drivers you have, I'm not a gamer but when I had Nvidia drivers installed (I can't install them anymore on Debian Testing, modules are too old for newer kernels, I use Nouveau now) I remember that also other AppImages based on Conty were slow at startup, try to perform the same test with my VirtualBox, Gnome Boxes and Bottles. If they are still slow, the issue is with Conty. Or maybe with all AppImages based on Arch Linux containers, or with portable Arch Linux containers in general, and this can be related to the issue we have here ivan-hc/ArchImage#20 |
I'll do it.
You couldn't for a while, but now they've updated the drivers, and they're compatible with newer kernel version again, so you can.
No, that's probably a Conty issue. I'll test it with Bottles when I have time. |
I close this for inactivity |
@kenderipa The appimage has been updated and now uses a totally different method, let us know if the issue is still present. |
Actually, the problem has miraculously disappeared a couple of days ago, not after an AppImage update, but after the internal Steam update. But I'll try it nonetheless. |
But just so you know: the game that I'm playing right now (Torment: Tides of Numenera) freezes while loading with the SquashFS version and runs very slowly (~10 FPS) with the DwarFS version. I'm sticking with a Conty version for now. |
Anything on the terminal that doesn't show on the conty appimage? Sounds like the game isn't using your nvidia gpu. |
@kenderipa I tested with a GTX1060 and it correctly downloads the nvidia drivers and I dont see any performance issues: I did notice however that it uses the same |
I'm not sure, excactly, where is the Conty folder in my case, since $XDG_DATA_HOME is not set. I've found and deleted ~/.local/share/Conty, nothing changed. |
Yep, no nVidia libraries. /tmp/.mount_kOA6UXiT/Run.sh: line 442: ldconfig: command not found |
I think Ivan had a similar issue with Archimage that not all systems have |
@Samueru-sama its enough you include |
Turns out the AppImage actually already contains its own The
And the real ldconfig was renamed to |
The problem here is that this version of the driver (535.216.03) is not in any of the nvidia mirrors...
And the problem here is that this system doesn't have https://github.com/VHSgunzo/runimage/blob/main/rootfs/var/RunDir/Run.sh#L442 @kenderipa |
@kenderipa Try again please, you don't have to download the appimage again just in case. |
That's Debian Trixie. The driver version is probably the one patched by the Debian team, hence the strange numbering. ldconfig is in /sbin, but /sbin is not in the PATH. |
Ooh, it has downloaded nVidia drivers now. Looks like the system needed a restart. The game runs normally, too. Thanks! |
@Samueru-sama, after last update the game is again running slowly. Logs look as follows: Steam log`Ignoring invalid max threads value 4294967295 > max (100000). [ INFO ][2025.02.24 12:58:14]: Found RunImage internal config: Run.rcfg [ INFO ][2025.02.24 12:58:14]: Autorun mode: steam-screensaver-fix-runtime [ INFO ][2025.02.24 12:58:14]: Found xorg.conf in: '/etc/X11/xorg.conf' [ INFO ][2025.02.24 12:58:14]: Host /usr/share/icons is shared! [ INFO ][2025.02.24 12:58:15]: Host /usr/share/fonts is shared! [ INFO ][2025.02.24 12:58:15]: Host /usr/share/themes is shared! [ INFO ][2025.02.24 12:58:15]: Mounting the nvidia driver image: 535.216.03.nv.drv bin_steam.sh[7647]: Setting up for debugging, not logging to console-linux.txt bin_steam.sh[7647]: Setting up for debugging, not logging to console-linux.txt bin_steam.sh[7647]: Setting up for debugging, not logging to console-linux.txt steam.sh[7647]: Running Steam on arch rolling 64-bit steam.sh[7647]: STEAM_RUNTIME is enabled automatically setup.sh[7693]: Steam runtime environment up-to-date! steam.sh[7647]: Log already open steam.sh[7647]: Using supervisor /home/kender/.local/share/Steam/ubuntu12_32/steam-runtime/amd64/usr/bin/steam-runtime-supervisor steam.sh[7647]: Steam client's requirements are satisfied steam.sh[7647]: WARNING: Using default/fallback debugger launch steam_sdl_injection.sh /home/kender/.local/share/Steam/ubuntu12_32/steam -srt-logger-opened CProcessEnvironmentManager is ready, 6 preallocated environment variables. [2025-02-24 12:58:17] Startup - updater built Jan 28 2025 00:50:36 [2025-02-24 12:58:17] Startup - Steam Client launched with: '/home/kender/.local/share/Steam/ubuntu12_32/steam' '-srt-logger-opened' 02/24 12:58:17 minidumps folder is set to /tmp/dumps 02/24 12:58:17 Init: Installing breakpad exception handler for appid(steam)/version(1738026274)/tid(7857) [2025-02-24 12:58:18] Loading cached metrics from disk (/home/kender/.local/share/Steam/package/steam_client_metrics.bin) [2025-02-24 12:58:18] Using the following download hosts for Public, Realm steamglobal [2025-02-24 12:58:18] 1. https://client-update.fastly.steamstatic.com, /, Realm 'steamglobal', weight was 900, source = 'update_hosts_cached.vdf' [2025-02-24 12:58:18] 2. https://client-update.akamai.steamstatic.com, /, Realm 'steamglobal', weight was 100, source = 'update_hosts_cached.vdf' [2025-02-24 12:58:18] 3. https://client-update.steamstatic.com, /, Realm 'steamglobal', weight was 1, source = 'baked in' [2025-02-24 12:58:18] Verifying installation... [2025-02-24 12:58:18] Verification complete UpdateUI: skip show logo Steam logging initialized: directory: /home/kender/.local/share/Steam/logsXRRGetOutputInfo Workaround: initialized with override: 0 real: 0xefe47370 Importing game controller configs (process:13371): GLib-GObject-CRITICAL **: 13:01:35.201: g_object_unref: assertion 'G_IS_OBJECT (object)' failed |
The log says that the nvidia driver is being used, now I don't know if that's the nvidia driver that was downloaded of the nvidia driver from the host. check If not check that your actual nvidia drivers work like they should, with vkcube maybe? @VHSgunzo might know more. |
Deleted everything from ~/.local/share/runimage_nvidia. The game still runs slowly. vkcube spins the cube fluidly, can't say anything more. |
@Samueru-sama @kenderipa
|
https://github.com/ivan-hc/Steam-appimage/releases/tag/1.0.0.82-1 If you asked where on the system, I have no idea xd. |
@Samueru-sama @kenderipa
|
@kenderipa We are at the pkgforge discord btw, troubleshooting is likely quicker thru there. We double checked with another nvidia user and there were no problems 🤔 |
kender@Kender:~$ steam rim-shell -c nvidia-smi +---------------------------------------------------------------------------------------+ Also, I'm not using Discord and, if possible, I would like to not use it further on. |
I don't see a problem with the nvidia driver in the container, I also checked this appimage myself and didn't notice any performance degradation. |
@kenderipa And why are you using such an old driver? Your card supports the latest Nvidia driver and here are the current driver branches:
Speaking of which. Modifying the nvidia driver is forbidden by their own license and the source code of the userspace part of the driver is closed. There is no way the Debian team could modify the nvidia driver. |
This is the version available from the Debian repository. I still think Debian (or nVidia itself?) backports changes from the recent driver to the 535 version, so the driver isn't that old. The size comes a bit later when I'm at my PC. |
No, that's not true, the most nvidia can "backports" is vulnerability patches. And you seem to think too highly of debian) as I said, no one is allowed to modify the nvidia proprietary driver. |
kender@Kender:~$ lsd ~/.local/share/runimage_nvidia/535.216.03.nv.drv -la |
@kenderipa
This will download the driver image with all the necessary libraries. And in the future you can run steam as usual. |
@VHSgunzo, after deleting and redownloading the image (which is now 333 Megs) everything works fine. Thanks for the troubleshooting! |
Hello,
I've found time for a small test (three games: Psychonauts 2 (native), Murdered: Sould Suspect (Proton), KotoR II (native)). Looks like the games mostly start, but onlt after they are stopped through Steam client (first two). Others just crash (third one), and I'm not sure where to find logs for them. Logs are neither in game directory nor in the ~/.local/share folder.
Logs for the games that CAN be launched (Murdered: Soul Suspect, Proton), written by Steam client in stdout:
After clicking Start, before clicking Stop:
After Stop is clicked
But still, it looks very promising. Thanks to you, Steam is moving in the right direction :)
The text was updated successfully, but these errors were encountered: