DayZ, somehow, kills mouse buttons in-game.

[rynthas 0]

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.

[Rage VG 4033]

Try just pressing [ and ] from your keyboard as opposed to from your mouse. This will allow us to identify whether it's an issue with the mouse or the app.

Edited March 21, 2013 by Rage VG

[rynthas 0]

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.

Edited March 21, 2013 by GV00

[Rage VG 4033]

Then the problem possibly lies with the mouse, but perhaps it's not a hardware one.

Does DayZ have administrator privileges when you try to play?

Edited March 21, 2013 by Rage VG

[rynthas 0]

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.

[LegitOldSchool 261]

Your Arma II / DayZ Commander starts with administrator privileges, you have to start your mouse customization software as an administrator as well, I was having the same problem until I found out why. Press Ctrl-Shift-Esc, find your mouse software executable, open the executable location. Then close the process, go where the executable is, right-click it and in properties go to compatibility. Check the box that says "Run this program as an administrator". You will need to start it manually when you reboot from now on because it can't run as admin by itself on startup. Hope this helps.

Edited March 21, 2013 by EchoZeero

[Rage VG 4033]

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.

If you're using Windows 7, its icon should have a Blue-yellow checkered shield icon in the corner of its toolbar icon.

Steam won't launch games as an admin unless it is running as an admin itself.

[rynthas 0]

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.

[Rage VG 4033]

Okay, can you tell us if your mouse has its own program that runs alongside it/its drivers? My trackpad has, and I noticed there were some odd things going on with it until I tinkered with the program.

[rynthas 0]

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.

[Rage VG 4033]

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.

I'm aware, but if that program doesn't have admin rights, it sometimes goes FUBAR, at least for me. Motion gestures were doing random things at random times.

But if you've tried it, then I'm stumped, I'm afraid.

[rynthas 0]

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...

[rynthas 0]

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.