ARMORED CORE™ VI FIRES OF RUBICON™

ARMORED CORE™ VI FIRES OF RUBICON™

View Stats:
imbrock Sep 21, 2023 @ 8:49am
I fixed mouse hardlock using logitech g-hub
As we all know hardlock breaks if you actually move your mouse, which if you have your dpi even a bit high happens pretty easily. Here is how I fixed this problem:

I have a g502. I opened up ghub and navigated to the armoredcore6.exe (I had to add it manually) page.
I went into the macro section and made a really simple macro, all it does is middle click and rotate the dpi. The default macro delay is 50ms, I went and reduced that to 5ms using the custom delays option. Saved the macro.
Added the macro to my mousewheel click option.
Went to the dpi page. Normally I only use one dpi and don't change it. I created a second dpi at '50', this is as low as it goes. The mouse barely moves at this setting.

Thats it, its done. Now when you activate hardlock your dpi will drop down to 50 and it'll be very difficult to break the hard lock. When it breaks, or you die you'll need to hit middle mouse to switch to your regular dpi. When you manually exit hardlock it should just pop out. Every once in a while I get stuck in the wrong dpi not in hardlock but muscle memory is helping.

I'm not sure if other mouse software has macro settings like this but if you're familiar with your particular software maybe this will help you figure something out.
< >
Showing 1-2 of 2 comments
Call Sign: Raven Sep 21, 2023 @ 8:51am 
Just to make sure I understand what you set up, you made it so middle mouse click sets the DPI to 50ms for when you hardlock, then set it back to 5ms when you click it a second time?
Last edited by Call Sign: Raven; Sep 21, 2023 @ 8:51am
imbrock Sep 21, 2023 @ 8:55am 
Originally posted by Call Sign: Raven:
Just to make sure I understand what you set up, you made it so middle mouse click sets the DPI to 50ms for when you hardlock, then set it back to 5ms when you click it a second time?
It changes back to my default dpi of 1500 when I click it a second time.

The ms readings are the changes I made to the default g-hub macro delays which are usually fifty milliseconds between each input. When firing off a button down (+50ms) dpi switch (+50ms) button up series of commands I've found I would sometimes start clicking my primary mouse buttons before the macro was complete which interrupted it. So I reduced the timings to 5ms each to speed it up which makes that not an issue.

DPI switches between 1500 and 50 for me.
Last edited by imbrock; Sep 21, 2023 @ 8:56am
< >
Showing 1-2 of 2 comments
Per page: 1530 50

Date Posted: Sep 21, 2023 @ 8:49am
Posts: 2