#trinity-desktop < 2026/07/15
[02:02]ccx has quit (Remote host closed the connection)
[02:02]ccx has joined
[07:19]Fat-Zer has quit (Ping timeout: 245 seconds)
[07:34]Fat-Zer has joined
[07:38]Fat-Zer has quit (Ping timeout: 264 seconds)
[07:53]Fat-Zer has joined
[08:15]micheleC has joined
[08:58]houston: variable refresh rate/gsync isn't working for me under trinity, has anyone come across this before?
[09:15]Fat-Zer: it should be configured on X11 side; tde should have little to no effect over it...
[09:15]Fat-Zer: the only thing you can try disabling krandrtray... it could meddle with resolution/refresh in not the best way...
[09:16]SlavekB has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[09:36]houston: hmm, games still seem to be giving me torn frames
[09:37]houston: I might have to compare with dwm again just to make sure
[10:04]ccx has quit (Ping timeout: 252 seconds)
[10:18]micheleC has quit (Quit: Kopete 0.12.7 : http://trinitydesktop.org)
[10:21]ccx has joined
[10:30]ccx has quit (Remote host closed the connection)
[10:31]ccx has joined
[11:16]houston: I think I might have just been configuring my games wrong. I was configuring them to use a maximum FPS of 240Hz (my monitor's maximum), but it might be more correct to go either above or below, but not to attempt matching it
[11:16]houston: though below would naturally be the more correct option
[11:55]houston: from looking it up online: 1. the ideal is to have your game's framerate be limited to an odd 100-300FPS higher than your monitor's output rate. g-sync will completely disable itself, but tearing at this point is "imperceptible" and the only other harm you're doing is putting your graphics card under some duress. so that works great for some quake
[11:57]houston: 2. the situation with other cases (most cases) is a bit more complicated. nvidia's and some other companies' official docs advise you to enable both vsync and gsync. online, some enthusiasts advocate for setting a maximum framerate somewhat lower than the maximum refresh rate of your monitor according to a certain formula. the output of that formula happens to be 226Hz when it comes to a
[11:57]houston: 240Hz monitor
[12:43]tian2992 has quit (Read error: Connection reset by peer)
[12:43]tian2992 has joined
[14:03]Fat-Zer: I'd love to chime in with some advice but frankly I don't have a slightest idea how all this supposed to work...
[15:33]Frances has joined
[16:39]Frances has quit (Read error: Connection reset by peer)
[16:49]SlavekB has joined
[17:15]a-865 has quit (Ping timeout: 276 seconds)
[17:29]a-865 has joined
[18:28]tian2992 has quit (Ping timeout: 257 seconds)
[18:33]tian2992 has joined
[18:44]inverted_rabbit has joined
[20:22]MrMazda has quit (Ping timeout: 244 seconds)
[20:24]a-865 has quit (Ping timeout: 242 seconds)
[20:31]MrMazda has joined
[20:41]a-865 has joined
[22:19]inverted_rabbit has left (Disconnected: Replaced by new connection)
[22:19]inverted_rabbit has joined

#trinity-desktop < 2026/07/15