Crashing when opening.

[maumagro]

Version information:

• Platform: Windows 11 Pro
• Version: 23H2 (Build 22631.3296)
• Build/commit: f0863a0

Describe the bug
When opening OpenLoco from the Launcher (also with zipped version), I get a crash dump. Tried changing the display settings on openloco.yml as I read on an article, still same problem.

To Reproduce
Steps to reproduce the behaviour:
Just opening the game from launcher or openloco.exe

Expected behaviour
Game opening and having fun.

Screenshots

Additional context
Can't attach crash dump, weighs 61 MB.

[AaronVanGeffen]

Could you please upload a zipped version of the crash dump somewhere? It will be vertical difficult to reproduce without

[maumagro]

1c7e7732-0b87-48c5-8189-a03c49ab6b6b(OpenLoco, v24.03 (f0863a0c on master)).zip

Why didn't I think of zipping it? Here you go. Thank you!

[duncanspumpkin]

This is crashing in an opengl init function which we don't have much to do with. All we do is tell SDL to get it setup, tell it the dimensions of the window and make a suggestion of using opengl. Could you provide your openloco.yml file? Maybe the width and height are something odd.

[maumagro]

Here's the openloco.yml

---

display:
mode: fullscreen
window_resolution:
width: 800
height: 600
fullscreen_resolution:
width: 1920
height: 1080
audio:
play_title_music: true
network:
enabled: false
loco_install_path: C:\Program Files (x86)\GOG Galaxy\Games\Locomotion
last_save_path: ""
last_landscape_path: ""
language: en-GB
preferredCurrency:
flags: 130
name: CURRDOLL
checksum: 0
usePreferredCurrencyForNewGames: false
usePreferredCurrencyAlways: false
scale_factor: 1
showFPS: false
uncapFPS: false
allow_multiple_instances: false
cashPopupRendering: true
edgeScrolling: true
edgeScrollingSpeed: 12
zoom_to_cursor: true
autosave_amount: 12
autosave_frequency: 1
breakdowns_disabled: false
buildLockedVehicles: false
cheats_menu_enabled: false
companyAIDisabled: false
disableVehicleLoadPenaltyCheat: false
displayLockedVehicles: false
invertRightMouseViewPan: false
townGrowthDisabled: false
trainsReverseAtSignals: true
disableStationSizeLimit: false
preferredOwnerName: ""
usePreferredOwnerName: false
preferredOwnerFace:
flags: 0
name: "\x00\x00\x00\x00\x00\x00\x00\x00"
checksum: 0
usePreferredOwnerFace: false
shortcuts:
closeTopmostWindow: Backspace
closeAllFloatingWindows: Left Shift+Backspace
cancelConstructionMode: Escape
pauseUnpauseGame: Pause
zoomViewOut: PageUp
zoomViewIn: PageDown
rotateView: Return
rotateConstructionObject: Z
toggleUndergroundView: 1
toggleSeeThroughTracks: 2
toggleSeeThroughRoads: 3
toggleSeeThroughTrees: 4
toggleSeeThroughBuildings: 5
toggleSeeThroughScenery: 6
toggleHeightMarksOnLand: 7
toggleHeightMarksOnTracks: 8
toggleDirArrowsOnTracks: 9
adjustLand: L
adjustWater: W
plantTrees: P
bulldozeArea: X
buildTracks: T
buildRoads: R
buildAirports: A
buildShipPorts: D
buildNewVehicles: N
showVehiclesList: V
showStationsList: S
showTownsList: U
showIndustriesList: I
showMap: M
showCompaniesList: C
showCompanyInformation: Q
showFinances: F
showAnnouncementsList: Tab
makeScreenshot: Left Ctrl+S
toggleLastAnnouncement: Space
sendMessage: F1
constructionPreviousTab: ""
constructionNextTab: ""
constructionPreviousTrackPiece: ""
constructionNextTrackPiece: ""
constructionPreviousSlope: ""
constructionNextSlope: ""
constructionBuildAtCurrentPos: ""
constructionRemoveAtCurrentPos: ""
constructionSelectPosition: ""
gameSpeedNormal: ""
gameSpeedFastForward: ""
gameSpeedExtraFastForward: ""

[duncanspumpkin]

Hmm that's annoying. Nothing unique or odd there. I'm out of suggestions. Update graphics card drivers? Do you play other games do they have issues? It looks like an sdl issue which is used by tons of games.

[maumagro]

I play tons of games, most regular are AoE II Definitive, GTA V, Ark, Cities Skylines, Transport Fever, Portal 2, FSX. I hope that helps.

[AaronVanGeffen]

I think we should update our SDL dependencies, as they're pinned to one of last year's versions of SDL. Not sure if it will help your case, but it's worth a try.

Could you try a build from #2407 to see if that fixes the issue for you? Once CI has finished, builds should appear at the bottom of this page.

[AaronVanGeffen]

We released v24.04 moments ago, which uses an updated version of the SDL library. Could you try the new version, and see if that solves your problem?

[maumagro]

Updated, not working. Here's new error and dump. Any other way I can help?
I tried using the launcher and also downloading from the official website. Both ways same error.

a99cfcbf-9b8d-440b-9e9c-6e266fc4ab85(OpenLoco, v24.04 (a91d0c42 on master)).zip

[LeftofZen]

That's unfortunate then, I'm not sure how we'll debug this one then

[LeftofZen]

Looks like you have an ATI graphics card? Can you download the latest drivers for your card? What card specifically is it?

[maumagro]

I've 2 graphic cards. GTX 960 2GB and AMD Radeon R7 IGP. Tried changing both on graphic settings on windows, same thing.

[LeftofZen]

yep ok, the 960 is definitely the way to go as while loco doesn't actually use the gpu for any hardward rendering, the integrated graphics from the AMD card probably has some funky stuff going on. the 960 is quite old though - what driver version does it say you have in geforce experience?

[maumagro]

Updated 4 days ago.

Yes, the GPU is quite old, but I don't have any problems with any other game, everything works like a charm.

[LeftofZen]

hmm yeah i don't see any reason why it wouldn't work then. although i'm still puzzled why the amd/ati drivers are in the minidump call stack, as that implies the integrated gpu was used during the crash

[LeftofZen]

I recall on my old laptop, there was also an nvidia setting for forcing the GPU. I really don't trust Windows to enforce it, so could you try this option as well. I usually did the system-wide/global option, but per-program should also work.

https://superuser.com/questions/1815471/force-windows-laptop-to-always-use-my-dedicated-gpu-on-power-and-integrated-gpu

[LeftofZen]

in fact can you

1. set it to High-performance NVIDIA processor

2. retry the game

if that doesn't work (it still crashes) then can you:

1. then run dxdiag command?
   

2. then printscreen the output for display1, like this