Im not above running macros , I just don't see the need for one in this case , the gauss isn't hard to use now .... Btw if you want a macro that works for the gauss run one with some pixel detection on the ******* reticule indicator . PGI literaly couldn't make it easier to macro if they tried , red marker on cooldown , green marker ready to fire ... a small amount of knowlage on the firing time of gauss and ppcs and your golden to sync your ppc/ gauss every shot .


Can't You Just Macro The Gauss?
Started by Cycleboy, Sep 03 2013 12:27 PM
45 replies to this topic
#41
Posted 08 September 2013 - 03:28 AM
#42
Posted 08 September 2013 - 10:00 PM
Fun fact... trail time needed for Gauss vs. PPC should be 1/6000th of a second for every 1m of range (if I can trust my math)
Should be easy to set some kind of +/- zeroing scale to ensure both shots hit at the exact same time. Bonus points if you tie it into an overlay instead of just keeping the current value up on a second monitor.
Macro boys... go nuts.
P.S. Can you tell I'm still sore with PGI over ghost heat?
Should be easy to set some kind of +/- zeroing scale to ensure both shots hit at the exact same time. Bonus points if you tie it into an overlay instead of just keeping the current value up on a second monitor.
Macro boys... go nuts.
P.S. Can you tell I'm still sore with PGI over ghost heat?
#43
Posted 11 September 2013 - 08:32 AM
Macros.....ban them.
Show me some decent pilot skill please. Macros make you lazy, they're the sort of thing 12 year old kiddies use in CoD before they start screaming obscenities at you over comms.
Automating anything in a game is basically cheating, go cheat elsewhere....
/b.itchslap macro users/
Show me some decent pilot skill please. Macros make you lazy, they're the sort of thing 12 year old kiddies use in CoD before they start screaming obscenities at you over comms.
Automating anything in a game is basically cheating, go cheat elsewhere....
/b.itchslap macro users/
Edited by GlycerineOxide, 11 September 2013 - 08:33 AM.
#44
Posted 12 September 2013 - 03:59 PM
(Well, here's a good o' fashion macro. It works pretty well and as autohotkey is allowed it's not cheating. All you need to do is put your gauss (one or two) on group 5 and your ppcs on group 6. This will automatically fire your alpha .10 seconds after the gauss has been changed. The sleep function will allow you to just hold the key and it will alpha as soon as the gauss is charged and ready. Works great for those out in the open. It works well. Enjoy!
#InstallKeybdHook
#InstallMouseHook
$CapsLock::
while GetKeyState("CapsLock","P") ; While Left Shift is being held down physically do.
{
send {5 down}
sleep 850
send {6 down}
sleep 100
send {5 up}
send {6 up}
sleep 4000
}
return
; .183 seconds between each push
; 1000 = 1 second
#InstallKeybdHook
#InstallMouseHook
$CapsLock::
while GetKeyState("CapsLock","P") ; While Left Shift is being held down physically do.
{
send {5 down}
sleep 850
send {6 down}
sleep 100
send {5 up}
send {6 up}
sleep 4000
}
return
; .183 seconds between each push
; 1000 = 1 second
Edited by SolCrusher, 12 September 2013 - 04:01 PM.
#45
Posted 15 September 2013 - 10:01 PM
SolCrusher, on 12 September 2013 - 03:59 PM, said:
(Well, here's a good o' fashion macro. It works pretty well and as autohotkey is allowed it's not cheating. All you need to do is put your gauss (one or two) on group 5 and your ppcs on group 6. This will automatically fire your alpha .10 seconds after the gauss has been changed. The sleep function will allow you to just hold the key and it will alpha as soon as the gauss is charged and ready. Works great for those out in the open. It works well. Enjoy!
#InstallKeybdHook
#InstallMouseHook
$CapsLock::
while GetKeyState("CapsLock","P") ; While Left Shift is being held down physically do.
{
send {5 down}
sleep 850
send {6 down}
sleep 100
send {5 up}
send {6 up}
sleep 4000
}
return
; .183 seconds between each push
; 1000 = 1 second
#InstallKeybdHook
#InstallMouseHook
$CapsLock::
while GetKeyState("CapsLock","P") ; While Left Shift is being held down physically do.
{
send {5 down}
sleep 850
send {6 down}
sleep 100
send {5 up}
send {6 up}
sleep 4000
}
return
; .183 seconds between each push
; 1000 = 1 second
#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. #Warn ; Recommended for catching common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. #singleinstance Force ;Set gauss to right mouse group, ppc to group 6 (6 key). hold right mouse to charge. ;firing window marked with beeps. release right mouse to fire. PPC will only fire in the gauss firing window. ;Additional beep indicates recycle complete. Rbutton:: settimer, gCharge, 750 Charging := 1 return Rbutton up:: settimer, gCharge, off settimer, gWindow, off if ((Charging == 0) and (charged == 1)) { settimer, recycle, 4000 send, {6 down} sleep, 25 send {6 up} } charged := 0 charging := 0 return GCharge: settimer, gCharge, off settimer gWindow, 1250 charged := 1 Charging := 0 soundbeep , 1000, 50 return gWindow: settimer gWindow, off charged := 0 soundbeep , 1000, 50 soundbeep , 500, 150 return recycle: settimer, recycle, off soundbeep, 2000, 100 return
#46
Posted 17 September 2013 - 02:03 AM
People who use macros are exactly like people who use "performance enhancers", except they dont get laid as often...
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users