Create an account


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
What's your mouse?

Logitech MX620
[Image: logitech_mx620_cordless_laser_mouse.jpg]

pro:
- 1k dpi
- long battery life (many months)
- good fit in hand
- not too heavy
- good refresh rate (I can draw circles and they are circles)

con:
- still, it's wireless (but I have to :-( )
- righthanded only
- only 1k dpi
- the wheel is too loose - can't wheel click without rolling or swinging to the sides & have to precisely click straight down cause if it catches the wheel click as wheel left/right then it won't work :-P
My contributions to Xonotic: talking in the forum, talking some more, talking a bit in the irc, talking in the forum again, XSkie
Reply

I use a SteelSeries Xai -- nice mousie Heart

there are not many who fit for left-handed peepz

GreetZ Su
Reply

(10-23-2012, 08:53 AM)Cyber Killer Wrote: Logitech MX620
[Image: logitech_mx620_cordless_laser_mouse.jpg]

pro:
- 1k dpi
- long battery life (many months)
- good fit in hand
- not too heavy
- good refresh rate (I can draw circles and they are circles)

con:
- still, it's wireless (but I have to :-( )
- righthanded only
- only 1k dpi
- the wheel is too loose - can't wheel click without rolling or swinging to the sides & have to precisely click straight down cause if it catches the wheel click as wheel left/right then it won't work :-P

I have got that one. Xonotic does not seem to recognise all the extra buttons on it.
[Image: 0_e8735_c58a251e_orig]
Reply

(10-31-2013, 11:27 AM)aa Wrote: I have got that one. Xonotic does not seem to recognise all the extra buttons on it.

