Game doesn't start after clicking Play on the Launcher

[Juarez6]

I Just installed the game today and I'm running v0.13. After I hit play nothing happens. I see the game pop up in the task manager but after a few seconds of ramp up it just disappears. I've tried deleting the document file and I've tried changing the read-only setting but when I right click it again its ticked as read-only again I'm not sure what I'm doing wrong there. Also I understand that you need the logs/ crash files to help me but I've never done this before so I'm not sure if I'm supposed to just open latest one and copy paste the contents in it or what. Pls help 😞 

[Joe]

same problem here, when I start I hear the "bing" sound tho

[Maex91]

same problem here too

[MarcoMaar]

If you are on Windows you can locate your logs in: %userprofile%\Documents\BattleForge\Diag
Please upload your latest logs by attaching the file _log_proxy_latest.log when replying here

Edited January 28, 2022 by MarcoMaar

[ccaballer]

double posting

1 minute ago, ccaballer said:

double posting

22:52:14.769 WARN 4160 proxy:94 proxy from 2022-01-10T10:35:13.166134200Z is initializing
22:52:14.769 INFO 4160 proxy::patches::lua_functions:28 lua hooks initialized
22:52:14.769 INFO 4160 proxy::patches::lua_functions::gds:16 lua gds hooks initialized
22:52:14.769 INFO 4160 proxy::patches::lua_functions::cpg_card:20 lua card hooks initialized
22:52:14.771 INFO 4160 proxy::patches::changes::half_orb:32 half orbs hooks initialized
22:52:14.772 INFO 4160 proxy::patches::map_presets:55 tests hooks initialized
22:52:14.772 INFO 4160 proxy::patches::inventory:21 inventory hooks initialized
22:52:14.772 INFO 4160 proxy::networking::connect:172 connect disconnect hooks initialized
22:52:14.772 INFO 4160 proxy::networking:34 networking hooks initialized
22:52:14.772 WARN 4160 proxy:118 Initialized successfully
22:52:14.773 WARN 4160 proxy::logging:64 code: 406d1388
22:52:14.773 WARN 16208 proxy::logging:64 code: 406d1388
22:52:15.076 INFO 4160 proxy::logging:164 src="Direct3D 9" message="Start Scan"
22:52:15.109 INFO 4160 proxy::logging:164 src="Direct3D 9" message="Found Adapter: NVIDIA GeForce RTX 2070 with Max-Q Design"
22:52:15.109 INFO 4160 proxy::logging:164 src="Direct3D 9" message="Support Hardware vertex processing"
22:52:15.109 INFO 4160 proxy::logging:164 src="Direct3D 9" message="Support SM 3.0"
22:52:15.109 INFO 4160 proxy::logging:164 src="Direct3D 9" message="End Scan"
22:52:15.109 INFO 4160 proxy::logging:164 src="Direct3D 10/10.1" message="Start DXGI scan."
22:52:15.112 INFO 4160 proxy::logging:164 src="Direct3D 10/10.1" message="Found Adapter: NVIDIA GeForce RTX 2070 with Max-Q Design"
22:52:15.190 INFO 4160 proxy::logging:164 src="Direct3D 10/10.1" message="Supports 10.0 and 10.1"
22:52:15.190 INFO 4160 proxy::logging:164 src="Direct3D 10/10.1" message="End DXGI scan."
22:52:15.191 INFO 4160 proxy::logging:164 src="app" message="BattleForge Final Build: 400031 (Retail branch)"
22:52:15.191 INFO 4160 proxy::logging:164 src="app" message="CPU GenuineIntel family 6 (P2, P3, Pentium-M, Athlon) detected."
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 8380 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 14244 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 8308 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 20260 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 20420 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 6056 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 11320 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 5868 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 15544 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 5792 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 4160 proxy::logging:64 code: 406d1388
22:52:15.191 WARN 7680 proxy::logging:64 code: 406d1388
22:52:15.192 WARN 14328 proxy::logging:64 code: 406d1388
22:52:15.460 WARN 4160 proxy::pcre3:84 RegexMatcher {
    regex: .*GeForce .*7[0-5]...*,
    options: 1,
} vs NVIDIA GeForce RTX 2070 with Max-Q Design find? Match { text: "NVIDIA GeForce RTX 2070 with Max-Q Design", start: 0, end: 41 }
22:52:15.460 INFO 4160 proxy::logging:164 src="app" message="CPU clock speed is ~2592 MHz."
22:52:15.460 INFO 4160 proxy::logging:164 src="app" message="CPU has 12 cores."
22:52:15.460 INFO 4160 proxy::logging:164 src="app" message="CPU rating is 16 points."
22:52:15.460 INFO 4160 proxy::logging:164 src="app" message="GFX rating is 6 points."
22:52:15.695 TRACE 15860 proxy::patches::inventory::filter::prepare:314 loading took: 274.1376ms
22:52:15.779 ERROR 4160 proxy::logging:166 src="BASE" message="Unhandled exception error. Crash dump written."
22:52:15.779 ERROR 4160 proxy::logging:166 src="BASE" message=""

Edited January 29, 2022 by ccaballer
error

[Juarez6]

_log_proxy_latest.log

[MarcoMaar]

Thanks for the logs.
Did you try installing directx 9.0c?
 

You can check the troubleshooting guide  that I linked.
Specifically:

• 10. Force BattleForge to run in DX9 Mode
• 8. Check whether you have DirectX 9 and Visual C++ prerequisites/redists installed 

 

Edited January 29, 2022 by MarcoMaar