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

rynthas

Members
 View Profile  See their activity

  • Content Count

    7

  • Joined

  • Last visited

Community Reputation

0 Neutral

About rynthas

  • Rank
    On the Coast
  1. rynthas
    Yep. Updating through steam, or installing the beta through Steam, leaves me with .102678, whereas everything seems to be running .102591. I tried blowing out the beta folder and installing from the patch via dayzcommander, but it promptly threw a "wrong CD key" error, and the problem persisted after I attempted to run it. BIS's patch site appears to be undergoing maintenance. Looks like I'm just screwed.
  2. rynthas
    So it's looking increasingly like this might have something to do with the beta version. I validated Steam's cache, which evidently reverted it to a previous one. Everything was working great...until I tried to join a server, and had to update...
  3. rynthas
    Already tried that. Like I said, it works fine in every other application and does not have a profile set for any specific app -- it's universal across all windows apps.
  4. rynthas
    I've tried the six launcher in admin mode, dayz commander in admin mode, and steam in admin mode -- and tried to set both ArmA and OA's executables to run that way manually. Nothing works, the same condition persists.
  5. rynthas
    To the best of my knowledge, yes. Given that I'm using a launcher sometimes, I'm not sure how to see exactly what priv levels it's running at -- but with Steam, I imagine it's launching dayz and OA at the same priv levels, and the same glitch happens when launched like that as well.
  6. rynthas
    Pressing them on the KB in game works as expected. The mouse config is system-wide, and as I said works fine in vanilla OA. It's just that in DayZ, it produces no results at all. Only in DayZ, I might add.
  7. rynthas
    I have no idea how the hell this happens, but I'm using a MS Intellimouse 3. I've got the two side buttons bound to keystrokes, [ and ] respectively. If I start OA normally through steam, ArmA picks up those button presses fine. If I start up DayZ through DayZ commander or through Steam, it does not recognize those buttons at all. I can press the corresponding keys on my keyboard, and it'll pick them up, but the mouse buttons just don't work. Yes, [ and ] are bound in the config. Even if I try to rebind them, pressing the mouse buttons does nothing at all. Those mouse buttons work in literally every other app just fine as well, producing the same keystrokes. I'm utterly boggled, but since these are my "do action" and "cancel" buttons, it's driving my nuts.
×