Jump to content

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

wompshmack

Members
  • Content Count

    1
  • Joined

  • Last visited

Community Reputation

0 Neutral

About wompshmack

  • Rank
    On the Coast
  1. My first guess was that this is related to the old bug where you had to actually run each game without the mod first before you try to run it with the mod. Steam can be really picky about things like that. So I tried that without success. Then I noticed that it was installed to a different steam library location than the rest of Arma2. So I uninstalled the Dayz mod, then I ran both Arma2 and Operation arrowhead without having it installed. Then I reinstalled it to the same steam library as the rest of my Arma files, and that solved the problem. I hope this helps someone! Likewise, I had the same problem with the beta. It was giving me the same error trying to run Dayz with the beta patch, and sure enough, it was installed to the other library. So I reinstalled it to the same library as everything else, and I ran it before trying to run Dayz again with the beta patch. Once again this solved it.
×