88 replies to this topic

[GODzillaGSPB]

Just a last statement: Your script makes this game so much more enjoyable. Sometimes it's the small things. Having the zoom on the wheel is so great and intuitive.

I still think it deserves a thread, even in it's current state.

[evilC]

It's coming.
As I now have virtual joysticks working with MWO, I can now do absolutely everything (Keyboard, joystick, mouse mapping) with AutoHotkey, PLUS have a GUI to control it all.

Check out my Universal Joystick Remapper

So, yeah, I am about to start compiling a couple of threads that are designed to be permanent, rather than my proof-of-concept threads or comments on other people's threads.

[GODzillaGSPB]

Since I don't want to spam in your other topic, here's what I think after a quick read:

It could need a bit more "advertising". I mean there are already working joysticks in MWO. You should flesh out the advantages of your virtual joystick right at the start of the thread, in a "features" or "what does it do?" section.

[Capt Jester]

You can always set the right mouse button to group 6 and set TAG to group 6 if you don't want to mess around with macros.

[evilC]

Capt Jester, on 18 January 2013 - 03:01 PM, said:

You can always set the right mouse button to group 6 and set TAG to group 6 if you don't want to mess around with macros.

This guy is a genius, I dunno why I bothered writing a script!

GODzillaGSPB, on 18 January 2013 - 08:20 AM, said:

Just a last statement: Your script makes this game so much more enjoyable. Sometimes it's the small things. Having the zoom on the wheel is so great and intuitive.

Do you mean the complex zoom? Have you been using it? Reliable?

GODzillaGSPB, on 18 January 2013 - 02:59 PM, said:

Since I don't want to spam in your other topic, here's what I think after a quick read:

It could need a bit more "advertising". I mean there are already working joysticks in MWO. You should flesh out the advantages of your virtual joystick right at the start of the thread, in a "features" or "what does it do?" section.

I think you are right. I need to remove the contents of the readme and do as you say.

[GODzillaGSPB]

evilC, on 18 January 2013 - 04:34 PM, said:

This guy is a genius, I dunno why I bothered writing a script!

Definitely! I have to admit...just yet I realised my mouse has buttons at the side! O_o

evilC, on 18 January 2013 - 04:34 PM, said:

Do you mean the complex zoom? Have you been using it? Reliable?

No, the simple script. Still...night and day difference.

[TheLastUn1corn]

Hey evilC, I have a question about your script.

I have to admit it's my first time to use AutoHotkey, so I'm inexperienced with it.
I downloaded your script code, created a new script file, named it "zoom+tag.ahk" and pasted your code.
Then I saved the script and double clicked it, the "H" icon appeared in the taskbar, so I knew the script was active.

Sadly, it didn't function in the game: working the mouse wheel caused no effect and pushing it made my 'Mech throttle down instead of TAGging. So what am I probably doing wrong? Does this work for all mouses? Do I need to have the controls on default for it to work?

I'd really like to use your script...

Please help me!


Thanks
TheLastUn1c0rn

[Will3019]

My easy answer: bind it to a toggle switch instead of a push-button. I have it on the pinky toggle on my throttle quadrant. Now if only they would give an option to make night vision and thermal vision push-and-hold instead of toggling, my boat switch would work right.

[evilC]

OK, just to clarify, I now separate out tag toggle and zoom into two scripts.
TAG toggle is this one: http://evilc.com/fil...o/tagtoggle.ahk

To debug the script:
Open the AHK file in a text editor, find the following TWO lines and add a ; at the start of each line:

#IfWinActive, ahk_class CryENGINE

#IfWinActive

Now right click the green H and choose "Reload this script".
This will stop the script only working in MWO. Now you should be able to open a notepad window, hit the buttons and see the generated output appear in the notepad window.
So, if you have the tagtoggle set to weapon group 6, when you hit the trigger button, does 6 appear in the notepad window?

If it does, the script is working fine.
Do you have the number keys 1-6 bound to weapon groups 1-6?
Is Middle Mouse bound to anything in MWO?

