Since updating to 2.0, I've been getting random crashes, all with the same log messages (most recent log and memory dump are attached). They have been happening during all phases of the game (I even had one during the initial startup load when booting the game). Despite what the logs may claim, I don't have any controllers connected to my machine.
Sorry for not having a reproducible test case, it's been happening often enough to impede progress but not enough to narrow down a cause. If need be, I can try and attach a debugger to the game while I play.
[2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame (MR)
- lucyisgamer
- Burner Inserter
- Posts: 5
- Joined: Sun Oct 27, 2024 5:03 am
- Contact:
[2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame (MR)
- Attachments
-
- factorio-previous.log
- (14.47 KiB) Downloaded 35 times
-
- factorio-dump-previous.dmp
- (911.63 KiB) Downloaded 19 times
Re: [2.0.11] Seemingly random hard crash (possibly SDL related?)
I WAS randomly crashing before 2.0.8 I think? Several hours then a crash, consistently. Haven't in a day or two, though, since 2.0.8 or 2.0.9 or something like that.
[2.0.11] Game crash - SDL_rawinputjoystick.c
The game crashed randomly
Merged...
Merged...
- Attachments
-
- sa.zip
- (4.13 MiB) Downloaded 15 times
-
- factorio-current.log
- (20.7 KiB) Downloaded 24 times
Re: [2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame
You could try disconnecting your joystick and disabling steam overlay for factorio.
- lucyisgamer
- Burner Inserter
- Posts: 5
- Joined: Sun Oct 27, 2024 5:03 am
- Contact:
Re: [2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame (MR)
I didn't have any controllers connected to begin with, but I can try disabling the Steam Overlay. I can also confirm that this issue still affects 2.0.14.
- lucyisgamer
- Burner Inserter
- Posts: 5
- Joined: Sun Oct 27, 2024 5:03 am
- Contact:
Re: [2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame (MR)
Tried disabling Steam Overlay (and Steam Input, for good measure) and game still crashes on 2.0.15.
Re: [2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame (MR)
Is this still an issue in the latest version (2.0.23 or newer)? In Factorio 2.0.16 we have updated SDL from version 2.30.0 to 2.30.9 and there are several fixes for controller support mentioned in the SDL patch notes.
Re: [2.0.21] Crash (RAWINPUT_UpdateWindowsGamingInput)
Also had this crash occur on version 2.0.23. It seems to trigger when my XBox Series X Controller is turned on (even if it isn't actively connected to my PC via Bluetooth, i.e. it is connected to another PC, but in my "bluetooth devices" list)
- Attachments
-
- factorio-current.log
- (16.37 KiB) Downloaded 13 times
Re: [2.0.11] Crash, SDL_rawinputjoystick.c / VulkanSteamOverlayProcessCapturedFrame (MR)
Thanks for the info.
I bought Wireless Xbox Controller but have not been able to reproduce the crash. One thing I noticed from minidump OP posted, is that they have somewhat outdated version of Steam's gameoverlayrenderer64.dll (in which the crash happens). I have version 9.38.28.26, OP's minidump has version 9.18.90.86, and one of the duplicate threads has minidump with version 9.33.91.58.
From the crashlog, SDL is calling Window's API function get_GamePads from Windows.Gaming.Input.IGamepadStatics interface, which is intercepted by Steam's overlay, which triggers the crash. So it might be even bug in Steam overlay which might have been fixed in current Steam client.
I bought Wireless Xbox Controller but have not been able to reproduce the crash. One thing I noticed from minidump OP posted, is that they have somewhat outdated version of Steam's gameoverlayrenderer64.dll (in which the crash happens). I have version 9.38.28.26, OP's minidump has version 9.18.90.86, and one of the duplicate threads has minidump with version 9.33.91.58.
From the crashlog, SDL is calling Window's API function get_GamePads from Windows.Gaming.Input.IGamepadStatics interface, which is intercepted by Steam's overlay, which triggers the crash. So it might be even bug in Steam overlay which might have been fixed in current Steam client.