Thread with 12 posts

jump to expanded post

honestly it’s really depressing that this is actually how stuff like fraps, the Steam overlay, RTSS, and many other gamer overlays work. they just inject themselves into your app’s OpenGL context (or whatever) and fuck around. and sadly it’s not them that find out. it’s you. >:(

Open thread at this post

I already have enough to worry about with the fact I’m basically doing the same thing to the app under emulation, but I can at least trust myself to be careful. I can’t trust random software installed on the average gamer’s computer. I don’t even know what that software is.

Open thread at this post
Gina Peter Banyard , @Girgias@phpc.social
(open profile)

@hikari Possibly? The fact that each window is a separate context and because compositing is mandatory in Wayland, I would imagine this would prevent some of this interference?

As for me, an overlay is just a thing that composites/decorates on top of an existing, but specific window?

May be saying nonsense tho as I'm not that familiar either. Just that I'm running Wayland on Fedora and sometimes I have weird issue that might be because of that.

Open remote post (opens in a new window)

@Girgias yeah you’d think that overlays could be handled by the compositor, but to the best of my knowledge, the way all the gaming ones work is by messing with other apps’ opengl/direct3d/whatever contexts instead. this might be because they predate widespread use of composition, but there’s not really a good excuse for them to continue to work that way these days imo

Open thread at this post