For a long running list of reasons, I use the legacy WT launcher (non-steam). However, I still want Steam features like SteamRecord - so far I’ve been using a workaround by launching aces_be.exe as a non-steam game to get the overlay on it, but that stopped working today. Is anyone else facing this issue? The game will launch from beac_wt_mlauncher.exe or launcher.exe, but these unfortunately aren’t the direct game process, so Steam won’t hook correctly into them.
There was a BE update that i got this morning, might haev something to do with that maybe?
Possibly. I’ve found a workaround: If aces_be.exe is started manually from the game folder, and then from Steam within a few hundred milliseconds, the game will actually launch again and with the Steam Overlay hooked into it. It’s not reliably reproducible though, and only adds to questions as to what went wrong to require this.
It’s definitely BattlEye. With the right timing I can get it working as my old setup was, but otherwise BE will just fail init and kill the process. I’ve managed to get it working by statrting 2 processes of aces_BE.exe with a batch file, but even this is unreliable and hardly a fix, since it leaves a zombie process running in background.