Treadpool Posted July 29, 2017 Share Posted July 29, 2017 I have a simple macro set to the G4 button on my Scimitar that presses and releases the left mouse button. I have it press, then 30ms pause, release, then 30ms pause. With advanced settings enabled, I have it at this: Action Trigger - While Pressed Action Repeat - Constantly Delay 30ms It seems to keep running the script even when I lift off the G4 button. Guns keep firing and screen selections start going bonkers. Is there a way to have it check if the button is still pressed and end the macro if it isn't? As a side note, I've tried rolling back to previous versions and it hasn't made a difference. Currently on 2.15.83.tctd.cueprofile Link to comment Share on other sites More sharing options...
SumAussieCobber Posted July 30, 2017 Share Posted July 30, 2017 Mate i have the same issue none of my macro's working with this new update and i have tried rolling back to 1.16 CUE and still nothing Link to comment Share on other sites More sharing options...
Comet 1626864951 Posted July 30, 2017 Share Posted July 30, 2017 I have a simple macro set to the G4 button on my Scimitar that presses and releases the left mouse button. I have it press, then 30ms pause, release, then 30ms pause. With advanced settings enabled, I have it at this: Action Trigger - While Pressed Action Repeat - Constantly Delay 30ms It seems to keep running the script even when I lift off the G4 button. Guns keep firing and screen selections start going bonkers. Is there a way to have it check if the button is still pressed and end the macro if it isn't? As a side note, I've tried rolling back to previous versions and it hasn't made a difference. Currently on 2.15.83. Instead of using separate macro actions to press and release the left mouse button, insert a single macro action to click the left mouse button. This is more efficient, and you will not risk having the macro interrupted between the mouse down and mouse up events--having a mouse (or key) down without lifting it can cause autorepeat to make your computer think the button (or key) is stuck mashed down. Link to comment Share on other sites More sharing options...
Treadpool Posted July 30, 2017 Author Share Posted July 30, 2017 Thank you that seemed to work well! Link to comment Share on other sites More sharing options...
Treadpool Posted July 30, 2017 Author Share Posted July 30, 2017 I lied - still ends up clicking everywhere in the game and out. Any idea what this is? I'll use the macro then try to type something and it won't let me bc the click macro is firing still. Link to comment Share on other sites More sharing options...
Comet 1626864951 Posted August 2, 2017 Share Posted August 2, 2017 2 ms delay is a bit short; I usually specify a random delay between 167 and 200 ms; you don't want to overrun your system buffers, and using random delay keeps some game engines from blocking your actions as a constant 2 ms delay will look like a bot. (To determine a good delay, I recommend that you time yourself doing a series of repetitive mouse clicks, and use your own timing; anything faster than you can do is a crutch that may bite you later.) Link to comment Share on other sites More sharing options...
Treadpool Posted August 3, 2017 Author Share Posted August 3, 2017 2 ms delay is a bit short; I usually specify a random delay between 167 and 200 ms; you don't want to overrun your system buffers' date=' and using random delay keeps some game engines from blocking your actions as a constant 2 ms delay will look like a bot. (To determine a good delay, I recommend that you time yourself doing a series of repetitive mouse clicks, and use your own timing; anything faster than you can do is a crutch that may bite you later.)[/quote'] Completely agree about the delay. When I record the macro and click on my own it's around 80-90ms. I've tried 100ms before and it's very very slow in-game. Much slower than when I click on my own, so not sure why that is. Link to comment Share on other sites More sharing options...
Comet 1626864951 Posted August 3, 2017 Share Posted August 3, 2017 Try, then random time between 50-90 ms, and see if this gives acceptable in-game performance. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.