This is only guesswork here, but I presume are you’re trying to simply run the game from your Steam library as linked prefix, instead of having it installed into a separate Lutris game library folder?
The first is reported to cause problems, the second is the usual, recommended way and I’d suggest you try that first.
That said, comparing both logs via Meld, I figured, a missing .NET dll may be an issue here:
err:environ:init_peb starting L"C:\windows\Microsoft.NET\Framework\v4.0.30319\mscorsvw.exe" in experimental wow64 mode
But since this error shows up in both logs, it can’t be the cause.
fixme:dxcore:dxcore_adapter_GetProperty property 11 not implemented.
This points towards missing dll’s/libs (here DirectX) and it only shows up in the Lutris log (it’s probably provided by Steam’s Wine/Proton prefix, but not by that of Lutris.
Either you could try to check your game’s settings in Lutris for a related non-activated feature, or you might add the missing DirectX version manually into its Lutris prefix, .
At the very least, there’s a subtle difference in your logs, Lutris’s configuration seems to rely on:
D3D11InternalCreateDevice: Using feature level D3D_FEATURE_LEVEL_11_1
Whereas when running directly from Wine, it reads ‘D3D_FEATURE_LEVEL_11_0’, so this points to a possible problem with differences in your Lutris’ and your standard Wine’s expectation for the DirectX 11 implementation, probably Lutris’ config can simply be adjusted to the lower D3D 11 version.
Yet another hint in the Lutris log:
Command ‘wine’ not found on your system
Couldn’t find a terminal emulator.
Since you’re obviously trying to run the game in Lutris from an existing Steam prefix
→ /run/media/system/SteamDrive/Games/EtheriaRestart
(also verify, if Wine’s ‘drive_c/Games/EtheriaRestart/EtheriaRestart.exe’ actually links to this location)
There may be some environment setting issues, like missing global Wine vars, which are probably not available when running from this location. You could again check your Lutris configuration for those, or try to add Wine to your global path var, if it’s missing there.
This would seem to be a job for your distribution (Bazzite) Lutris maintainer, though and you should probably file a ticket to them.
You could also check your corresponding Steam Proton prefix and run configuration/start parameters, for arguments you might need to manually transfer into your Lutris’ game configuration, if the working folder matches, scan for differences between your Steam’s Proton and your Lutris’ game prefix, manually copying probably missing dll’s and configurations.
Maybe there’s also some missing anti-cheat setting/dependency required, see the entry for ‘Battle.net’ in Lutris’ log.
You could also try experimenting with Lutris’ system optimization settings like ‘prefer system libraries’, ‘Feral GameMode’, ‘Multi-GPU’, etc.
I haven’t tried to Link Steam prefixes to Lutris myself yet, perhaps I can tell more, when that’s the case and I encountered similar issues.
First I’d try to install the game into a dedicated Lutris game lib and prefix, though, if that’s possible.
That’s perhaps not an option, if you bought the game from the Steam store, due to their lock-in policy.
Trying to ‘hijack’ a Steam prefix is clearly not in this company’s interest and escaping their prison may require more or less tedious experimental fiddling / proof not feasible.
You can avoid this problem, when buying Online-DRM-free games only in the future, e. g. from GOG.