That's very strange. What OS do you use? If linux, have you tried both sdl and glx? Does your OS recognize the buttons?
[Image:http://i.imgur.com/4XODR.png]640K ought to be enough for anybody.
     ― Linux Torvalds
Reply

Yes, using SDL helped. I am using Linux Slackware 14 64 bit, and it recognizes the buttons...
[Image: 0_e8735_c58a251e_orig]
Reply

Can you use xev to find out what events are associated with the mouse buttons?
Code:
xev -event mouse | grep --no-group-separator -B3 button
then click inside the window that appears.
[Image:http://i.imgur.com/4XODR.png]640K ought to be enough for anybody.
     ― Linux Torvalds
Reply

Code:
ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x3e00002, time 4085989129, (58,53), root:(952,514),
    state 0x0, button 1, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x3e00002, time 4085989233, (58,53), root:(952,514),
    state 0x100, button 1, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x3e00002, time 4085990177, (58,53), root:(952,514),
    state 0x0, button 3, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x3e00002, time 4085990345, (58,53), root:(952,514),
    state 0x400, button 3, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4085993513, (47,73), root:(941,534),
    state 0x0, button 2, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4085993681, (47,73), root:(941,534),
    state 0x200, button 2, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4085998833, (47,73), root:(941,534),
    state 0x0, button 4, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4085998833, (47,73), root:(941,534),
    state 0x800, button 4, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086002265, (47,73), root:(941,534),
    state 0x0, button 5, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086002265, (47,73), root:(941,534),
    state 0x1000, button 5, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086005617, (47,73), root:(941,534),
    state 0x0, button 7, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086005617, (47,73), root:(941,534),
    state 0x0, button 7, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086007945, (47,73), root:(941,534),
    state 0x0, button 6, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086007945, (47,73), root:(941,534),
    state 0x0, button 6, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086014089, (47,73), root:(941,534),
    state 0x0, button 9, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086014209, (47,73), root:(941,534),
    state 0x0, button 9, same_screen YES

ButtonPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086014761, (47,73), root:(941,534),
    state 0x0, button 8, same_screen YES

ButtonRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4086014905, (47,73), root:(941,534),
    state 0x0, button 8, same_screen YES

Order: Left, Right, Middle, Mouse wheel up, down, left, right, page up, down. The "Search button" did not leave any signature, howether it works in the browser, Mozilla Firefox.

Some results from Xonotic SDL:

When first starting the game, whatever I try to bind in the input settings, results in JOY_UP command. Starting game. Constant movement in front left direction, view climbs up and left.

/joy_index 1 - all of the above stops. (switching to joystick which does not exist, thus no input from it.)
or
/joy_enable 0 same as above.

/joy_index 0 - Joystick 0 opened (SDL_Joystick 0 is "A4TECH USB Device" with 37 axes, 57 buttons, 0 balls) -- which is my older mouse, I cant disconnect it, it works together with my keyboard.

Now, If trying to bind keys in prefrences, all works fine. Except the "search" button .
[Image: 0_e8735_c58a251e_orig]
Reply

That's very odd. I haven't experienced problems with extra mouse buttons in the glx build, and your buttons seem pretty standard (except for the search one, and perhaps you can troubleshoot that in xev (without the extra parameters and grep)). What happens if you bind the button in the console?
Code:
bind mouse8 "say I just pressed pagedown on my mouse"

Good thing you figured out that joystick problem! Why does your old mouse present as a joystick and why can't you disconnect it? Is it attached?
[Image:http://i.imgur.com/4XODR.png]640K ought to be enough for anybody.
     ― Linux Torvalds
Reply

My old mouse is a wireless mouse that came in a set with a wireless keyboard, and they both use the same... er... usb slot. Actually, it came up to me I can take the batteries out.

I guess the main problem for the moment is the mouse that i recognized as a joystick.

Also, I know quite a bit about the joystick setup becouse i have tried using a joystick with Xonotic before. ( for the record: it is disconnected all the time i did all the testing)

....

Ok, it seems to work in GLX fine....

Went over to SDL.

First, I tried turning of the mouse- on/off switch on it. No changes, view still moves like crazy. It seems that the problem comes from the fact it works together with a keyboard, there are 37 axis, some of which might be buttons on the keyboard, especial the 0-3 axies used.
Next, I found a separate wired keyboard, and sticked it instead of the A4tech mouse/keyboard combo. No movement or JOY_UPs. After that I put it all back,as it was. The mouse+keyboard are recognized as joystics by Xonotic.

Going over to xev.
Code:
KeyPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4098754005, (29,116), root:(923,577),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XmbLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4098754125, (29,116), root:(923,577),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyPress event, serial 38, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4098756088, (29,116), root:(923,577),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XmbLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

KeyRelease event, serial 38, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4098756181, (29,116), root:(923,577),
    state 0x0, keycode 38 (keysym 0x61, a), same_screen YES,
    XLookupString gives 1 bytes: (61) "a"
    XFilterEvent returns: False

The a letter pressed on the wireless keyboard first, and then on the wired. No difference, as you see.

And here is the search button press result
Code:
KeyPress event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4098906061, (86,93), root:(980,554),
    state 0x0, keycode 225 (keysym 0x1008ff1b, XF86Search), same_screen YES,
    XLookupString gives 0 bytes:
    XmbLookupString gives 0 bytes:
    XFilterEvent returns: False

KeyRelease event, serial 37, synthetic NO, window 0x3e00001,
    root 0x15d, subw 0x0, time 4098906301, (86,93), root:(980,554),
    state 0x0, keycode 225 (keysym 0x1008ff1b, XF86Search), same_screen YES,
    XLookupString gives 0 bytes:
    XFilterEvent returns: False
So it is recognized as a key, not a button.

...

Found a similar case at: http://ubuntuforums.org/showthread.php?t=1567003

Moved the -js0 out of /dev/input/ .
No more problems observed.
[Image: 0_e8735_c58a251e_orig]
Reply

You could write a udev rule to completely disable the joystick, I guess. Or use your joy_* cvar workaround!

That search button is a keyboard event indeed. That's silly. I don't think you can bind XF86Search to a key in Xonotic, but I guess you could use xmodmap to map that key to something that Xonotic understands (there doesn't seem to be a ton of them, not even F13).
[Image:http://i.imgur.com/4XODR.png]640K ought to be enough for anybody.
     ― Linux Torvalds
Reply

In a different game, I managed to bind the Search button, and it was named 00x0 there.
[Image: 0_e8735_c58a251e_orig]
Reply

Yup. But DarkPlaces' input system really sucks, and there's a lot of keys that it simply does not have a name for. You can mostly bind keys that are on a standard US keyboard. That's why cyrillic keyboard layouts and such can't be used.

It would be easy to add support for your search key in a custom darkplaces build, but supporting everything would need a lot of work.
[Image:http://i.imgur.com/4XODR.png]640K ought to be enough for anybody.
     ― Linux Torvalds
Reply

(08-29-2010, 04:48 AM)Fisume Wrote: Am using a Razer Diamondback. Never had any problems with it and it isn't really expensive.

I am also using
Reply

SteelSeries Rival 300 -- Broke in 3 months, the sidebuttons got squishy, the mouse wheel started freespinning, the thumb rubber started to disintegrate.

Razer DeathAdder --  Killed one of these in < 2 months. Have gone through 5+ in my lifetime, they have been getting progressively worse in terms of quality.

Razer Chroma -- dead in 2 months, mousewheel and side button are cheap. overpriced, gimmicky, I don't even care about the LEDs

Logitech G5 -- this is a great mouse for most people. I didn't like the sidebutton feel, personally.  alive because I didn't use it enough, it's a backup.

Zowie Gear EC2-A -- 7 months+ on this currently, no major issues, cheaper than Razer's garbage -- would recommend, was recommended to me by the Xonotic community.
Reply

Yah, I had Razer Copperhead - piece of shit. Sensor is extremely crappy, software is buggy and unusable (I need to plug in another mouse to press the button to update firmware?). Now I have Logitech G500 which I use for about 7 years now. Not the best one but durable.
Reply

Logitech G400s here, I've been using it for 4 years. It's rock-solid.
Stats | Maps: CTF: disarray, vinegar, metro DM: labyrinth Duel: cucumber, quark.
Reply

(07-25-2017, 01:55 PM)-z- Wrote: SteelSeries Rival 300 -- Broke in 3 months, the sidebuttons got squishy, the mouse wheel started freespinning, the thumb rubber started to disintegrate.

Razer DeathAdder --  Killed one of these in < 2 months. Have gone through 5+ in my lifetime, they have been getting progressively worse in terms of quality.

Razer Chroma -- dead in 2 months, mousewheel and side button are cheap. overpriced, gimmicky, I don't even care about the LEDs

Logitech G5 -- this is a great mouse for most people. I didn't like the sidebutton feel, personally.  alive because I didn't use it enough, it's a backup.

Zowie Gear EC2-A -- 7 months+ on this currently, no major issues, cheaper than Razer's garbage -- would recommend, was recommended to me by the Xonotic community.
If it's a habit for your mouses to break within 2-3 months, then maybe you're handling them wrong? LOL
Reply

Logitech MX518. 5+ years and still going strong!
asyyy^ | are you releated to chuck norris?
Reply

Zowie FK 1
I've had it for a couple of months. It's pretty good but I have nothing else to compare it against except a $5 IBM mouse. The scroll wheel sounds kinda fucked sometimes when I scroll fast.
I don't have a big enough mousemat to test it out on yet though so my opinion is useless for now.
[Image: whpqyn.png]
Reply

(07-29-2017, 03:05 AM)Smilecythe Wrote: If it's a habit for your mouses to break within 2-3 months, then maybe you're handling them wrong? LOL
The side buttons, and mouse wheel aren't really that durable, I wish they were. Would be nice to have more accurate mousewheel clicks, and side buttons that can take being held down for long periods of time.
Reply

Chinese knock off gaming mouse with a dragon head on it - lasted 2 years (with two repairs to the usb cable) 
I felt so awesome knowing that I had a dragon on my mouse. 
- Logitech G302 - 6 months and then the side buttons started feeling like trash, so I put it in a box of stuff and never looked at it again.
- Logitech G502 - using now. feels solid, but a bit on the heavier side, so it took some getting used to it.
Has a removable panel underneath for adding / customizing the weight inside.  or for hiding tiny snacks.
[Image: 14402.png]
Reply

Roccat Kova 2016 that I purchased to succeed my old Razer Lachesis (original 2008 model). Cheap, reliable, well put together, has features that are actually useful, and has driver parity between Windows and Linux. Only issue it had was the rubber surround the wheel started to lose it's grip on the actual wheel itself (same thing happens to all the mice I've bought except my Dreamcast one), but that was easily fixed with some super glue.
ECKZBAWKZ HUGE LIST OF ACHIEVEMENTS GOES HERE....


Oh wait.
Reply

Razer deathadder 2013 - Died 1 game before world cup matches
Razer Chroma - Died after World cup matches
SteelSeries Rival 300 Black - slaughtering children better than pennywise the clown
[Image: 38443.png]
Reply

Logitech M500 - have this one for about 2 years, don't remember previous models, but they were also Logitech, died from too much use Big Grin
Reply



Possibly Related Threads...
Thread Author Replies Views Last Post
  Using Mouse Acceleration JoeMaro 4 3,160 02-26-2015, 05:14 AM
Last Post: JoeMaro

Forum Jump:


Users browsing this thread:
1 Guest(s)

Forum software by © MyBB original theme © iAndrew 2016, remixed by -z-