1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
# Gamescope Script/Config Files
## ⚠️ Health Warning ⚠️
Gamescope scripting/configuration is currently experimental and subject to change massively.
Scripts and configs working between revisions is not guaranteed to work, it should at least not crash... probably.
## The Basics
Gamescope uses Lua for it's configuration and scripting system.
Scripts ending in `.lua` are executed recursively in alphabetical order from the following directories:
- `/usr/share/gamescope`
- `/etc/gamescope`
- `$XDG_CONFIG_DIR/gamescope`
You can develop easily without overriding your installation by setting `script_use_local_scripts` which will eliminate `/usr/share/gamescope` and `/etc/gamescope` from being read, and instead read from `../config` of where Gamescope is run instead of those.
When errors are encountered, it will simply output that to the terminal. There is no visual indicator of this currently.
Things should mostly fail-safe, unless you actually made an egregious mistake in your config like setting the refresh rate to 0 or the colorimetry to all 0, 0 or something.
# Making modifications as a user
If you wish to make modifications that will persist as a user, simply make a new `.lua` file in `$XDG_CONFIG_DIR/gamescope` which is usually `$HOME/.config/gamescope` with what you want to change.
For example, to make the Steam Deck LCD use spec colorimetry instead of the measured colorimetry you could create the following file `~/.config/gamescope/my_deck_lcd_colorimetry.lua` with the following contents:
```lua
local steamdeck_lcd_colorimetry_spec = {
r = { x = 0.602, y = 0.355 },
g = { x = 0.340, y = 0.574 },
b = { x = 0.164, y = 0.121 },
w = { x = 0.3070, y = 0.3220 }
}
gamescope.config.known_displays.steamdeck_lcd.colorimetry = steamdeck_lcd_colorimetry_spec
```
and it would override that.
You could also place this in `/etc/gamescope` if you really want it to apply to all users/system-wide, but that would need root privelages.
# Features
Being able to set known displays (`gamescope.config.known_displays`)
The ability to set convars.
Hooks
# Examples
A script that will enable composite debug and force composition on and off every 60 frames.
```lua
my_counter = 0
gamescope.convars.composite_debug.value = 3
gamescope.hook("OnPostPaint", function()
my_counter = my_counter + 1
if my_counter > 60 then
gamescope.convars.composite_force.value = not gamescope.convars.composite_force.value
my_counter = 0
warn("Changed composite_force to "..tostring(gamescope.convars.composite_force.value)..".")
end
end)
```
# Hot Reloading?
Coming soon...
|
