Illiad

I fail to see how they were being abusive in a sexual harassment way... White knights being white knights because they "victim" was a girl. They obviously spoke no english, and were saying, "huh?" "Wha?" "Hm" What was sexual harassmenty about this? What people should take from this video is that guy was punching the player, and the player fought back and owned them... has nothing to do with gender.

As the topic states, still no word or fix on this matter. I, and many many others, want to be able to test this game for you properly, however the inability to rebind left and right click on the mouse is rather cumbersome to this process. For example, if I bind left click to move forward instead of fire, and bind right click to fire, the game does not recognize this. Instead, it causes left click to move forward AND fire simultaniously, and right click is unresponsive. The bug was reported first week that SA dropped, with many others experiencing the same issue. Surely this issue isn't hard to rectify?

thebrotherhood.guildlaunch.com Odd! WWW.CLANAOD.NET Signed, AOD_Spec_iLLiaD*LT*

I want to see female models with hairy arm pits. It IS russia, after all.

I'm proud of you. My little boy's all grown up!

Pro set up. What I am using is w = scope s= straff left d = straff right c = move backwards z = crouch x = prone a = stand up/jump over LMB = move forward RMB = fire

http://feedback.dayzgame.com/view.php?id=343

TL:DR? The fire function is hard coded to Primary mouse button even when there is nothing assigned to the fire function. Binding anything to LMB will result in that function, as well as fire function being executed simultaniously. Tested, retested, isolated, verified. There are a couple other functions that have a similar issue, and I've been keeping track of it on the bug report. If you want Mos1ey, I can link the bug report?

You are welcome to test this out on your own client. Assign primary mouse to move forward, and secondary mouse to fire. See what happens when you try it. I've already gone through the config file process, so it's not really required to verify that route, but you can try to see if you can find a fix. if 65536 is only assigned to three functions, move forward, car forward, and helicopter up (which I've unbound just to be sure it wasn't a conflict), then there's absolutely no reason why 65536 should be firing unless somewhere in the code, it's hard coded. One more thing. I've tested this further, once before I reported, and once tonight, where I set controls to default and change NOTHING, and close the client. Opening up the profile config file, I manually input the key values for each of the functions I want changed. Even doing that, the same issue remains.

Alright so I changed the number to 65537 as per your fix for the RMB as move forward. That's the number you used in your config file to bind RMB to moveforward, so I put it where fire is, and made sure it did not repeat anywhere else. When I enter game, RMB is still unresponsive (Won't fire), and in the config UI, it has listed 2xSecondary Mouse. Double clicking RMB is unresponsive as well though. So it still appears that LMB is hardcoded to fire(The LMB number function does not repeat at all in the config file, so it's only assigned to move forward, car forward, and helicopter thrust up). I've changed the number back to 65665, made sure it doesn't repeat, and relaunched the client. Same issue still, and the config UI only lists 2xRMB. Some information that may help solve the issue: The list of commands on the right side of the bind window that you can select to bind to that function do NOT include secondarymousebutton. I removed 2xRMB, and manually (by clicking RMB in the left portion of that UI) input RMB to fire on a blank window. It now has Secondary mouse button listed, but it's unresponsive, and LMB still causes move forward and fire simultaniously. Another interesting bit of information. When I check the config file after closing the client when I had 2xRMB, RMB, and hold RMB bound to fire, the config file still only lists 65665 in the fire value. Again, to the condescending gentleman who thinks he knows everything, LMB is ONLY bound to my move forward functions, and nowhere else(value 65536 in the config file). Verified in both the config UI and the profile config file. RMB is ONLY bound to fire. It does NOT repeat anywhere.

So as I stated regarding the cfg file, I had already tried this route prior to reporting it (Hoping I could come up with a fix for the issue so I knew what to tell people to do just in case), and here is the deal. keyFire[]={65665}; keyMoveForward[]={65536}; Now... keyfire is bound to right click according to the cfg file. 65665 is RMB MoveForward is left click according to cfg file. 65536 is LMB No? That's what it was in Arma 2, so I assumed it is what it is in SA. I verified these two numbers by loading a default keymap, and checking the profile config file, verified that. While in game, left click performs both functions simultaniously, and right click is unresponsive. I will search the file and use the numbers you provided, but this could be a clue as to where the bug is coming from. The config UI is binding the numbers improperly, and the engine isn't recognizing it. Thoughts? :Edit: I use a razor abysus mouse, could the issue be related to the hardware inputting a flawed input function?

As I;ve stated in the bug report, this was done, tested and retested, and it doesn't work. I unbound left and right click from their default settings. EG: Fire had not binds assigned, and walk had no binds assigned. They were blank. I assigned left click to move forward, and right click to fire. Left click moves forward and fires at the same time, and right click is unresponsive. The settings were even changed remotely in the config files, and still no fix. Don't be condescending if you don't know the whole story, that's not how things get fixed. @Mos1ey - Thanks, I'll have a look and see if this helps.

Same reason you want to use the default controls over anything else.

If you had been playing FPS for two decades, and were used to one setup over the other, and it was anything but the default settings and you were unable to change it, you would be bringing it up too. This effects a wide range of players, and just because it doesn't effect you doesn't mean it's not a valid concern.

Here's another person having this issue that I found with a quick google search. http://steamcommunity.com/app/221100/discussions/5/648814843694581611/ and another concerning the right mouse button http://steamcommunity.com/app/221100/discussions/5/648814738466727200/ Others http://forums.dayzgame.com/index.php?/topic/158217-bug-binds-assignment-mouse-buttons/

I'm so tired of everybody LoSing! Everywhere I go, I see people LoSing! It's not fair! When will this mentality fade? Can't we all just shoot eachother instead? LoSing is ruining the game. If I wanted to play a loot on sight game, I'd play WoW.

Oh.... People thought I was serious... For those who need it spelt out, this is satire in relation to the KoS threads.

Can you take your hand off my junk please?

Not all Roleplayers are noobs. I KoS quite a bit, I also bandit it up in character... PVP focus, but RP... weird concept for some I guess, lol. It's not "roleplaying noobs", it's "PVE carebears", get it right.

So you're a noob?

Somebody actually downvoted this.... what the hell?

Wait, so you play with default controls? lol.

EXACTLY! MY group is better suited to survive than a group of nameless randoms we dont' know or give two shits about. If you aren't in my clan, aren't part of the wolf pack, you are KoS. Simple. There's too much risk involved in letting you live, because your survival in our vicinity COULD be detrimental to OUR group.

if 50% of the population in game is friendly... hell, even 98%, I would rather kill you than fall victim to the 2% that will kill me. Simple as that.

That's just it... with multiple survivor groups, it IS war. It's us, or everyone else... I'd rather it be everyone else.