simultaneous input mouse?

[NoStateofMind]

Does it exist? Google turns up nothing. Would like a mouse that will allow input while others are pressed. Don't have much hope of finding this though....


This pertains to gaming BTW

 

[Aluvus]

Other what?

 

[Bryf50]

Um well if I understand what your asking. The ability to press both the left and right button is pretty standard. A lot of games wouldn't work well without it(Standard FPS controls are usually right click to bring up the sights and left to shoot). For what it's worth my Microsoft laser mouse 5000 does it for sure.

 

[NoStateofMind]

Um well if I understand what your asking. The ability to press both the left and right button is pretty standard. A lot of games wouldn't work well without it(Standard FPS controls are usually right click to bring up the sights and left to shoot). For what it's worth my Microsoft laser mouse 5000 does it for sure.

Yeah sorry I wasn't more clear. I'm "quick scoping" in a game but instead of using the last weapon used button I just right click to unscope right after firing. However there are times I scope in, intend to fire but instead unscope. Was hoping there was a mouse that would allow simultaneous input so I can guarantee a shot every time. I think there may be three solutions/problems with this. Either this mouse doesn't exist, the game wasn't designed for that kind of mouse input or I just need to suck it up and learn not to be greedy with speed.

 

[zagood]

That's game input. Try a mouse or keyboard macro instead.

 

[Ross Ridge]

Yeah sorry I wasn't more clear. I'm "quick scoping" in a game but instead of using the last weapon used button I just right click to unscope right after firing. However there are times I scope in, intend to fire but instead unscope. Was hoping there was a mouse that would allow simultaneous input so I can guarantee a shot every time. I think there may be three solutions/problems with this. Either this mouse doesn't exist, the game wasn't designed for that kind of mouse input or I just need to suck it up and learn not to be greedy with speed.

It still not clear what you're talking about, but the problem you're having doesn't sound like it's related to the mouse hardware. If you hold down the right button and then press the left button all mice will send a signal to the PC indicating that the left button was clicked. In fact the mouse will send a sequence of messages saying the right button has been pushed down, the left button has been pushed down and then left button has been released as each of these events happen.

How those sequence of events ends up getting interpretted depends on Windows and the game you're playing. Your problem seems to be that your clicks aren't being interpretted the way you expect them to be.

 

[Ben90]

It still not clear what you're talking about, but the problem you're having doesn't sound like it's related to the mouse hardware.

This. Just sounds like the game engine sucks hard.

 

[ChAoTiCpInOy]

What game are you playing?

 

[NoStateofMind]

What game are you playing?

Day of Defeat Source. Right click to scope, left click to fire then right click again to unscope. I know I'm clicking to shoot but sometimes it registers the right click instead. Did I clear it up a bit?

 

[Ben90]

Sounds to me like you are passing commands too fast for your/server's cmdrate.

Each cmd period will process the commands you send to the server. If multiple commands are sent during the same period, the server sees these commands as being sent at the same time. Most commands won't conflict with each other, but some will as is most likely your case.

For example you can "+moveleft;+speed;use weapon_x" at the same time without problems, but "use weapon_x" will override +attack. It appears to be the same with +attack2 overriding +attack in your case.

The only real solution to the problem is to make sure you are sending as many cmds as possible. Without delving too deep into the new (shitty) OJB source engine, making sure you have optimal rates will help this problem substantially. Specifically cl_cmdrate in this case.

Even if your cmdrate is set to the servers maximum, your frame rate can limit this value as well. Obviously we want to be pumping 100+ fps. Although since the OJB engine, 66+ is acceptable as most servers are running at 66 tic with a 66 sv_maxcmdrate. For most purposes we want to use the following commands unless your internet is complete crap.

rate 55555555555
cl_cmdrate 554352
cl_updaterate 342342
fps_max 0

Before we get the followers that will cry "omgz YOU DIDN'T SAY CL_CMDRATE 101 CL_UPDATERATE 101", open the console and just use insanely high numbers because the server is going to be the one that determines what the maxes will be. Z_block might be a wise and beautiful woman at times, but if it is just do what it says. The makers of Z_block got pretty retarded anyways. They don't know that fps_max 0 >= fps_max 66.

Anyways back to the problem. Verify your cmdrate with net_graph. If you already have followed the steps above and it persists, you are just going to have to accept the fact that you cannot execute +attack2 within 1000/cmd milliseconds of an +attack, else it will overwrite +attack.

 

[ChAoTiCpInOy]

It could be your mouse?

 

[Ben90]

It could be your mouse?

No, any PS/2 mouse onwards can handle this (aka any mouse made after 1987). Its the Source engine.

And just to prove this to yourself OP, type this in console.

bind mouse1 "+forward"
bind mouse2 "say my mouse can detect both buttons at the same time"

/thread