Hi there — thanks for the report, sorry it’s broken.
This is a new one for me, and apparently for googling “winrt::hresult_error godot” as well. We upgraded to godot 4.7 between the two builds, which is where I bet such a low-level sounding error is coming from.
Looking at the engine’s changelog, it looks like that WinRT (some sort of generic windows driver error?) might have come from changes in accessibility or audio interfacing – if you have any hardware drivers like tablets, screen readers, screen overlays, or complex audio setups that might be the contributing factor.
From what I’m reading it sounds like we might be able to get more information from running that console version of the game in verbose mode (I should probably add a shortcut that lets you do it automatically). If you open up a terminal at the game’s folder (shift+right click an empty space in the folder and pick “open in terminal”), you can run it in verbose mode with this:
.\LancerTactics.console.exe --verbose
And we might get some more hints with that?