Difference between revisions of "Talk:Steam"
(→Adding the Valve Developer Community to the interwiki table: close)
m (→Mention steam-native-runtime in main wiki?: remove closed discussion)
|Line 1:||Line 1:|
== Killing compsitors (Compton) ==
== Killing compsitors (Compton) ==
Revision as of 15:53, 17 March 2018
Killing compsitors (Compton)
killall compton && %command%; nohup compton &
killall compton; %command%; nohup compton &
be better as it does not rely on compton running when you start up a game? I've been frustrated more than a few times when I'd start a game, forgetting that compton wasn't running and the steam game would hang. —This unsigned comment is by Wartz (talk) 15:38, 9 March 2015. Please sign your posts with ~~~~!
- I think both are terrible. The proper way would be to to read the compton manual and adjust the configuration accordingly (i.e
unredir-if-possible = true). But if you did use a command like this, know that compton has a
-bswitch to daemonize, making nohup redundant. -- Alad (talk) 14:58, 9 March 2015 (UTC)
Hardware decoding for In-Home Streaming
For Intel Graphics
For NVIDIA Graphics
First, make sure that lib32-libva-vdpau-driver is installed from the AUR. Then, move the old steam vdpau folder out of the way:
mv ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/vdpau/ ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/vdpau.bak
Then, link in the vdpau folder from your system:
ln -s /usr/lib32/vdpau ~/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/.
To prove to yourself that it's working properly, make sure you have "Display performance information" ticked in your steam settings on the client under In-Home Streaming/Advanced Client Options. Now when you start streaming, press F6 on the client. The "Decoder:" line should show "VDPAU hardware decoding"
How to read Minidumps?
Set up Steam and have been playing around with a runtimeless install. It seems to work okay sometimes, other times it seems to randomly crash, giving minidumps that sit in /tmp. I'm familiar with using gdb to backtrace coredumps but these minidumps are something else, and I'm having a hard time finding out how to actually use them to figure out what's going on. Anyone have any clues? If so, that's perhaps something to add to this page. Insidious611 (talk) 16:10, 28 April 2016 (UTC)
Running games with bumblebee
it took me some time to find out why my games wouldn't run on the nvidia graphic card. I found out, that I needed Bumblebee and primus installed with 32-bit support. Also this page by steam was very helpful. Maybe somebody more experienced can add this to the article or I'll do that when I find the time.
- Correct me if I'm wrong, but isn't this the case for all GPU rendering and not just a Steam issue? Or do other GPU-intensive programs run on your NVIDIA card without Bumblebee and only Steam requires it? If it's the former, then we don't need to change the article.
- Silverhammermba (talk) 21:36, 3 August 2017 (UTC)
- The emphasis lies on the 32-bit support. At the time that I installed Bumblebee I didn't have any 32-bit programs. When installing Steam I did not go through the installation guide of Bumblebee again. Also it might be helpful to mention that some games are 32-bit and that you actually need to install 32-bit support.
- Nomalag (talk) 08:42, 4 August 2017 (UTC)
Adding the Valve Developer Community to the interwiki table
prefix: valve url: https://developer.valvesoftware.com/wiki/$1
We should facilitate linking to the official documentation.
- How often do we link to that wiki? There are 3 links on this page, but besides that I couldn't find any. I don't think it is worth it for 3 links.
- Besides that I think that wiki is of quite poor quality. (Outdated and poorly moderated; I've been active there in the past).
- -- Lonaowna (talk) 14:39, 28 January 2018 (UTC)