Edited by evilC, 30 January 2013 - 04:05 AM.

[TheLastUn1corn]

I had a look at my controls. Weapon groups are set to 1-6 as by default, mouse buttons 1, 2, 4 and 5 are bound to the first four weapon groups (these are left and right button as well as two side buttons). Mouse button 3, the wheel, is not set to anything.

I put the " ; " before the two lines and reloaded the script; but nothing changed at all. After that I created a new script with the code you posted above. Sadly, this didn't work either. I tried changing the "Mbutton" to "WheelDown", but this didn't give any results, too.

Pressing the Middle mouse button in a document also didn't type any letter or symbol. By the way, when I activated the old script (TAG + zoom) and turned the wheel up and down in some notepad, the output was z and v, but pressing the button also had no effect.

So what's wrong here?


If it is important, my mouse has the four buttons I mentioned and a 4-way-wheel.

[evilC]

There is no such AHK control as "WheelDown" - "MButton" *is* wheeldown.

Maybe in your mouse config app, wheel down is not configured to send middle button? If you have a logitech, just leaving it on the default setting may not work, you may need to set it to "Middle Button", or "Generic Button 3"

[FerrolupisXIII]

hello there, i tried out your script. couldnt seem to get it to work either. i admit to ahving no idea what im doing. i did edit the scrip, as suggested, to run out of the game, and did a test click, i got this as a return:

059: Return (31.36)
067: if (TAGMode ==1)
070: Return (0.16)
078: if (TAGMode == 0)
079: EnableTAG(1)
130: SetScrollLockState,On
131: Send,{%WeaponGroup% down} (0.06)
132: if (update == 1)
133: TAGMode = 1
134: }
135: }
080: }
083: Return (1.76)

any help? like i said im not familiar with this stuff so if you can see whats wrong explain like you would to a new kid lol

:edit: forgot to mention, that little box that pops up when i load the skript, is set to weapons group 6.

Edited by FerrolupisXIII, 30 January 2013 - 09:34 AM.

[evilC]

OK, let's simplify this a bit.

create a new AHK file and place the following code in it:

MButton::
   MsgBox, Middle Mouse Pressed
   return

Run it and hit the Middle mouse button.
Does a dialog pop up saying "Middle Mouse Pressed" ?

If not, then AutoHotkey cannot recognise your middle mouse button - this will be an issue with the setup of your mouse.
What mouse do you have?

Edited by evilC, 30 January 2013 - 12:53 PM.

[FerrolupisXIII]

yup, middle mouse button pressed!

its a logitech wireless, i forget the exact model.

Edited by FerrolupisXIII, 30 January 2013 - 05:46 PM.

[evilC]

What's with all the numbers at the start and end of each line above?
You don't have those in your AHK file do you?

Quote

059: Return (31.36)

[FerrolupisXIII]

nope. i haven't got a clue what they are haha

[evilC]

So if you right click the link for the tagtoggle, and save as an ahk file (Rather than copy and paste the text), it still does not work?

[FerrolupisXIII]

just tested, saved that link as an AHK file, ran it. box that pops up is set to 6. got in match, still no luck. damn,

Edited by FerrolupisXIII, 31 January 2013 - 09:01 AM.

[evilC]

And you put your TAG in weapon group 6?

[TheLastUn1corn]

It's me again.

Sadly, the problem doesn't give me the chance to "simplify" it: created your little script, pushed mouse wheel - a window pops up, saying "Middle Mouse Pressed". That means, that my mouse is working correctly and Autohotkey reckognizes it, so the problem must be somewhere else. TAG is definitely set to weapon group 6. Do I have to to anything with the little window that pops up when I run the tagtoggle.ahk beyond selecting group 6?

Any other ideas? May there be a mistake in the code, by any chance? Maybe some # or ; left out? Sadly, I can't read that code properly and don't know the rules it is based on, so I can't search for mistakes myself...

Edited by TheLastUn1corn, 31 January 2013 - 02:43 PM.