https://bugs.kde.org/show_bug.cgi?id=356938
--- Comment #10 from Thomas Lübking <thomas.luebk...@gmail.com> --- (In reply to AnAkkk from comment #9) > Running everything on the nvidia GPU isn't really a solution I rather meant "for a test" - to see whether it's optimus related reg. management of multiple contexts. > I am seeing the same behaviour as in bug #356366, if I click on the CS GO > window to come back from the ALT-TAB, I get the bug, but if I hover some > other icon on the task bar (like Dolphin) and use ALT-TAB to get back > in-game, I don't have the bug. Hovering will likely get you a tooltip (becoming the active plasmashell context) and when switching, the tooltip closes (and the active/dominant context becomes the game) > I went to kwin window rules, but I can't find any option to block > compositing for the window. Or maybe it's called differently here? Last tab (appearance and fixes), last item "block compositing" (I've unfortunately no idea how it's called in the french translation) > __GL_THREADED_OPTIMIZATIONS=1 is set in the game launch script by default in While __GL_THREADED_OPTIMIZATIONS should get you a benefit on multicore systems, I doubt it has actual impact on multicore rendering (which should work just as much) Also I meant "for trying impact" - and you'd still rather get superior rendering compared to the present situation (if that has impact on the problem, we don't yet know the actual problem - except for maybe trouble on GL context management; apparently it's not limited to optimus - the other bug is iirc on fglrx) -- You are receiving this mail because: You are watching all bug changes.
