handling cpu limiting differently, maybe fine
This commit is contained in:
@@ -35,11 +35,9 @@
|
||||
|
||||
/home/gameservers/.steam/debian-installation/steamapps/common/Counter-Strike Source/cstrike/cfg/autoexec.cfg: <br/>
|
||||
alias loop "exec looptest.cfg; wait 5; loop;"; wait 5; loop; <br/>
|
||||
(textmode is no video output) <br/>
|
||||
|
||||
exporting correct SDL_VIDEO_X11_VISUALID value is important before steam login for starting games correctly <br/>
|
||||
<br/> With the virtual desktop related to the VNC/x2go/nomachine client you can log into steam using the normal GUI -> <br/>
|
||||
once logged in steam can run actively for months without requiring restarts
|
||||
|
||||
## bashrc for users
|
||||
in the users thats running a session edit the .bashrc file and add the follwing (remember SDL_VIDEO_X11_VISUALID deppends on glxinfo from xterm terminal):
|
||||
@@ -52,7 +50,7 @@
|
||||
fi
|
||||
|
||||
|
||||
ovh: 0x205, 0x209
|
||||
0x205, 0x209
|
||||
|
||||
#if running steam native libraries instead of runtime libraries one might require following apt install for making libpipewire work
|
||||
|
||||
@@ -90,3 +88,4 @@ limiting cpu can throttle the download speed as well. if bots cant connect and a
|
||||
#pip3 extra
|
||||
|
||||
pip3 install watchdog
|
||||
|
||||
|
||||
Reference in New Issue
Block a user