11/8/2023 0 Comments Steam linux![]() userdata/saves/flatpak/data/.var/app//.steam/steam/package/betaĮxit the file manager and relaunch steam again at ports, it will be updated to the regular version again. Settings/Preferences > Account > Beta Participation - Steam > NONEīut if you can't to do it due to the interface window issue, do it manual:Īt batocera, open the file manager [F1}, and the delete the beta file found in steam/packages: To fix it, you need to rollback to the regular version, but due to the settings issues, you can't rollback using the interface, so you need to manually delete the beta file to goes back to the standard steam client version Unable to change any settings from steam settings using the interface in the Steam Beta Client version Unable to initialize Big Picture Mode with Gamepad Hotkey (Start Key in the Steam) in the Steam Beta Client version Those two issues are reproducible only in the Steam BETA update client version: Write themes for batocera-emulationstation.Redirect upgrades from any board to my own builds.Latency reduction and optimizing performance.Raspberry Pi: Add power buttons/switches.Sync files across multiple devices (Syncthing).PCman built-in file manager (for Xorg-powered devices).That Warning u get is because ur using a 64 bit OS, well thats wat i know atleast, i get it too and im using Ubuntu 12.10 gnome remix 64bit / gnome shell 3. Try Ubuntu 12.04 32bit, and see if there is any difference, and update ur video card driver to its latest. we've ruled out the graphics card, and window manager (openbox actually hasn't been updated for 15 months, so ours should be the same unless the testing repository uses the GIT version which I doubt.) It should affect everyone, and it should be hopefully fixed soon. It's a testing bed for developers delivered to the end-user.Īlso to those running Team Fortress 2, there's currently a bug where Steam uses 100% of your CPU, or at least on one core. You ought to get off testing repositories and use non-testing repositories. ArchLinux even advises you to subscribe (or at least recommends you) to their mailing list for reports on broken packages and other testing related stuff. I wouldn't advise you to run ArchLinux's testing libraries though, as those are not meant for production use. I ran openbox, and I could not see any noticeable performance issues that Steam was producing alone by itself. I'm using the same specifications as you except I'm using an ubuntu derived operating system with XFCE and that I use a non-sandy bridge Core i5 760. WM: MATE with AWN dock and compiz enabledĪll I had to do was update the Mesa stack and click play. Graphics: Nvidia Optimus GT650M / Intel 4000 HD I've had excellent performance so far using the following: Reference the initial floating reference is not owned by anyoneĪnd must be removed with g_object_ref_sink(). This means that someoneĬalled g_object_unref() on an object that had only a floating (steam:17095): Gtk-WARNING **: A floating object was finalized. Steam also logs the following to console continuously: Similarly context menus seem quite unresponsive sometimes refusing to acknowledge any mouse over or mouse clicks.ĭistro: Arch Linux with testing repos enabled. Scrolling through this forum using the inbuilt browser under the community tab is extremely choppy and stuttery. Moving the mouse around on the main steam window causes it to spike to 120% (Ie: using up 1 whole cpu core ++ ). On my current setup, MainThrd uses around 40-50% cpu while idling. Originally posted by Mewt :<:I would like to get some feedback on the performance of steam on linux.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |