Tagged: que es lo que es
August 16, 2017 at 3:26 pm #2475
Just asking becaus a lot of people are saying that some players play with mouse macros like bunny hop or spray control.
Well there was nothing in their logfile about a macro or similar.
So i tested it with my rival 700 and still nothing in the logfile. So it seems like Moss cant or just didnt have a feature for detecting macros.
Well its illegal to play with macros so is there a way to add it?
Btw the game it is about is Crossfire.
RegardsAugust 17, 2017 at 10:53 am #2476
could you share the log file ? in version you have the process EXE has to be detected to trigger the macro controlAugust 17, 2017 at 12:48 pm #2477
here is the whole archive. (you have to press the blue download button)August 22, 2017 at 8:06 am #2483
it should but in current version it was bound to game process detection , I will remove that controlAugust 24, 2017 at 7:44 pm #2485
it is enough for me to see a mouse or keyboard .exe opened in log even with no macros used.
all mouse programs and keyboard tasks must be ended before playing.
so will be sure no macros are used.August 24, 2017 at 8:03 pm #2486
The macros are saved in the internal memory of the device so you can execute macros without the driver process.August 24, 2017 at 8:14 pm #2487
Yes, in internal memory of device
So if you disable mouse software in tasj manager, there is no way to use scripts because you disable driver. Try it.August 24, 2017 at 8:24 pm #2488
ye , that the idea , some hardware (corsair for example) doesnt need any driver to macro. that’s the reason why moss just read the final result, whatever sent the information.
final analysis is based on “human” or “unhuman” behaviorAugust 24, 2017 at 8:26 pm #2489
👍August 25, 2017 at 3:31 am #2490
Of course the macro is still working if i close the driver. btw nohope i saw you updated moss and its still nothing in the logfile about a macro. So do you even updated the thing you talked about?
Logfile with moss 126.96.36.199: http://textuploader.com/d6jgkAugust 25, 2017 at 7:38 pm #2495
ye there is still a problem , I drop a new version (tested with a steelseries macro ! )
August 26, 2017 at 4:19 pm #2497
- This reply was modified 3 years, 5 months ago by ADM_nohope.
nice it works now. Ty that you cared about my issue. But i noticed that if you choose crossfire in parameters moss didn’t notice if esl wire is active anymore. Is this wanted?August 27, 2017 at 2:40 pm #2499
yop too much issues on ESL , and no real value added as ESL dont give access to who is logged in, anyway wire is listed in processes.October 11, 2017 at 5:07 am #2545
Hello, how and where can i find detected macro in log?October 11, 2017 at 7:06 am #2546
at the end of log where it’s written “sequence:” and details about the sequence
‘Key1’ medium delay to next key ( standard deviation in this delay)
‘Key2’ medium delay to next key ( standard deviation in this delay)
‘Key3’ medium delay to next key ( standard deviation in this delay)
eventually 2 more keys ifs sequence grew up to 5 keys
at the end the number of times where this sequence get repeated
– time values are Milliseconds
– Standard deviation
Moss notify only sequences , it thinks there is a macro. but Moss is just a program… so if you need my opinion or a confirmation, send me samples
- You must be logged in to reply to this topic.