feel of playing R6 with V5.6.107

[scott]

I played for about three hours on v5.6.107 and would like to share my experience.At first I detected the keystrokes as soon as I entered the game, probably because I was using macros. I tried turning off the macro and after two games the alarm disappeared, after turning on the macro again there was no alarm, after playing four games the mousetrap did not work, I will try more modes to detect if the mousetrap will work.

[richard]

Thanks for sharing:)

[nadie852]

I played all day yesterday R6 noticed in a single game a small delay that lasted 1 minute nothing more, there was no detection, I played with macros norecoil rapidfire and others all BEAST mode !!! CONGRATULATIONS Richard, thank you for your work!

[Glorybravesoul]

PS5 exp.

Last 2 days, there were no detections at all. Hopefully nothing changes in future)
Any chance to donate you?

[mxczn]

Richard, could you let us know if this update might arrive on the old crosshair? many people still have it and are expecting this position from you.

[richard]

@Glorybravesoul
thanks for the feedback!
your presence on the forum is all that we need:)

[richard]

@mxczn
the possibility is low, the codes of Cross Hair and S1 are completely different,
and Cross Hair has limited space to contain more codes.

[SimplyHCF]

Just wanted to post a update here myself after playing nonstop for 2 days.

So far, while using 5k DPI and 1K HZ with this new update, I have not yet been touched by Mousetrap in both Rainbow Six Siege and Destiny 2.

Loving the update so far as it obviously bypasses MT, but also the engine just feels more refined and better with this update. Thank you for the hard work guys!

[scott]

I'll continue to share my experience of the two days of the tour.The mousetrap always caught me on the first game at the start of each session, with or without the macro on, and when I stopped the macro and started three games the mousetrap would stop working, even if I turned the macro on afterwards the mousetrap would not work. I suspect that the mousetrap may work when you first enter the game, stop working when it detects that you are not using the keyboard and mouse, and remain inactive after that. I will try to re-enter the game several times over the next few days to prove this conclusion and I will keep you updated on my playthroughs.
@richard
If you need a donation please let us know, don't be shy!

[richard]

@scott
thanks for sharing! please keep us updated with your new findings:)

[nayk]

Thank you everything, works well.

[nadie852]

Latest news, Mr. OBsIV from Xim Apex is furious with Richard because he has the best Firmware that exists at the moment for R6, confirmed Reasnow S1 best product on the market, will Richard be selling a Reasnow S2?

[scott]

I will continue to update my experience over the last two days, firstly I can't verify if my suspicions are correct, as sometimes entering a game with macros on will not be detected, it is more likely to be a matter of probability. But I have found a way to avoid detection in the first game, first you can turn off all macros, enter the game, do everything with the joystick and then turn on the macros when you have control of your cadre at the end of the game's scouting time, after which the mousetrap will not work, even if you turn on the next game.
@richard
xim has run out of good solutions to deal with this and they are more likely to use the development of new firmware. Congratulations on your victory and we thank you for your work day and night. If you need a donation to develop new firmware please let us know, don't be shy!

[Ecko]

Good afternoon! I played with the new firmware as soon as it came out, set it to 250 hz and always turned on macros during the match, and today I immediately fell into a trap in the first match. Does everyone get it or am I just unlucky?

[richard]

@nadie852 thanks!
and currently there is no plan for a S2.

[richard]

@scott thanks for sharing! we will note and assess your feedback carefully.

[richard]

@Ecko try some more matches with a controller until everything is back to normal,
then try our S1 with 5.6.107 firmware with no macros.
please send your findings to support@reasnow.com
we would love to help with all our resources.

[scott]

I'll continue to update my two days of play and as others have said, Ubisoft seems to have updated their mousetrap since May 1 and I can't avoid getting caught in it. I also went to other forums looking for answers and xim apex released SAB 2.0, however their solution was to use some specific keyboards and mice to simulate a joystick, which did allow some players to avoid the mousetrap, but many players were venting about the poor dpi.
@richard
Could we try to simulate the xim apex and convert the signal into a joystick signal with some clever little device?

[indicud]

Could we try to simulate the xim apex and convert the signal into a joystick signal with some clever little device?

It feels more logical to add randomization in all features, randomized ramp up time on left joystick and triggers, randomized anti recoil patterns that change ever so slightly from the original in an effort to evade detection, randomized timing on all inputs but keep them under say 20 ms (or whatever is logical and possible) randomized timing on macros in general such as "100 ms" I feel as if they(ubisoft) can read that "x" button was held for "y" "z" many times in a row.

Let me know if this makes sense, hopefully richard and devs will get to see this message. No rush take your time and bring us a surefire mousetrap work around and goodluck.

[cerep_rus]

Have same issues with mousetrap.  Played one game and after started delay on movement. And end of the match get penalty for using mnk.