Compatibility Report

Hey @alasky17

1. No. Appears it is not regression
2. No. I am using KDE + Wayland. Yes. My configuration is very specific… Red is refresh rate
   
3. The one you provided is not one who causing the problem.

I figured out that issue appears only when I change full screen mode to Full Screen (Exclusive).

And for some reason the window appears to have a title, but in game settings it is full-screen and title is disabled in KDE settings.

Let me know if you know how to copy list of all changed settings, if my new info didn't help a lot

Gentle ping. I checked all settings I changed related to window managing. It seems to be unrelated to plasma settings, but I'll check again when plasma 6.0 hits Manjaro testing

Also Proton experimental still has same issue at the moment

@damnkrat I don't want to give you false hope - unfortunately, since this is not a regression, this specific bug is not something we are actively working on. We do work on improving focus loss in general, but it is a slow process. It is an extremely challenging aspect of Wine, without even taking into account the large number of WMs and variation in monitors like you described above. For what it is worth, we were not able to reproduce this issue locally, so it is almost certainly due to something specific about your setup. It is possible that unplugging a monitor when you play Planet Crafter or something of that nature could fix this issue for you in the meantime :)

@alasky17 Sorry to say this only now, but I just now checked that physically and software disabling other monitors doesn't help in any way. Alt tabbing breaks the window, even when there is only 1 monitor. Tested on a 1080 and 2k monitor

The solution is done on KDE side!

When Alt+Tabbing through windows, tab keystrokes no longer leak into XWayland-using apps when using default XWayland app keyboard snooping setting (David Edmundson, Plasma 6.2.0. Link)

Hello! The game refuses to load on recent versions of Proton, and on 6.x the mouse is very glitchy, tends to force my view to go all the way up or down. I suspect it might be a regression since DLC release, given my player.log says:

UnloadTime: 1.279100 ms
NullReferenceException: Object reference not set to an instance of an object
  at SpaceCraft.PlanetList.GetIsPlanetPurchased (SpaceCraft.PlanetData planet) [0x00028] in <bb15078570824cc99da35ddd2657a824>:0 
  at SpaceCraft.HideIfOwnPlanet.OnEnable () [0x00000] in <bb15078570824cc99da35ddd2657a824>:0 

Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
UnloadTime: 21.973000 ms
Unloading 292 unused Assets to reduce memory usage. Loaded Objects now: 138455.
Total: 56.800700 ms (FindLiveObjects: 7.989300 ms CreateObjectMapping: 10.333200 ms MarkObjects: 38.080800 ms  DeleteObjects: 0.396700 ms)

NullReferenceException: Object reference not set to an instance of an object
  at SpaceCraft.PlanetList.GetIsPlanetPurchased (SpaceCraft.PlanetData planet) [0x00028] in <bb15078570824cc99da35ddd2657a824>:0 
  at SpaceCraft.PlanetList.InitPlanetList () [0x00073] in <bb15078570824cc99da35ddd2657a824>:0 
  at SpaceCraft.PlanetList.GetPlanetList (System.Boolean allPlanets) [0x00000] in <bb15078570824cc99da35ddd2657a824>:0 
  at SpaceCraft.PlanetNetworkLoader.Start () [0x0001c] in <bb15078570824cc99da35ddd2657a824>:0 

Hi kisak, thanks for your very quick answer (and your fantastic work as usual)!

Here is the proton log: steam-1284190.log
Here is the Steam runtime system info: https://gist.github.com/Cheaterman/b3b69ae943a189ad8b1709912725d4cf

In addition, here is the game-specific Player.log I mentioned above: Player.log (probably less useful to Valve, but probably useful to the game dev instead)

Thanks again, I hope we can find a good solution to this :-)

This might be a red herring, but VK_DRIVER_FILES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json in your environment (https://gist.github.com/Cheaterman/b3b69ae943a189ad8b1709912725d4cf#file-steam-runtime-system-info-txt-L75) is forcing a 32 bit Vulkan render path to not be available. If you can find where that's being set, then removing it might have an effect.

That's something I add on purpose on my openbox environment script, I have a primusrun script for 64 bits apps and a primusrun32 that does the opposite and forces the 32 bits Vulkan renderer for Intel:

.config/openbox/environment:

PATH=$HOME/.local/bin:$PATH
export VK_DRIVER_FILES=/usr/share/vulkan/icd.d/intel_icd.x86_64.json

cat $(which primusrun):

#!/bin/sh
export \
    __GLX_VENDOR_LIBRARY_NAME=nvidia \
    VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.json:$VK_DRIVER_FILES \
;
exec "$@

cat $(which primusrun32):

#!/bin/sh
export \
    __GLX_VENDOR_LIBRARY_NAME=nvidia \
    VK_DRIVER_FILES=/usr/share/vulkan/icd.d/nvidia_icd.i686.json:/usr/share/vulkan/icd.d/intel_icd.i686.json \
;
exec "$@"

I can try to drop it, or I can try launching Planet Crafter with the primusrun32 script, but this setup otherwise works pretty well for me so far.

EDIT: As expected, Planet Crafter doesn't launch with primusrun32 ; I'll be trying to launch the game without VK_DRIVER_FILES set in my env later on, mostly to rule it out as a cause, but as you noted it's likely not the issue.

EDIT2: That indeed does not help, sadly.

OTOH at this point the biggest issue I have is the mouse pitch thing - mouse gets stuck in full up or full down position, this seems to be framerate-dependent and particularly noticeable with vsync and/or frame limiter enabled. I'd love for the game to work on latest Proton versions because I assume it could fix some of that, but if the game fixes the mouse situation playing on Proton 6 is perfectly fine (if not totally stable).