@airtex2019 This was very helpful, thanks. I also suspected something funky with the audio drivers based on some of the modules that were coming up in the Windbg session.
On a fresh reboot this morning, I changed the audio device to the HDMI out instead of the external speakers I have set up. And voila, Falcon launched fine. I changed the device back to the normal external speakers… and… voila, worked fine again.
Bizarre. Interestingly enough, here’s the xlog
output from when it was crashing:
...
[00:00:00.000] 41508 Terrain: Unload
[00:00:00.000] 41508 Terrain: Load
[00:00:00.000] 41508 Terrain max texID: 3991
[00:00:00.000] 41508 SoundDriver 0x0000000019A2BDE0
And here’s the working debug output from this morning when it launched fine:
...
[00:00:00.000] 5448 Terrain: Unload
[00:00:00.000] 5448 Terrain: Load
[00:00:00.000] 5448 Terrain max texID: 3991
[00:00:00.000] 5448 SoundDriver 0x00000000192030A0
[00:00:00.000] 5448 Sound SetCooperativeLevel HWND=0xc0bfe
[00:00:00.000] 5448 CreateSoundBuffer
[00:00:00.000] 5448 QueryInterface IID_IDirectSound3DListener
[00:00:00.000] 5448 Listener SetDistanceFactor
[00:00:00.000] 5448 Reading comm data from XML -> C:\Falcon BMS 4.37\Data\Sounds\commfile.xml
[00:00:00.000] 5448 Reading eval data from XML -> C:\Falcon BMS 4.37\Data\Sounds\evalfile.xml
[00:00:00.000] 5448 Reading frag data from XML -> C:\Falcon BMS 4.37\Data\Sounds\fragfile.xml
[00:00:00.000] 5448 SFX loading took 1583 ticks
[00:00:00.000] 5448 Version: R 1329. 1.37.EBS.4_ | Oct 25 2023 | 18:47:29 | MSVC 1937
...
So, yeah, clearly something sound related. I guess if anyone else runs into this, try either: a) rebooting, or b) changing your audio device outputs.