Jump to content

Zone15

Member
  • Content Count

    7
  • Joined

  • Last visited

  • Medals

Community Reputation

10 Good

About Zone15

  • Rank
    Rookie
  1. It seems EVERYONE using a nVidia graphics card are crashing now which is a MAJOR issue. If you cannot quickly fix this issue, you need to officially roll back the patch.
  2. The A3 Feedback tracker isn't sending me a confirmation email so I have been unable to create a ticket.
  3. Where do we go about finding those files to upload them? BTW, now I'm just getting a freeze, then after a few seconds a black screen. I am able to alt+ctrl+del to bring up the task manager and have to manually close Arma 3. I'm not getting any crash message because I have to manually kill the Arma 3 process in the task manager. I talked to a friend of mine and he is having the exact same issue playing the King of the Hill mod. It is apparent this is a broken patch and needs to be rolled back until you can figure out what is causing everyone to crash. I'm just looking at the list of servers I usually play on and they are all at about half the number of players as usual due to all the crashing.
  4. I'm getting the exact same issue. No error message or anything, just a hard freeze that requires me to physically press the reset switch on my case. I've never had any issues with the game until today. At first I thought I was having some sort of hardware failure then I read online where everyone else is also crashing. This patch has pretty much broken the game for me, I cannot play more than 5 minutes without a hard lockup.
  5. It is not just me and reinstalling doesn't help. A few guys I play with have the same issue and I also had found a forum post with someone else experiencing the same issue.
  6. Ever since one of the new Battleye updates a week or so ago, the MSI Afterburner/RTSS overlay no longer works. I use this to monitor things like my FPS, GPU Temps, and CPU Temps. This also prevents you from using Afterburner to take screenshots or record video. Does anyone have a workaround to fix this?
×