Bug report:
I don't usually open the overlay, so I've noticed this only when playing with a PS5 controller (great work on the controller support btw!). Whenever I have to type something (e.g. train station name, display panel), the game essentially breaks.
For example, take the following screen where text input is necessary:
- Clicking the text box is a death sentence
- 11-17-2024, 13-41-49.png (166.5 KiB) Viewed 778 times
The game continues running as normal, but stops accepting input from the controller - presumably because the game is awaiting input from a virtual keyboard. Using the actual (physical) keyboard allows writing on the text box, but clicking on any buttons does not work at all, so I get stuck on that screen. The game does not appear to register any mouse clicks, keyboard arrow keys, controller input, etc...
Moving the cursor with the mouse, analog stick or PS5 touchpad works fine. Weirdly enough, the ESC key also works, which opens the pause menu. But again, the game does not appear to register any mouse clicks, keyboard arrow keys, controller input, etc, so I can't save and exit the game. At this point, my only option is to ALT+F4.
The issue, however, appears to be related to the steam overlay. Usually, starting the game while in big-picture mode and pressing the PS button while in-game should bring up the big-picture overlay. This does not work. Pressing the button plays the sound that usually plays when opening the overlay, but nothing actually appears on screen - the game simply continues to show on-screen as if nothing happened. The game becomes unresponsive to controller input, as it now appears to be controlling an invisible overlay - I can hear the sounds of navigating through the overlay. Pressing the PS button makes the overlay closing sound, and the controller now controls the game as normal.
In the normal "desktop" mode, SHIFT+TAB does absolutely nothing, the game just keeps playing as usual. I've also tried enabling the steam overlay FPS counter, but this is also missing in both desktop and big-picture modes.
When in big-picture mode, if I press the super key, I can see that the steam overlay is running on a separate window:
- 11-17-2024, 14-11-57.png (545 KiB) Viewed 778 times
As I previously stated, pressing the PS button in normal plays sounds and the game becomes unresponsive to input. If I alt-tab to the overlay, I can navigate the menus. Sometimes, pressing the PS button changes focus automatically to this overlay window but does not return focus to the game, and I could not figure out which combination of options results in the focus changing from the game to the window vs focus remaining on the game.
- Appearance of overlay window when in focus. Usually, this window would show an additional menu with the factorio logo and options to change specific stuff like controller input. But here, those options are missing, almost as if steam does not recognize the game.
- 11-17-2024, 14-15-56.png (54.57 KiB) Viewed 778 times
Here's a list of things I've tried:
- Enabling/disabling X11/Wayling option in-game
- Using steam beta client
- Launching steam with iGPU, dedicated GPU, enabling/disabling hardware acceleration and "GPU blacklist" options in steam, disabled iGPU in BIOS, etc. No combination of these options made a difference.
- Launching game with compatibility option "Steam Linux Runtime 1.0 (Scout)" option
Here's something I noticed that might be a clue:
Logging out from my current Ubuntu session and selecting the option "Ubuntu on Xorg" (i.e. using X11 instead of wayland) allows both the "normal" overlay and the big-picture overlay to open when SHIFT+TAB or the PS button is pressed, but the virtual keyboard still won't appear on-screen. In this mode, when selecting the text input box using a controller, no virtual keyboard opens but the game keeps accepting input as usual, so I don't get stuck but still can't input anything.
I've attached logs for both X11 and wayland (ubuntu) sessions + the output log of simply running "steam" on the terminal (under wayland), launching the game that way, and reproducing the issue with the input. I've also included the outputs from steam's system report and runtime system information.
