What Wine version? And do you have Gallium 9/CSMT enabled?

It's been pretty consistent for me since 1.6, if not earlier, with and without the wine-staging patches, but 1.7.43-staging for sure.

Also I confirmed that it's not just a Bethesda game, but Dragon Age Origins does it too. Interestingly, DAO's cursor appeared on the overlay but I couldn't click anything with it. I think it's something to do with how it captures the mouse.

I don't think I even have Gallium 9 support (proprietary nVidia drivers), but it's been pretty consistent with and without CSMT.

Hmm, because I had it working with Skyrim. Haven't tested it with anything else. The default cursor appears. So I doubt it is a problem with Steam itself, and rather a problem with the compatibility layer.

Wine 1.7.43-staging
Wine settings:

• Windows Version: Windows 7
• CSMT enabled
• EAX enabled

Library overrides:

• d3dcompiler_43 (native, builtin)
• d3dx10_33 - d3dx10_43 (native, builtin)
• d3dx11_42 - d3dx11_43 (native, builtin)
• d3dx9_24 - d3dx9_43 (native, builtin)
• dwrite (disabled)
• gameoverlayrenderer (native, builtin)
• msvcr90 (native, builtin)
• msxml3 (native)

System info:

• Operating System: Fedora 22 4.0.4-301.fc22.x86_64
• OpenGL renderer: Mesa DRI Intel Haswell Mobile
• OpenGL version: 3.0 Mesa 10.5.4

I'm not using the Windows overlay at all, by the way, I'm not sure it's clear. I'm using the Linux overlay.

Sorry but I'm not familiar with that setup. So you're running Steam for Windows but it launches the Linux overlay?

...sort of.

I have two instances of Steam running, Windows Steam and Linux Steam. Windows Steam runs in offline mode, and is configured to not open the overlay under any circumstances. From there, my Windows games are added to my Linux Steam instance as non-Steam shortcuts, and with that, the overlay is provided by the Linux version of Steam.

As I think I said, it's not exclusive to games that rely on Windows Steam. My copy of Dragon Age: Origins is an Origin copy (har har), and Windows Steam is in no way involved with it (it's usually not even running at the time). The overlay still fails to receive mouse input. I believe it's something to do with how wine captures mouse input.

Yeah, probably because wine is asking for mouse input/focus since it is a game with its window selected, and doesn't recognize the Linux Steam overlay asking for mouse focus.

But why go through such lengths to use the Linux Steam overlay? Is the Windows Steam overlay not working?

I just prefer to launch all my games through the same Steam instance.

Also, I'd like to point out (once again) that it's consistent across Wine
games, including games where Steam is not required in any form whatsoever.
Therefore, Windows Steam isn't actually relevant to the bug that I'm
actually trying to report. If I completely uninstalled Windows Steam and
all games tied to it, the bug would persist for Wine games that aren't
involved. This is an actual problem.

So can you please stop hounding me about the Windows overlay? It's not
relevant to this bug. Thank you.

On Mon, Jun 1, 2015 at 10:07 PM mastercoms [email protected] wrote:

Yeah, probably because wine is asking for mouse input since it is a game,
and doesn't recognize the Linux Steam overlay.

But why go through such lengths to use the overlay? Is the Windows Steam
overlay not working?

—
Reply to this email directly or view it on GitHub
https://github.com/ValveSoftware/steam-for-linux/issues/3862#issuecomment-107810190
.

You probably won't see any real movement in this; Valve has really heavily hinted at not supporting issues regarding Steam and Wine.

I'm sorry if you felt that way. In no way was I trying to be intrusive or hounding, though now I see how you would think that.

Does the game respond to your mouse?

You probably won't see any real movement in this; Valve has really heavily hinted at not supporting issues regarding Steam and Wine.

Well they definitely won't fix things they don't even know about. Besides, this might even occur with some native Linux game - if Wine can do it...

I'm sorry if you felt that way. In no way was I trying to be intrusive or hounding, though now I see how you would think that.

Apology accepted, and no harm done or offense taken.

Does the game respond to your mouse?

Not with the overlay up, at least not in any way that I can notice. DAO's cursor did appear on the overlay, but clicking menu options didn't seem to have an effect. I should probably retest though, my memory is garbage.

If the game does not respond to the mouse when the overlay is working, it is probably a Steam for Linux bug, although caused by Wine, since Steam for Linux probably only expects non-Wine games. As stated above, since this is a Wine related problem, although inevitability a flaw in Steam itself, it might not be fixed. However, personally, I hope this bug will be fixed.

I'm unable to reproduce with a pure Linux install.

The description of the issue leads me to suspect that the issue may be the game in Wine capturing the cursor and not releasing it to the unrelated (Steam for Linux) overlay.

If the game was capturing the cursor, wouldn't the game respond to mouse input?

What I mean is that the game releases the cursor, but not to the Steam overlay. It might just wind up buried (for lack of a better term) under the different layers (which is how compositors handle multiple items on screen). That might be why the cursor only shows up at the very edges.

Ah, yes, that makes sense. Could the Steam overlay somehow force capture to itself?

As I'm not a Valve employee, but rather a collaborator of theirs, I can't speak for the client's potential behavior. Hypothetically, that's possible, but I don't think that's how the client currently handles it.

Having discussed this issue with some other developers who have worked with Wine in their projects (not Valve employees, mind you), they feel that this scenario is neither a Wine issue, nor a Steam issue, but rather a configuration issue. That is, this is outside of the specifications of how either is really supposed to handle things. You might be able to craft some sort of kludge to get it to work... maybe a trigger that forces the cursor to top when the Steam Overlay (linux) is brought up, but again, that's outside of the purview of either Valve or Wine.

This happens also when I try using Steam overlay UI without any WINE, doesn't matter which game in: it simply pushes you back to the game many times, and rarely the overlay usable is.

@Plaque-fcc that's different from what was reported here. That sounds more like #3093.

#3427 has some information that may help the OP's situation, too. Granted, that's a stab in the dark. First step (as mentioned on this second issue) is running Steam without the runtime:
STEAM_RUNTIME = 0 steam

I can't run with STEAM_RUNTIME=0, since I'm apparently missing a 32 bit lib that it needs, and it won't tell me precisely which.

Also, I triple checked, and I can confirm that neither the overlay nor the game itself actually responds to mouse input (using Dragon Age Origins again since that cursor still renders on top of the overlay somehow)

Exactly what is the error?