35 replies to this topic

[Wintersdark]

Koniving, on 03 June 2013 - 07:54 AM, said:

I don't know. Mine runs extremely well with changes made inside a match. If you find me powered down in a match but I haven't fired a shot, the reason why is I'm fixing my macro as I change it every time I change a mech.

You could set a key to toggle macro modes.

Do it like Mr. Friday said above, with the CHATTING variable. Use, say, function keys to set an ACMODE variable, then if ACMODE=1 or ACMODE=2 etc to choose which bit of script to execute when your key is pressed.

Something like this:

Spoiler

#SingleInstance Force
#InstallMouseHook
#InstallKeyBDHook
 
; Clear it at start
ACMODE = 0
 
; F1 selects lbx/mg/ac2 mode, F2 selects AC5/AC2 mode, F4 turns off the macros.
 
F1::
   ACMODE = 1
   return
 
F2::
   ACMODE = 2
   return
 
F4::
   ACMODE = 0
   return
 
LCtrl::
; LBX/MG/AC2 Jager Mode
   if (ACMODE = 1) {
	  while GetKeyState("LCtrl","P") {
		 send {3 down}
		 sleep 85
		 send {3 up}
		 send {4 down}
		 sleep 85
		 send {4 up}
		 send {5 down}
		 sleep 85
		 send {5 up}
	  }
   }
   ; Mode 2 = AC/5 AC/2 mode
   else if (ACMODE = 2) {
	  while GetKeyState("LCtrl","P") {
		 send {3 down}
		 sleep 100
		 send {3 up}
		 send {4 down}
		 sleep 100
		 send {4 up}
		 send {5 down}
		 sleep 100
		 send {5 up}
		 send {6 down}
		 sleep 100
		 send {6 up}
         }
      }
   ; send basic left control if no modes selected
   else {
	  send {LCtrl}
   }
   return

Sadly, the forum ate my indentations when I copied and pasted from Notepad++, so they could be sketchy here.

Also, just a heads up unrelated to the above but correcting something erroneous I said earlier - the P the GetKeyState is telling AHK to check the physical state of the key, as opposed to the logical state which in some cases may differ. The other option here is to check T, for toggle, so you can tell if, say, Capslock is on or off instead of whether or not the Capslock key is held down or not.

Edited by Wintersdark, 03 June 2013 - 10:45 AM.

[Wintersdark]

For even more awesomeness, if you know someone who sounds even vaguely like Betty, read this:

http://www.autohotke...s/SoundPlay.htm

You could have the mode select hotkeys (f1, f2, etc) play a wav file of Betty announcing which AC mode you've selected... Maybe change it from a key per mode to using the mouse wheel to select modes... *ponders*

[Mr Friday]

DireBloodWolf, on 02 June 2013 - 05:02 PM, said:

I'm trying to get autohotkey to work for mapping the scroll wheel, and it is just not working. can someone tell me what i'm doing wrong:

Spoiler

SendMode Input
 
#InstallMouseHook
#InstallKeyBDHook
 
 
WheelUp::
		Send {z }
 
return
 
WheelRight::
		Send {5 }
 
return
 
WheelLeft::
		Send {6 }
 
return

It works in notepad but not in MWO.

Got to say, I haven't tried mapping things to mouse buttons thats much, so it could just be that CryEngine doesn't like it that much... Also you could try adding delays to the keys to ensure that CryEngine catches them, the script might be releasing the keys before the game can register them as pressed at all. Something like this:

send {z down}
sleep 60
send {z up}

or with SetKeyDelay perhaps.

Also I know its possible to bind the mouse without a 3rd party program like AHK in the middle. It would require you to be able to rebind the left and right mouse wheel buttons to Mouse 4 / 5 or even the keys themselves. That would allow the left and right to detected by MWO easily.

As for mouse wheel up / down you have to get a bit naughty and edit the actionmaps.xml. A bad thing to do 'cause they don't like us editing xml files anymore. A good thing to do 'cause MWO doesn't play nice with the mouse wheel any other way. Just add these lines into the actionmaps file:

