None of the above advices did even affect the ingame mouseperformance, while it was quite a piece of work to use the mouse under windows gui... naturally.
Maybe You want to see a vid showing what I mean?
The pointer is not moving it is jumping from point A to point B instead.
And yes the "wait" timer is going on my nerves too cause it doesnt even affect anything related to the macro performance on my machine!
I already coded some subs for testing purposes under AutoHotKey gui, e.g. moving "cargo" and "items" closing menus etc., and actually they work as fast as those of Macro Sheduler, while using smooth mousemovement using lesser resources. This has nothing to do with the mouse or driver you use its just the calculated time the mousepointer is moving a specific pixel distance. Like mph for e.g. has nothing to do with the car You drive its the same constant for every car.
There is one question: Are You actually able to "see" youre mousepointer moving from A to B?
Not jumping as fast as hell. Moving. That wont turn down the speed of the macro never ever cause you dont even need those "wait at a point without moving" commands anymore. Anyway... it would be harder to detect the macro cause the speed of interface usage would be more natural.
If I would get my f*ck*ng RAT_detection to work I could use my own macro. And post it to show You.
.
..
...
Oh and before I forget:
"Error - Label OVERVIEW_SETTINGS_RESIZE_LOGON_RECHECK Not Found!
:edit:
Made a small screen cap vid specialy for you
its around 3 mb.
Get it here
http://s5.11mbit.de/JmaBl1O79AGragGMxPd ... 5/pbc967hI
I have the speed usually at doubletime the speed in this video.
Made it slower cause the capture soft seems to have the same problems the macro software has... so just imagine without the flickering.
Of course its totally smooth in reality, as I said its the capture software.
Hope You now get what I ment...
Who is online