

G700S Mouse And Mwo
#1
Posted 23 March 2016 - 01:39 PM
Decided to upgrade....this mouse isn't recognizing the side buttons which were mapped to groups 4 & 5 on my old mouse...
Figured the 'tilt' function on the wheel would let me mess around with more functions or groups. The side buttons and wheel tilt aren't recognized in-game, nor am I able to map them via the Logitech software for functions. Anyone out there using this that's had it work in-game?
Thanks!
~War~
#2
Posted 23 March 2016 - 02:06 PM
#3
Posted 23 March 2016 - 03:27 PM
Edited by Ano, 23 March 2016 - 03:34 PM.
#4
Posted 23 March 2016 - 03:43 PM
As long as you did not change anything in game nor the Logitech software, it should work as noted. Group 3 is the top rear button (BACK) and group 4 is the top front button (FORWARD).
I use this mouse when I am away from the computer but I found it easier to set the bottom rear button as the FORWARD key for WGroup 4.
http://mwomercs.com/...-mouse-buttons/

Other option is to set those buttons to GENERIC
http://mwomercs.com/...not-being-seen/
PS I will say this kindly, PGI, please fix your forum search engine to provide allow to sort by dates/etc. My results should not start with posts from 2012/2013 (which did not have the info I NEEDED). We should not have to resort to Google to get better functionality.
Hmm.. okay, edited out all the stuff that would get me moderated and possibly banned.
Thank you...