<action name="m_toggle_zoom_mode">   <rebind device="keyboard" input="mwheel_up" index="1" defaultInput="mouse3"/>   </action>
<action name="m_toggle_4x_zoom_mode">   <rebind device="keyboard" input="mwheel_down" index="1" defaultInput=""/>   </action>

Wintersdark, on 02 June 2013 - 05:05 PM, said:

Hawt. Probably the title match mode there that fixes it. I'd originally used Mechwarrior Online with the window title, but it was very inconsistent - would work sometimes, and not others, so I just went to window class (as I'm not playing other CryEngine games) which has worked quite a bit better for me.

Why detecthiddenwindows?

Also, having T or Y toggle a chat variable is pretty clever, I hadn't even considered it. Would remove the necessity to tap backspace very quickly to toggle chainfire without double-toggling it

I tend to include detecthiddenwindows in most scripts where I need to check or manipulate windows. Had loads of problems with a program that wouldn't work without it before so I just include it in most scripts now.

[Wintersdark]

I've been playing with the mode select above, but using F1 through F3 to select timing on my -DD's 5 AC/2's - 100, 125 and 150ms delays between each of the 5 AC/2's, to get awesome dakkadakka with more controllable heat buildup. At 150ms, you're outputting less DPS of course, but you can sustain it for a good long time. Excellent for suppressive fire. It's surprising what a slight additional delay can do for heat buildup.

Also, you can use CTRL for the 150ms recycle, and always have the option of just holding down Left Mouse (if you've got all the AC/2's in a single group for it) to switch to max-dps fire too.

Edited by Wintersdark, 03 June 2013 - 11:35 AM.

[Koniving]

Wintersdark, on 03 June 2013 - 08:39 AM, said:

For even more awesomeness, if you know someone who sounds even vaguely like Betty, read this:

http://www.autohotke...s/SoundPlay.htm

You could have the mode select hotkeys (f1, f2, etc) play a wav file of Betty announcing which AC mode you've selected... Maybe change it from a key per mode to using the mouse wheel to select modes... *ponders*

Actually I have someone working on replacing Betty's voice, but in the meantime will swap Betty's voice with MW3's computer soon for a change in pace.
Example:

[WVAnonymous]

zraven7, on 03 June 2013 - 08:00 AM, said:

Dude, Kon is one of the most helpful members of the community here. He's really not a troll.

Although he may live in the northern Lower Peninsula of Michigan, which is where the trolls live.

But he's a good guy, nonetheless.

[Koniving]

I think Jazz was referring to Dark at first, who said he knew how to make chat macros but initially gave nothing on how to allocate the macro to a button.

Also, I actually live in Florida. Where's too humid even when its cool.

[DireBloodWolf]

Wintersdark, on 03 June 2013 - 07:26 AM, said:

Yeah, even without those lines, AHK is very inconsistent for me in MWO. Works fine in everything else, but in MWO... It's unreliable. Quite frustrating, really - I suspect Windows 8 has a role in my troubles (because it often does) but I've been unable to reliably reproduce the problems. It *always* works in everything else, and just sometimes works in MWO... but it seems almost random. Frustrating.

I'm running Windows 7 and I'm running AHK in admin mode... it still won't work after starting fresh... what the heck?

[DireBloodWolf]

Mr Friday, on 03 June 2013 - 10:55 AM, said:

Got to say, I haven't tried mapping things to mouse buttons thats much, so it could just be that CryEngine doesn't like it that much... Also you could try adding delays to the keys to ensure that CryEngine catches them, the script might be releasing the keys before the game can register them as pressed at all. Something like this:

send {z down}
sleep 60
send {z up}

Just saw this. That fixed it. Thanks!

[Wintersdark]

My current Jag Autocannon Fire Select and general MWO utility script:

Spoiler

; Prevent access to environment
#NoEnv
 
; Prevent multiple instances
#SingleInstance Force
 
; Window name matching to 'contains'
SetTitleMatchMode, 2
 
; Detect Hidden Windows
DetectHiddenWindows, On
 
; Install the mouse hook to circumvent CryEngine
#InstallMouseHook
 
; Install the keyboard hook to circumvent CryEngine
#InstallKeybdHook
 
