Log window conflicts with Steam overlay, game recording

[exscape]

I have issues with the log window being considered the main target for recording and the Steam overlay. Not sure what is going on here.
This also depends on exactly how you launch the game, and I don't know why.

This is what happens for me:

• Click "play" from inside Steam: game recording records the log window, Steam overlay shows in both windows when open, and various other issues (windows resize themselves, there's an offset between the mouse cursor in the Recording timeline and where it actually acts)
• Launch from taskbar StS 2 icon: game recording records the log window, Steam overlay shows ONLY in log window
• Launch from Rider (launch_vulkan.bat after build+copy mod files): seems to work as intended

I tried making the window Transient, but I don't think it had any effect. Setting Window.Flags.ExcludeFromCapture also did not help, but based on the docs I didn't expect it to.

Edit: I have a Radeon 9070 XT and am on Windows 11, by the way.

[exscape]

I figured out the difference between the last two cases, at least, that was my bad: the taskbar shortcut started the main .exe with no argument, i.e. D3D12 rendering. I thought it was a steam:// shortcut prior to checking.
If I add --rendering-driver vulkan, it works as intended.
Conversely, if I tell Rider to run launch_d3d12.bat it breaks, so this part is strictly due to the API used.

When launched from Steam, however, I also use Vulkan via command-line arguments, and that is still broken.
Ironically, If I DON'T use Vulkan in Steam, it works. Perhaps some quirk of Steam overlay's hooking with different APIs?

So to be clear:

API	Launched from Steam	Launched standalone
Vulkan	Broken	Works
D3D 12	Works	Broken

So I can fix this for me by picking the right API for the right launch type.

[Alchyr]

Does it happen with log window on startup or also if log window is shown with the showlog command?
Regardless, not much probably that can be done about this since a lot of this is likely deep in how Godot handles the separate window + how other software handles hooking into other windows.

[BAKAOLC]

Actually, I don't think the log window is very necessary; launching directly via the command line and relying on its native I/O data is more stable and doesn't require any extra handling, we just need to provide documentation telling users how to use it
Moreover, the custom-injected log window heavily depends on various launch orders, and I think a native workflow would be better suited for development use

[exscape]

I find the window rather useful (which is why I worked a bit on it). At least in Rider, you can't filter the log output, as far as I can tell. (Not even with the "Grep Console" plugin.)
Not by log level, and not by text content. That makes it annoying to find the bits you care about.

[BAKAOLC]

Honestly, being able to directly obtain the original log stream and process it in a separate window is also a completely feasible solution
The main issue is that an injected extra window is a solution involving deep embedding that affects actual performance

[Alchyr]

showlog is mainly a convenience feature, and I'd say this is both a complicated issue to fix and doesn't really have all that much benefit to doing so. So, will just leave this as-is for now.

[exscape]

I agree. It's also worth mentioning that the issues I have with the taskbar launch (D3D) where it only records the log window isn't a race condition or similar; if I delay the log window, it captures nothing until you open the log window.

So the window doesn't really break anything; the overlay and recording are broken without the log as well.