Jump to content
DayZ Forums

Forums Announcement

Read-Only Mode for Announcements & Changelogs

Dear Survivors, we'd like to inform you that this forum will transition to read-only mode. From now on, it will serve exclusively as a platform for official announcements and changelogs.

For all community discussions, debates, and engagement, we encourage you to join us on our social media platforms: Discord, Twitter/X, Facebook.

Thank you for being a valued part of our community. We look forward to connecting with you on our other channels!

Stay safe out there,
Your DayZ Team

tardis609

Members
 View Profile  See their activity

  • Content Count

    28

  • Joined

  • Last visited

Everything posted by tardis609

  1. tardis609
    What's the matter with DayZ/Arma/BattleEye/whatever? I have a friend that I'm trying to work with to solve this on his update to the latest 94362. Failing everything else, I'm going to run my system logger and post every inquiry (relevant ones) the launcher makes to the registry or to the file system - and to the ports. If that doesn't produce an answer, I'll run a profiler and hack around the bug by feeding back whatever the system is looking for (obviously, though, that would be hard if it's looking for a time-dependent CRC (or other) number from BattleEye or Arma or DayZ) This is just crap. Worse that EA/DICE/PB on Battlefield 3, and that's saying a LOT! Rocket - please fix this shit - don't ignore your fans.
  2. tardis609
    Y'all make it way to difficult. Here's the problem; dumbass patch maker. Solution. Goto to the arma2 beta directory where arma20a.exe lives. Check the version. If it is NOT 94209, then DELETE it and re-run your patch. It will install the correct version. You're good to go. For some reason, the software patch maker couldn't figure out the 'file delete' call.
×