; The virtual keypress delays
SetKeyDelay, 0, 0
 
; Whether we are chatting (1 = yes, 0 = no)
CHATTING = 0
 
; Force all following hotkeys to only activate in MWO
#IfWinActive MechWarrior Online
 
; All chat toggle
~T::
        CHATTING = 1
        return
 
; Team chat toggle
~Y::
        CHATTING = 1
        return
 
; Lance chat toggle
~U::
        CHATTING = 1
        return
 
; Send chat toggle
~Enter::
        CHATTING = 0
        return
 
; Cancel chat toggle
~Esc::
        CHATTING = 0
        return
 
; The Quick Fire Backspace hack
$Backspace::
        ; Prevent quick fire from happening outside of chat
        If (CHATTING = 1) {
                ; Send initial backspace
                Send {Backspace}
                
                ; Wait and check if key is pressed
                Sleep, 200
                if (GetKeyState("Backspace", "P") = 0) {
                        return
                }
                
                ; Keep sending backspace presses until key is released
                Loop {
                        Send {Backspace}
                        Sleep, 60
                        if (GetKeyState("Backspace", "P") = 0) {
                                break
                        }
                }
        }
        ; If not chatting send only 1 backspace
        else {
                Send {Backspace}
        }
        return
        
 
; Clear it at start
ACMODE = 0
 
; F1 selects 5ac2 mode, F2 selects reduced head AC2 mode, F3 selects 2AC2/2AC5 mode, F4 turns off the macros.
 
~F1::
    ACMODE = 1
    return
 
~F2::
    ACMODE = 2 
    return
    
~F3::
    ACMODE = 3
    return
 
~F4::
    ACMODE = 0 
    return
 
~LCtrl::
    ; 5xAC2 Jager Mode
    if (ACMODE = 1) {
        while GetKeyState("LCtrl","P") {
            send {2 down}
            sleep 100
            send {2 up}
            send {3 down}
            sleep 100
            send {3 up}
            send {4 down}
            sleep 100
            send {4 up}
            send {5 down}
            sleep 100
            send {5 up}
            send {6 down}
            sleep 100
            send {6 up}
        }
    }
    ; Mode 2 = reduced heat AC/2 mode
    else if (ACMODE = 2) {
        while GetKeyState("LCtrl","P") {
            send {2 down}
            sleep 150
            send {2 up}
            send {3 down}
            sleep 150
            send {3 up}
            send {4 down}
            sleep 150
            send {4 up}
            send {5 down}
            sleep 150
            send {5 up}
            send {6 down}
            sleep 150
            send {6 up}         
        }
    }
    ; Mode 3 = 2 AC2 2 AC5 staggerfire mode
    else if (ACMODE = 3) {
        while GetKeyState("LCtrl","P") {
            send {3 down} ; fire AC5 #1
            sleep 250
            send {3 up}
            send {5 down} ; fire AC2 #1
            sleep 250
            send {5 up}
            send {6 down} ; fire AC2 #2
            sleep 250
            send {6 up}
            send {4 down} ; fire AC5 #2
            sleep 250
            send {4 up}
            send {5 down} ; fire AC2 #1
            sleep 250
            send {5 up}
            send {6 down} ; fire AC2 #2
            sleep 250
            send {6 up}
        }
    }
    ; send basic left control if no modes selected
    else {
        send {LCtrl}
    }
    return
 

Fire modes 1 and 2 staggerfire my AC/2's when I'm rocking my 5AC2 Jag, at high DPS/high heat and moderate DPS/moderate heat timings. I've found firing them somewhat slower is fantastic for times when I'm firing at long range, and am aiming more for suppression than outright damage.

Fire mode 3 is for my 2AC5/2AC2 mode. It causes a cannon to fire every quarter-second, maximizing the AC5 output but skipping a couple potential shots with the 2's. I group fire the lot of them for high DPS/single strike damage, but chain fired like this they output steady, even dakka and will take *forever* to overheat, even with only the in-engine 10 DHS.

I've stolen Mr. Friday's context sensitive quickfire backspace implementation as well, so I can finally backspace properly in chat, too.

