snwyvern
Pathfinder-
Content Count
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
News
ATLAS Links
Gallery
Everything posted by snwyvern
-
Installing 1803 resulted in a BSOD error whenever atlas launches. (Hey, that's something, right?) I reverted even further back to 1709, and I'm able to play. You know. After configuring this old-ass Windows build with NVMe support. Great job, team. Keep up the barely meeting of expectation.
-
This issue is persisting beyond the patch just issued this evening. Great job, team...
-
Thanks for the attempt at help-- (At least in my/those of us who are being hosed by Battleye case) It's not a permissions issue, nor is it an antivirus issue, as it persists even with WIndows' antivirus functions turned off.
-
This is a continuation of in the hopes that this forum is monitored by more appropriate persons; Trying to launch the game produces a Battleye error. If the non-battleye executable is launched, the game can be played (offline...) Any help would be appreciated. And no, the battleye FAQ is not helpful here.
-
After the update that dropped in the last hour or so, I'm still not able to launch.
-
That still produces the "Failed to launch game" error. Thanks for the attempt at help.
-
I'm having the same problem. I can launch Atlas without battleye (%ProgramFiles(x86)%\Steam\ steamapps\common\ATLAS\ShooterGame\Binaries\Win64\AtlasGame.exe) But Atlas with battleye (...AtlasGame_BE.exe) produces the same error. Dear Battleye: LEARN THE DIFFERENCE BETWEEN UNIVERSAL ENVIRONMENTAL VARIABLES AND LOCAL ENVIRONMENTAL VARIABLES. (Yes, it's a Battleye error.) The error changes if you put a copy of AtlasGame.exe into (%ProgramFIles%\Steam\ steamapps\common\ATLAS\ShooterGame\Binaries\Win64\) which anyone with a 64 bit system shouldn't have-- And it still doesn't fix it, as that's the sort of shenanigans that Battleye is looking for.