Edited by Tarl Cabot, 23 March 2016 - 03:45 PM.
#5
Posted 23 March 2016 - 04:38 PM
#6
Posted 23 March 2016 - 05:55 PM
#7
Posted 23 March 2016 - 06:45 PM
*edit* i'll try running the battery down and trying from scratch....all profiles deleted.
Edited by Warspawn, 23 March 2016 - 06:50 PM.
#8
Posted 23 March 2016 - 06:50 PM
Good luck.
Edited by SkavenDC, 23 March 2016 - 06:50 PM.
#9
Posted 23 March 2016 - 08:09 PM
SkavenDC, on 23 March 2016 - 06:50 PM, said:
Good luck.
That's the one I have. Haven't noticed a problem, but then I don't use those buttons. Worked fine on the previous rig, which was a Win7/64 partition on a 2011 21.5" iMac. The new (-er) rig is on Win10, and I haven't bothered looking at those functions. I'll have to check and see if I'm also having this trouble, for what it's worth.
#10
Posted 25 March 2016 - 11:10 AM
My logitech software is setup to use automatic game detection instead of using the onboard configs. How are you setting up your mouse?
#11
Posted 25 March 2016 - 04:58 PM
#12
Posted 25 March 2016 - 06:41 PM
remapping is simple
just remap all your mouse keys to actual number or letter keys on the keyboard . don't use the back forward etc funktions , no game supports those . as they are windows short keys and not say mechwarrior online short cuts, and than go into the game and remap all the functions you want to those keys
i just use the numeric part of the keyboard
i got push to talk on there . heat vision , night vision , map, score board,zoom 1 and 2 and 3
i would also advise you to stay with the thumb keys and the middle mouse button the tilt keys are actually kinda fragile and break easily after a lot of use ( this is my 3rd G700 in the passed 3 years . the 2nd G700S previous was the old skool g700) and all of them broke because of micro switch key failure.
but!! still lasts longer than a deathadder..razor really makes cheap china junk =P
GL
Edited by Catnium, 25 March 2016 - 06:46 PM.
#13
Posted 25 March 2016 - 09:58 PM
Quote
False. At least with MWO and Crysis 3
MWO use back/forward default settings on the mouse itself for group 3/4. I use the G500 and G602. In MWO settings it is the alternate/mouse settings, which is noted as Mouse buttons 4 and 5. Just tested it on a Microsoft Intellimouse too. And changed the BACK browser button to other buttons, each button would then fire weapon group 3.
You CAN remap the using the software to press the actual numbers on the keyboard. If you do that then make sure to set it as a different profile so you do not lose the default mouse settings when not playing.
Others may have difficulty with settings cause they may have changed the default mouse settings for use in other games instead of making an actual profile for that game. But by default, when pressing Mouse 4 key, which is set to recognize default window setting BACK browser command, fires weapon group 3, unless the player had previously made changes to it.
As for weapon groups 5 and 6, those two have to be set to actual keystrokes.
So, default settings
Mouse Left button = WGroup 1
Mouse Right button = WGroup 2
Mouse button 4 (BACK browser mouse command)= WGroup 3
Mouse button 5 (FORWARD browser mouse command) = WGroup 4
Edited Also tested it in Crysis 3. Nothing was set to Mouse button 4 (BACK Browser) by default. Selected and set a command to Mouse 4 and it was accepted. Set a different mouse button in Logitech software to BACK browser command and that button would execute the command tied in game to Mouse button 4, even though it was a different physical mouse button.
Edited by Tarl Cabot, 25 March 2016 - 10:37 PM.
#14
Posted 26 March 2016 - 01:00 AM
Warspawn, on 25 March 2016 - 04:58 PM, said:
You will need to use the logitech software and set it to use automatic game detection and create a game profile for the mouse. With this you can point a profile to a specific exe (in this case MWOClient.exe) so it will autolaunch the profile when the game starts.
MWO natively recognizes the bottom two thumb buttons (G5 and G4) but you will need the software to assign the upper two thumb buttons. I'm not sure if MWO can natively recognize the tilt, I configured mine using the software.
#15
Posted 26 March 2016 - 04:56 AM
*edit*....odd. My old mouse, MX518 sees those side buttons fine and I'm able to map them to groups 4 & 5 with no worries via 'setup' in the client. Grr...
Edited by Warspawn, 26 March 2016 - 05:01 AM.
#16
Posted 26 March 2016 - 05:17 AM
#17
Posted 26 March 2016 - 06:32 AM
Perhaps its an issue with MWO not buffering keys but you need to make sure you Add a delay between down and up events well above the delay that exists between two display frames.
At a constant 60 fps that would be 16.6ms but in theory it requires both down and up registration which is at least 33ms~ And then add a bit more for margin or low fps.
My strike/coolshot used to go off half of the time on my G502 / G303 due to this phenomenon
Id stick with Mouse4/5 whenever possible.
Edited by M T, 26 March 2016 - 06:34 AM.
#18
Posted 27 March 2016 - 10:04 AM
M T, on 26 March 2016 - 06:32 AM, said:
Perhaps its an issue with MWO not buffering keys but you need to make sure you Add a delay between down and up events well above the delay that exists between two display frames.
At a constant 60 fps that would be 16.6ms but in theory it requires both down and up registration which is at least 33ms~ And then add a bit more for margin or low fps.
My strike/coolshot used to go off half of the time on my G502 / G303 due to this phenomenon
Id stick with Mouse4/5 whenever possible.
Interesting. I haven't experienced this yet and I use some commands regularly via logitech software mapping (namely the vision modes on the tilt wheel and firing groups on the upper thumb buttons). The only time buttons stopped registering consistently was when the microswitches got worn out. It happened to my g5 and previous g700 after years of use.
#19
Posted 27 March 2016 - 12:33 PM
And the standard delay for keystrokes should work fine with 50 ms setting. Thrustmaster Warthog also uses that delay and no issues.
Ok the help file mentions setting the delay but I cannot find the exact reference under recording a single keystroke. Sorry. Will double check
I can only say with Heinreich that it should work. Le sigh. At the very least try running as administrator.
How: RightClick link on Desktop. Go to Compatibility mode. Click always run as administrator.
Edited by Hammerhai, 27 March 2016 - 12:50 PM.
#20
Posted 27 March 2016 - 12:54 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users