It's working marvelously.


Oh, and I found the source of my woes. See, what I was doing previously is closing AHK and relaunching it when I changed my script. This lead to really inconsistent behaviour with the mouse/keyboard hooking and cryengine - now, just having the existing AHK instance reload the script when I change it has stopped the problem entirely.

PEBKAC, as always.

Edited by Wintersdark, 04 June 2013 - 09:52 AM.

[Mr Friday]

Winter, you could make your ACMODE macro thingy simpler by doing this:

Spoiler

; Clear it at start
ACMODE = 0
 
; F1 selects 5ac2 mode, F2 selects reduced head AC2 mode, F3 selects 2AC2/2AC5 mode, F4 turns off the macros.
 
~F1::
    ACMODE = 100
    return
 
~F2::
    ACMODE = 150
    return
    
~F3::
    ACMODE = 250
    return
 
~F4::
    ACMODE = 0 
    return
 
~LCtrl::
    if (ACMODE > 0) {
        while GetKeyState("LCtrl","P") {
            send {2 down}
            sleep %ACMODE%
            send {2 up}
            send {3 down}
            sleep %ACMODE%
            send {3 up}
            send {4 down}
            sleep %ACMODE%
            send {4 up}
            send {5 down}
            sleep %ACMODE%
            send {5 up}
            send {6 down}
            sleep %ACMODE%
            send {6 up}
        }
    }
    ; send basic left control if no modes selected
    else {
        send {LCtrl}
    }
    return

[Gyric]

hmm well, i want to know how i can send text messages on purpose

such things as "HF, GL & Bacon!", perhaps predefined team/lance commands and so on...
i read this thread and tried several things, but nothing has worked

[Mr Friday]

I ended up using this to chat in MWO:

; Install the keyboard hook to circumvent CryEngine
#InstallKeybdHook

; The virtual keypress delays
SetKeyDelay, 0, 0
 
; Set the message to be sent
Message = HF, GL & Bacon!
 
; Send the message
Send {RAW}%Message%

Those should allow you to send key presses to the chat box.

If you don't mind not creating your own I made one that easy to edit as all you needed to do was add variables according to its naming convention, like so:

Spoiler

; G menu
; The global quick chat menu
VGS_G_Menu = 1
VGS_G_Global = 1

VGS_G_A = Awesome
VGS_G_B = Good Bye
VGS_G_D = I Don't Know
VGS_G_F = GLHF
VGS_G_G = Good Game
VGS_G_H = Hello
VGS_G_L = LOL
VGS_G_N = Neg
VGS_G_O = Oops
VGS_G_Q = Quiet on Comms
VGS_G_S = Sorry
VGS_G_T = Thanks
VGS_G_V = Help
VGS_G_W = You're Welcome
VGS_G_X = I'm Dead
VGS_G_Y = Aff

So the key combination "VGF" (V to start the VGS, G for the menu, F for the sub option) would send "GLHF" to All chat. If your interested in this just say and I'll post up a link.

[Wintersdark]

Mr Friday, on 04 June 2013 - 12:22 PM, said:

Winter, you could make your ACMODE macro thingy simpler by doing this:

Spoiler

; Clear it at start
ACMODE = 0
 
; F1 selects 5ac2 mode, F2 selects reduced head AC2 mode, F3 selects 2AC2/2AC5 mode, F4 turns off the macros.
 
~F1::
	ACMODE = 100
	return
 
~F2::
	ACMODE = 150
	return
	
~F3::
	ACMODE = 250
	return
 
~F4::
	ACMODE = 0
	return
 
~LCtrl::
	if (ACMODE > 0) {
		while GetKeyState("LCtrl","P") {
			send {2 down}
			sleep %ACMODE%
			send {2 up}
			send {3 down}
			sleep %ACMODE%
			send {3 up}
			send {4 down}
			sleep %ACMODE%
			send {4 up}
			send {5 down}
			sleep %ACMODE%
			send {5 up}
			send {6 down}
			sleep %ACMODE%
			send {6 up}
		}
	}
	; send basic left control if no modes selected
	else {
		send {LCtrl}
	}
	return

