tf2_bot_detector
tf2_bot_detector copied to clipboard
PazerOP
[BUG] TF2BD Crashes when you click "Launch"
When I updated to this new version of TF2BD it crashes upon clicking launch. I reversed the launch option changes needed for the temp fix and everything, it still crashes, even on a fresh install with the default cfg files.
To Reproduce Install latest version of TF2BD Run TF2BD Click "Launch" Crash
I'm using Windows 10 TF2 Bot Detector V1.2.1.934
I will provide a mdmp crash dump file if that helps. https://puu.sh/HSmoK/e7417dd925.mdmp
Try nightly build 1.2.1.939 when you have a chance and see if it fixes the crashes. The tool might be failing to determine your command line arguments for some reason, so you'll probably see some error messages in the bottom right pane once tf2 opens.
Try nightly build 1.2.1.939 when you have a chance and see if it fixes the crashes. The tool might be failing to determine your command line arguments for some reason, so you'll probably see some error messages in the bottom right pane once tf2 opens.
Could I get a link to that? I'm not seeing it in the asset list for 1.2.1.939
https://github.com/PazerOP/tf2_bot_detector/suites/3156248596/artifacts/72585621
@Phencyclidine08 is this still an issue?
Yes. This is still occurring on the latest version. That nightly build links to a 404 error. I'd still like some help with this. I find it so strange that it worked fine for the longest time, then after V1.2.1.934 it crashes and never even opens TF2.
Here's a video of what's happening. https://www.youtube.com/watch?v=dUgXdm2EEMM
Special characters can cause issues in paths. Artifact links usually expire after a few days.
tf2-bot-detector_x64-windows_1.2.1.956_Release.zip
Special characters can cause issues in paths. Artifact links usually expire after a few days.
That build you provided worked, it opened the game and appears to function. My game usually opens in borderless windowed mode, and for some reason launching through this version of bot detector loads it in windowed mode. Any idea why that would be happening?
Might it be too long command-line parameters string, that the game could not properly read?
what do your steam launch options look like?
My launch options are the following;
-no_texture_stream -novid -nojoy -nosteamcontroller -nohltv -particles 1 -windowed -noborder