Maraneshi

It should be impossible to even *start* APB on that GPU since it doesn't have driver support for D3D11 nor hardware support for feature level 10_0.

Okay so I feel like I've seen this crash before. It's very bizarre since all it tries to do is create/rewrite the commands.txt file in the documents folder but somehow it can't open the file and crashes. From the dates of the files in the screenshot I can see it was able to open engine.cfg in the same folder just fine. I have absolutely no idea why this would happen. You could try deleting commands.txt and see whether that helps. In case that does not work, I've put in a check so it shouldn't crash anymore when this fails, but I can't guarantee that it won't crash somewhere else later from a similar error because I simply have no idea why this would fail and I'm not very keen on trying to find all the places where we access any files in the engine to try and safeguard them. I don't think I'm allowed to distribute the fix to you individually and you'll have to wait for a new APB patch to be released if deleting the file doesn't help.

So, this is a bit annoying because the game doesn't even get to its crash reporter to produce a memory dump for us to analyze, which leaves us with basically no information whatsoever. You're going to have to tell Windows to automatically generate crash dumps when this game crashes. The process is documented here: https://docs.microsoft.com/en-us/windows/win32/wer/collecting-user-mode-dumps I have made two reg files for you to automate this process (enabling/disabling the crash dumps). disable game exe crash dumps.regenable game exe crash dumps.reg After enabling the crash dumps and trying to run the game you should be able to see a .dmp file appear in the folder %LOCALAPPDATA%\CrashDumps (just paste this into your explorer address bar or manually navigate to C:\Users\<yourusername>\AppData\Local\CrashDumps). If you could upload that file (or a zipped version, it compresses really well), we can at least try to figure out what is going on.

AVG is known to have flagged literal "Hello World!" programs as viruses. If your executable is not signed by a big company and whitelisted it's pure luck whether you get blocked or not.

Betting on anti-virus here too. AVG and Avast (same company) are known to flag our game for whatever reason and shut it down immediately without any notification. Unfortunately we can't really do much about that on our end.

DxDiag shows Win7 SP1. Hardware is very old but barely above minimum target for 5.0 so it should run.

This was for the error in the launcher log. The entire thread has been a bit confusing. I said "if the launcher still does not work", then try that update. Since the launcher clearly works, there is no issue here. I'm still betting on anti-virus.

Have you tried adding the APB game exe as an exception to your anti-virus program (particularly AVG seems to dislike it for unknown reasons)? If that doesn't solve it, what hardware (CPU, GPU) and operating system are you running on?

The launcher already runs as admin (since we haven't been able to decouple the install process yet and it's almost impossible to launch a process with lower privileges from one with higher privileges). Compatibility mode is not necessary. I'm betting on anti-virus blocking it for whatever reason (particularly AVG seems to dislike our game).

Are you trying to connect to the APB server from a Renegade client? APB hasn't been playable from Renegade in a long time. It is a standalone mod on a version of the engine that is incompatible with the original. You need to install APB from our launcher to play APB.

Sorry, I somehow missed this thread. 1. The error log is from the W3D Launcher and it says it can't establish a secure connection. If the launcher still does not work, please update your Windows. https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392 2. The crash dump is from Interim Apex, not APB. Unfortunately the dump doesn't seem to contain any useful information. Does this happen consistently?

My best guess from the dumps is that the game fails to open the following path: "C:\Users\ZOOL\Documents\W3D Hub\games\apb-release\commands.txt" Make sure the path exists, your user account has write permissions and your antivirus doesn't block the game for some weird reason (seems to be AVAST?).

Yeah, we've confirmed that the allied ore truck causes the slowdown in a few cases. However, the root cause of why this even happens is yet unknown. Currently working on finding it by running a server with special checks in place 24/7 and constantly fixing related things but it takes many many hours to do so.

This laptop has an integrated GPU from 2008. I'm surprised it can run anything at all. It straight up doesn't support MSAA.

As I said, they're identical.