Not really, because the various mode options change all the time with my builds. I use about 15 mechs primarily, and even then I change their builds frequently. I don't just use them for timings - some are for entirely different weapon sets such as chain firing a pair or trio of UAC5's without jamming, etc. I started out with a variety of 5AC2 timings to experiment, but only use one now (125ms; I groupfire for full dps).

Thus, I can change between fire modes relevant for my current mech/build on a button press.

Mr Friday, on 22 June 2013 - 11:00 AM, said:

I ended up using this to chat in MWO:

; Install the keyboard hook to circumvent CryEngine
#InstallKeybdHook
 
; The virtual keypress delays
SetKeyDelay, 0, 0
 
; Set the message to be sent
Message = HF, GL & Bacon!
 
; Send the message
Send {RAW}%Message%

Those should allow you to send key presses to the chat box.

If you don't mind not creating your own I made one that easy to edit as all you needed to do was add variables according to its naming convention, like so:

Spoiler

; G menu
; The global quick chat menu
VGS_G_Menu = 1
VGS_G_Global = 1
 
VGS_G_A = Awesome
VGS_G_B = Good Bye
VGS_G_D = I Don't Know
VGS_G_F = GLHF
VGS_G_G = Good Game
VGS_G_H = Hello
VGS_G_L = LOL
VGS_G_N = Neg
VGS_G_O = Oops
VGS_G_Q = Quiet on Comms
VGS_G_S = Sorry
VGS_G_T = Thanks
VGS_G_V = Help
VGS_G_W = You're Welcome
VGS_G_X = I'm Dead
VGS_G_Y = Aff

So the key combination "VGF" (V to start the VGS, G for the menu, F for the sub option) would send "GLHF" to All chat. If your interested in this just say and I'll post up a link.

What role does the menu play? Why not just V, F? Or do you have other functionality (V, <something else> <something else>)?

[Mr Friday]

The key 'V' was chosen simply to start the VGS system as it steals all keypresses. While entering the VGS macro you can't control your mech.

And yes there are other menus. The current list is this:

Spoiler

-------------------------------
Legend:
-------------------------------
?	Number
_	Space key

$	Callsign:
		_ = None
		1-0 = Alpha-Mike
		A-Z = Alpha-Zulu

%	Position: (Used in pairs: A1, A_, _1, etc)
		_ = Line
		1-0 = Row
		A-Z = Column

&	Mech: (Used in pairs, second number is mech in release order: 1,1 = Jenner, 1,2 = Commando, etc)
		1 = Lights
		2 = Mediums
		3 = Heavies
		4 = Assaults

*	Other Command:
		Specifies that this command allows the input of another command after it, used for 'pairing' commands
		eg: VL1 ("Lance 1"), followed by CC ("Capture Enemy Base") prints: "Lance 1 Capture Enemy Base"
-------------------------------

-------------------------------
Macros:
-------------------------------
VCC	Capture Enemy Base
VCE	Capture Epsilon
VCG	Capture Gamma
VCH	Capture Highest Base
VCK	Capture Kappa
VCL	Capture Lowest Base
VCN	Capture Nearest Base
VCT	Capture Theta
VCS	Capture Sigma

VDC	Defend Our Base
VDE	Defend Epsilon
VDG	Defend Gamma
VDH	Defend Highest Base
VDK	Defend Kappa
VDL	Defend Lowest Base
VDN	Defend Nearest Base
VDT	Defend Theta
VDS	Defend Sigma

VEC	Switch ECM to Counter
VED	Switch ECM to Disrupt
VEF$	Disrupt $
VEV$	Counter $

VGA	Awesome
VGB	Good Bye
VGD	I Don't Know
VGF	GLHF
VGG	Good Game
VGH	Hello
VGL	Lol
VGN	Neg
VGO	Oops
VGQ	Quiet On Comms
VGS	Sorry
VGT	Thanks
VGV	Help
VGW	You're Welcome
VGX	I'm Dead
VGY	Aff

VHA	Aiming Help
VHH	Heat Help
VHL	LRM Help
VHO	Override Shutdown Help
VHP	PPCs Help
VHR	Targeting Help
VHS	SSRM Help
VHT	Torso Twist Help
VHU	Ultras Help
VHW	Weapon Group Help

