Page 1 of 1

Gadget: Check if BoD has crashed...

Posted: Sat Jul 13, 2019 5:38 am
by Sryml
In BoD games, there are engine bugs, such as shadows + camera shots that cause the game to crash, or logic errors in the script.
In win7 or higher systems, BoD crashes are annoying. It delays any of your keyboard input, no matter what key you press, it puts the entire computer in a state of fake crash, often waiting 40 seconds or more before you can close the crashed game.

I talked about the fake crash, because only the Blade.exe process is not responding, and other processes are working normal. So we can use an external process to check if the BoD game has crashed. When BoD crashes, it will pop up Blade has stopped working, let the external process kill the Blade.exe process.

With the dos command, it can close the crashed Blade in 3 seconds.
@echo off
setlocal enabledelayedexpansion
set n=0
echo Check if BoD has crashed...

tasklist /FI "WINDOWTITLE eq Blade" | find /i "WerFault.exe" >nul && (taskkill /f /im WerFault.exe /t >nul & set /a n=!n!+1 & echo BoD has crashed !n! times.)
timeout /t 2 /nobreak >nul

goto loop_check
Copy the code to a text document and save it as CheckBodCrash.bat. Run this script and it will loop check the BoD. The period is 2 sec.

In "Ruins_M4", open the temple lock and enter the gate. If you turn on the shadow and the camera is facing the left and right flames, it will cause the game to crash.

The video is not accelerating, this is the real response time, about 3 seconds.