IIRC, the Steam Overlay will not appear unless you have --in-process-gpu
, because Steam doesn't understand Chrome's multi-process architecture. Using --in-process-gpu
is a hack to work around that bug in Steam. They really should fix the Steam overlay, otherwise you just keep getting deeper and deeper in to hacks and workarounds, and you eventually get cornered with situations like this, where you have to choose between good performance or having the Steam overlay work.
IIRC there was some other way to modify a binary to force the high-performance GPU, and maybe that works with --in-process-gpu
, but that's still going down the rabbit hole of hacks. The best approach is and always has been for Steam to fix the overlay.
I've done by best to contact Valve about that, and so far they've ignored us. In situations like this we need every individual developer affected to contact Valve about it so they better understand the scope of the problem.