Open kenderipa opened 3 weeks ago
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.
@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.
@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).
@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 https://github.com/ivan-hc/Steam-appimage/issues/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
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 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 :)
With conty.sh it looks exactly the same.
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 https://github.com/ivan-hc/ArchImage/issues/20
So this issue should be moved to https://github.com/Kron4ek/Conty
I'll do it.
(I can't install them anymore on Debian Testing, modules are too old for newer kernels, I use Nouveau now)
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.
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
No, that's probably a Conty issue. I'll test it with Bottles when I have time.
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 :)