Macro loss configuration

[adan_oliveira]

Hi, I configured "rapid fire" as a macro, I left the "J37" button as "hold" to activate the "R2" button with 5 ms. But when I hold the "J37" Cross Hair disables the macro, then I have to hold the "J37" again and then the macro is activated again. Can you correct that? Thank you.

[richard]

5ms will not be recognisable for consoles.
please try a bigger one, such as 100ms.

and this topic may also help you.
http://www.reasnow.com/forum/index.php?topic=1710.0

if you still can not figure things out, pleas export your macro and post it here in attachment.

[adan_oliveira]

First, thank you for responding. I already followed this tutorial, but I thought 5 ms would be a good value. I will test with 100 ms and post my result, if the problem persists I post my config here. Thank you.

[adan_oliveira]

Here is my config, I have switched between (100ms) (30ms) (15ms) (10ms) (5ms) (8ms) (50ms) and the result is the same, sometimes works, sometimes not. If you want, I can record a video and post it for you to see. Thank you.

[richard]

hi, you need to add a "blank" line to represent the release of your r2 button as showed in the attached pic.

[Team_MFDK]

5ms rapid fire macro works just fine for me on Call of Duty Infinite Warfare .

I've found that values below 4ms stop working mid-game and the designated fire button for my rapid fire macro dies on Infinite Warfare. 

The best thing to do is tweak the mechanics of the CrossHair, do some good ole fashioned plugging & un-plugging, lol

[richard]

thanks for report this, we will look into it, and get back to you later, if we find any bug.

BTW, a 4-ms delay might not be recognized by a console due to the communication limitation.
some games will also neglect these tiny intervals.
so it might cause some trouble.