VIC	Damn Clanner
VID	Damn Fedrats
VIF	Damn Freebirth
VIK	Damn Dracs
VIL	Damn Liao
VIM	Damn Marik
VIP	Damn Pug
VIR	Damn Rasalhague
VIS	Damn Steiner
VIT	Damn Trashborn

VL?*	Lance ? *
VLA*	Assaults *
ALD*	Direct Fire Support *
VLH*	Heavies *
VLI*	Indirect *
VLL*	Lights *
VLM*	Mediums *

VMA%	Attack %
VMB	Return To Base
VMC	Go To Cap
VMD%	Defend %
VMF%	Firing Line %
VMH%	Hold %
VMI%	LRMs %
VML%	Flank Left %
VMM%	Move %
VMR%	Flank Right %
VMS%	Scout %

VNA%	Enemy: Attack %
VNB	Enemy: Return To Base
VNC	Enemy: Push To Cap
VND%	Enemy: Defend %
VNF%	Enemy: Firing Line %
VNH%	Enemy: Hold %
VNI%	Enemy: LRMs %
VNL%	Enemy: Flank Left %
VNM%	Enemy: Move %
VNR%	Enemy: Flank Right %
VNS%	Enemy: Scout %

VP%*	Grid % *...

VQ$A	$ has Stream SRMs
VQ$B	$ is a Brawler
VQ$D	$ is Direct Fire Support
VQ$E	$ has ECM
VG$F	$ is Fast
VQ$G	$ has Gauss
VQ$I	$ is Indirect Fire Support
VG$J	$ has Jump Jets
VQ$K	$ has Streak LRMs
VQ$L	$ has LRMs
VQ$N	$ has NARC
VQ$P	$ has PPCs
VQ$R	$ has RACs
VQ$S	$ has SRMs
VQ$T	$ has Tag
VQ$U	$ has UAC/5s
VQ$2	$ has AC/20s

VS$&	Spotted $ &

VT$	Target $

VU*	Lance *

VVA	Awesome
VVB	Good Bye
VVD	I Don't Know
VVF	GLHF
VVG	Good Game
VVH	Hello
VVL	Lol
VVN	Neg
VVO	Oops
VVQ	Quiet On Comms
VVS	Sorry
VVT	Thanks
VVV	Help
VVW	You're Welcome
VVX	I'm Dead
VVY	Aff

VWA	has Stream SRMs
VWB	is a Brawler
VWD	is Direct Fire Support
VWE	has ECM
VWF	is Fast
VWG	has Gauss
VWI	is Indirect Fire Support
VWJ	has Jump Jets
VWK	has Streak LRMs
VWL	has LRMs
VWN	has NARC
VWP	has PPCs
VWR	has RACs
VWS	has SRMs
VWT	has Tag
VWU	has UAC/5s
VW2	has AC/20s

V_	(Stops the VGS, prints any prefix command by itself)
-------------------------------

Note that some of the macros may be out of date, like the grid reference parts not being able to handle more then 10 rows.

Its definitely too much, but I tend to use TS most of the time, so it was more of a curiosity then anything I tried to get really simple. The system works, but the command list needs some.

Edited by Mr Friday, 22 June 2013 - 03:09 PM.

[Koniving]

Koniving, on 01 June 2013 - 11:20 AM, said:

Actually figured it out! Thank you.

Both of these use Left CTRL, which is also mouse button under my ring finger.
I use this for the LB10, MG, AC/2 Jager. It's set to fire the AC/2s in groups 3, 4, and 5. My Shotgun fires on group 1, and the MGs are in the comfortable to hold group 2.

Spoiler

#SingleInstance Force
#InstallMouseHook
#InstallKeyBDHook

#IfWinActive ahk_class CryENGINE
LCtrl::
while GetKeyState("LCtrl","P")
{
send {3 down}
sleep 85
send {3 up}
send {4 down}
sleep 85
send {4 up}
send {5 down}
sleep 85
send {5 up}
}

Finally got around to vids using this macro.