Solved Wrong size of rendered area in app window and window size+pos from settings.toml are ignored on start

[DerTroglodyt]

Game Version​

2026.8.22.5348

Operating System​

Linux (Fedora 44, Wayland, 2 Monitors, Nvidia RTX 5080)

What Happened​

First start of the app sizes the window much to big (~1.5 times monitor size).
Resizing the window breaks the rendering of the app: It now only renders in the left upper part of the app window. Mouse interaction is scaled wrong, mouse does not render at position where it interacts.

More testing revealed:
When starting KSA all windows settings in setting.toml get ignored.
The application always starts up in postion and size where last session was closed.
Every start of the app leaves the rendered portion of the window smaller!

What Was Expected​

The app should use the whole window to render its content.

Reproduction Steps​

1. start app
2. resize window

Reproduction Rate​

always

 

[DerTroglodyt]

Game Version​

2026.8.22.5348

Operating System​

Linux (Fedora 44, Wayland, 2 Monitors, Nvidia RTX 5080)

What Happened​

First start of the app sizes the window much to big (~1.5 times monitor size).
Resizing the window breaks the rendering of the app: It now only renders in the left upper part of the app window. Mouse interaction is scaled wrong, mouse does not render at position where it interacts.

More testing revealed:
When starting KSA all windows settings in setting.toml get ignored.
The application always starts up in postion and size where last session was closed.
Every start of the app leaves the rendered portion of the window smaller!

What Was Expected​

The app should use the whole window to render its content.

Reproduction Steps​

1. start app
2. resize window

Reproduction Rate​

always

I solved the problem by setting a KWin rule to force a window size of 2249x1271 (though i have a 4k monitor). It seems that my scaling factor of desktop 170% is messing up the KSA renderer which gets confused between physical and logical pixel count.

 

[Kiwi Shark]

I solved the problem by setting a KWin rule to force a window size of 2249x1271 (though i have a 4k monitor). It seems that my scaling factor of desktop 170% is messing up the KSA renderer which gets confused between physical and logical pixel count.

I'll go ahead and mark this thread as solved then. Glad you got it working!