Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post
Bungie Answered

Game self-closes / crashes shortly after launching

When I hit Play on Steam the game launches and I briefly see the "loading" cursor icon but the taskbar window never appears. The BattleEye Launcher shows up and gets to the "Launching game..." step, then disappears. After a few second the cursor goes back to normal, the Marathon Task Manager process exits, and Steam's button goes from "Stop" back to "Play". 

I have tried:

  • Updating to the latest drivers
  • Verifying integrity of game files in Steam
  • Reinstalling BattleEye using the batch files in the game directory, with admin
  • Skipping the launcher and running Marathon.exe with admin
  • Disabling all overlays except Steam's

Don't tell me to try:

  •  Flashing my BIOS. I don't have the gear to back up my hard drives in case it bricks Windows. Also, no other game or software has ever required this over multiple decades.

My specs:

Nvidia RTX 2070 Super (8GB VRAM)
Intel i5-3470 @ 3.2 GHz

16GB RAM
Windows 10

0

Kommentare

  • Offizieller Kommentar

    Hello there,
    Thanks for the detailed report, and I’m sorry you’re running into this.

    We have seen reports of Marathon failing to launch properly on Steam, including cases where restarting the Steam client allowed the game to patch correctly and launch afterward. The detail that the Marathon process starts briefly, never reaches a taskbar window, and then exits back to Steam is helpful context.

    Since you’ve already gone through the common checks like drivers, file verification, BattlEye reinstall, and reinstalling the game, we’ll continue tracking reports like this.

  • It seems it might be related to my CPU lacking AVX2

    0
  • I could be wrong, but I believe that my CPU has AVX2 and I'm still experiencing the issue.

    1
  • nullHeretic ah, damn. Thanks for the update.

    0
  • That's cool I guess you don't want my $42 that badly

    0
  • Hey man, I don't know if you'll see this, but try moving the game from external drive storage to your device's local/native drive. That's what fixed the issue for me and another.

    1
  • nullHeretic thanks I'll give that a try if I can find enough space!

    0
  • Let me know if that works! If it doesn't, reach out to Bungie again! Messages slip through the cracks sometimes.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.