Posted January 28, 2024
Run the config utility.first and play with the settings.
This seems obvious, but I want to note that for some reason I think Galaxy launches the DX9 version of the game executable specifically, so you'll want to play with the config utility specific to that version. The "Launch The Legend of Heroes - Trails in the Sky" shortcut also points to the DX9 executable. Both configs and both game executables are in the game install directory.
I just now had the problem where launching from Galaxy failed. I was too smart by half and ran its config utility for the non-DX9 version first, setting it to borderless windowed at fullscreen resolution, so I didn't get to test what the non-DX9 version was like before this, but after I did this, the non-DX9 executable ran fine. Then I found that the DX9 executable still crashed even when launched directly. Then I modified the settings for the DX9 version in the same way, and it launched fine, both directly and via Galaxy.
Then, I used the config utility to set the resolution back to what I remembered was default (1440x900, which in turn swaps "borderless windowed" back into "windowed mode", but then both versions still launched fine, even through Galaxy.
Possible causes for my crash (which I can't reproduce anymore, though that's not exactly a bad thing):
1. I'm forcing the GOG Overlay. https://docs.gog.com/gc-overlay/#testing-overlay-locally
The GOG Overlay is known to be a little wonky with some older Falcom PC games; see this thread for more details: https://www.gog.com/forum/general_beta_gog_galaxy_2.0/galaxy_overlay_tests_and_reports_for_unsupported_titles/post20 .
However, it works fine (including with the overlay) after I run the config, on two different resolutions, so maybe this isn't the issue.
2. I brought in an old config file and also old save files from my previous computer. I already beat the game once before, on a different computer, and on Steam, but I'm gradually moving my stuff over to GOG, so I ported over my saves and config. This might have broken it initially, and gotten fixed when I re-ran the config and gave it the right settings to work on this computer.
This seems obvious, but I want to note that for some reason I think Galaxy launches the DX9 version of the game executable specifically, so you'll want to play with the config utility specific to that version. The "Launch The Legend of Heroes - Trails in the Sky" shortcut also points to the DX9 executable. Both configs and both game executables are in the game install directory.
I just now had the problem where launching from Galaxy failed. I was too smart by half and ran its config utility for the non-DX9 version first, setting it to borderless windowed at fullscreen resolution, so I didn't get to test what the non-DX9 version was like before this, but after I did this, the non-DX9 executable ran fine. Then I found that the DX9 executable still crashed even when launched directly. Then I modified the settings for the DX9 version in the same way, and it launched fine, both directly and via Galaxy.
Then, I used the config utility to set the resolution back to what I remembered was default (1440x900, which in turn swaps "borderless windowed" back into "windowed mode", but then both versions still launched fine, even through Galaxy.
Possible causes for my crash (which I can't reproduce anymore, though that's not exactly a bad thing):
1. I'm forcing the GOG Overlay. https://docs.gog.com/gc-overlay/#testing-overlay-locally
The GOG Overlay is known to be a little wonky with some older Falcom PC games; see this thread for more details: https://www.gog.com/forum/general_beta_gog_galaxy_2.0/galaxy_overlay_tests_and_reports_for_unsupported_titles/post20 .
However, it works fine (including with the overlay) after I run the config, on two different resolutions, so maybe this isn't the issue.
2. I brought in an old config file and also old save files from my previous computer. I already beat the game once before, on a different computer, and on Steam, but I'm gradually moving my stuff over to GOG, so I ported over my saves and config. This might have broken it initially, and gotten fixed when I re-ran the config and gave it the right settings to work on this computer.
Post edited January 28, 2024 by GlennMagusHarvey
