Jump to content

Ultra AC5 macro's


69 replies to this topic

#21 Paladin1

    Member

  • PipPipPipPipPipPipPip
  • 836 posts
  • LocationCapellan March, Federated Suns

Posted 02 November 2012 - 04:08 AM

View PostCptPlanet, on 01 November 2012 - 04:14 AM, said:

For those of you saying 'make it jam the whole match', that wouldn't work either, because people just wouldn't use them.


I agree that if you made it a permanent jam as it stands now, it would drive players away from it but if you reduced the jam rate to 6% (such as it jams if you fire it within the first 6% of the weapon's recharge time) then it becomes not only a known skill but something that will add a realistic feel to the UACs instead of the current jam rate. Most importantly, the devs need to note in the patch notes that keeping your UAC from jamming is now a skill instead of pure chance as it seems now.

#22 Sayyid

    Member

  • PipPipPipPipPipPip
  • 482 posts

Posted 02 November 2012 - 04:15 AM

View PostAllekai, on 01 November 2012 - 02:52 AM, said:

seems to be common place for anyone using this weapon.. I personally believe there should be some sort of system in place to identify and ban people using macro's it's nullifying the jamming system put in place to prevent continualy chain firing these weapons.. which is being basically hacked out of the game with macro's



How do you ban people running a macro to fix it? I have a gaming mouse that has a built in flash drive, that I can program to run macros. I am not "hacking" or cheating, I am using my tools to their most.

#23 Khobai

    Member

  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • Elite Founder
  • Elite Founder
  • 23,969 posts

Posted 02 November 2012 - 04:18 AM

The problem isnt that people are using macros.

The problem is that jamming is so unintuitive it even requires a macro in the first place. They need to change it.

#24 Mylar

    Member

  • PipPipPipPipPip
  • Bad Company
  • 105 posts

Posted 02 November 2012 - 10:14 AM

So, i have not used an ultra AC since early closed if at all, and I don't remember it jamming.

If it does jam what is the non-macroed, manual, in game procedure for clearing the jam?

#25 Gigastrike

    Member

  • PipPipPipPipPipPipPip
  • FP Veteran - Beta 1
  • FP Veteran - Beta 1
  • 704 posts

Posted 02 November 2012 - 10:49 AM

View PostMylar, on 02 November 2012 - 10:14 AM, said:

So, i have not used an ultra AC since early closed if at all, and I don't remember it jamming.

If it does jam what is the non-macroed, manual, in game procedure for clearing the jam?

You have to go to the U-AC5 row and remove/add it twice on all 6 fire groups.

#26 Tasorin

    Member

  • PipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 825 posts
  • LocationCartman 3050 HQ

Posted 02 November 2012 - 11:04 AM

Why should I and others be banned because we spent the money to have a programmable I/O and mapped a simple macro?

So all programmable I/O should become a banable offense?

How about we ban $hytie threads about useless garbage that clutters up the General Discussion boards?

#27 Mylar

    Member

  • PipPipPipPipPip
  • Bad Company
  • 105 posts

Posted 02 November 2012 - 01:20 PM

View PostGigastrike, on 02 November 2012 - 10:49 AM, said:

You have to go to the U-AC5 row and remove/add it twice on all 6 fire groups.


...
...

Not sure if serious.

...


If so... WHAT?
Talk about counter intuitive.

Is that a bug that it unjams the weapon that someone stumbled onto, or did someone actually think "Hmm we need an unjam procedure for a weapon, oh I know!!!" and program THAT in? Heh, that must have been a very late night or somone had an extra helping of crack flakes for breakfast that morning.

Is that documented someplace in game? Do the instructions roll up on the screen when the weapon locks?
I'm a bit of a forum ***** and I've NEVER seen anything about that till these macro threads started up.

#28 CptPlanet

    Member

  • PipPip
  • Little Helper
  • Little Helper
  • 37 posts

Posted 02 November 2012 - 01:44 PM

I can't remember if this was documented or not (though I assume it was somewhere...at some point...) but that is the way to unjam it. Nothing tells you to, but all the weapons groups in line with the UAC/5 start flashing.

That's definitely the procedure though. Hence my macro on my G9x.

#29 Hexenhammer

    Member

  • PipPipPipPipPipPipPipPipPip
  • Legendary Founder
  • Legendary Founder
  • 3,729 posts
  • LocationKAETETôã

Posted 02 November 2012 - 02:18 PM

And how will PGI identify the players using macros? Programmable keyboards and mice can inject the code at the peripheral level and once its gone through the Kernel/OS/DLL its no different than anything input command.

Ban programmable keyboards and mice? Blizzard did that to some players. Image how happy you'd be if you tried to log into a game only to find out your account has been banned for running a Bot program when you're only crime was having a G series Logitech keyboard. Well it happened and it pissed off a lot of players. Blizzard corrected it but it left a nasty taste in some players mouths.

#30 Jacmac

    Member

  • PipPipPipPipPipPipPip
  • 828 posts

Posted 02 November 2012 - 02:50 PM

Tyring to ban a macro is like trying to plug leaky pipes with toilet paper, pretty much a total waste of time.

**** piper pipes

What the heck, pip3 is a bad word?

Edited by Jacmac, 02 November 2012 - 02:53 PM.


#31 Vermaxx

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bridesmaid
  • Bridesmaid
  • 3,012 posts
  • LocationBuenos Aires

Posted 02 November 2012 - 03:02 PM

Unless I did my math wrong, rolling a 2 on 2D6 is a 3 percent chance, not 6. The current chance is 10.

#32 Paladin1

    Member

  • PipPipPipPipPipPipPip
  • 836 posts
  • LocationCapellan March, Federated Suns

Posted 02 November 2012 - 03:30 PM

View PostVermaxx, on 02 November 2012 - 03:02 PM, said:

Unless I did my math wrong, rolling a 2 on 2D6 is a 3 percent chance, not 6. The current chance is 10.

That'd be my bad memory acting up again, it actually is 2.8% (close enough to 3%) but I was thinking you had to roll a 4+ to keep from jamming the UAC. I was actually thinking of the RAC instead and even there I was wrong, as you have to roll a 5+ at maximum rate, which is a 16.7% chance to jam.

Anyway, like you pointed out, it's still way too high of a percentage chance to jam.

#33 Shawgrin

    Member

  • Pip
  • Liquid Metal
  • Liquid Metal
  • 13 posts
  • LocationNorthern California

Posted 05 November 2012 - 09:30 PM

The macros I use for firing and jam clearing are very short for my Nostromo by Belkin/Razor. For firing I set the UAC5 to group 6.

To fire
repeats while button is held down.
6 down
.250ms
6 up
.250ms

to clear I repeat this one six times with one button push.
cntl
.1ms
cntl
.1ms
right arrow

#34 Tickdoff Tank

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,647 posts
  • LocationCharlotte NC

Posted 05 November 2012 - 09:53 PM

The Devs hate the un-jam procedure as well. They have spoken of throwing their keyboard accross the office in frustration. So a fix WILL be made. It will most likely be either A: a simple delay in your next shot (5-10 seconds) or B: hit a button to unjam (like J) and it then takes 5-10 seconds to unjam. Either un-jam may also consume 1 shot of ammo for the weapon (it has been discussed, but not gaurnteed).

Untill then, just use the macro.

#35 spook9

    Member

  • Pip
  • 11 posts

Posted 17 November 2012 - 09:00 AM

View PostevilC, on 01 November 2012 - 05:50 AM, said:

QFT.

Here is an autohotkey macro that will unjam your UACs.
Use up and down to place the cursor on the first UAC5.
Then use mouse wheel up to unjam the first one and down for the second.
DO NOT try to do both at once, wait for the first one to finish.
; MWO Dual UAC clearing script
; Usage: Use up/down arrows to position cursor on first UAC5, then...
; Roll the mouse wheel up to clear the 1st AC
; Roll the mouse wheel down to clear the 2nd AC
 
 
#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.
;SendMode Play  ; Games Compatibility.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
#InstallMouseHook
#InstallKeybdHook
 
sleepdur = 50
  
Wheelup::
	Clear()
	Return
 
Wheeldown::
	Send {Down}
	Sleep sleepdur
	Clear()
	Send {Up}
	Sleep sleepdur
	Return
	
 
Clear()
{
	Global sleepdur
	Loop, 6 {
		Loop, 2{
			Send {RCtrl}
			Sleep sleepdur
		}
		Send {Right}
		Sleep sleepdur
	}
	Return
}

You can make it faster or slower by changing sleepdur.
It can work on 25, but it may be a little unreliable.


Couldn't get this to work with my Cicada today. Works fine outside of MWO. Has this been patched somehow?

#36 Chemie

    Member

  • PipPipPipPipPipPipPipPipPip
  • Bad Company
  • Bad Company
  • 2,491 posts
  • LocationMI

Posted 17 November 2012 - 10:35 AM

View Postspook9, on 17 November 2012 - 09:00 AM, said:


Couldn't get this to work with my Cicada today. Works fine outside of MWO. Has this been patched somehow?


Not patched. I cannot get autohotkey to work in game at all for anything (like tag press)

#37 Allekatrase

    Member

  • PipPipPipPipPipPip
  • 357 posts

Posted 17 November 2012 - 10:40 AM

I think they should give it a 5-10 second unjam cycle that you have to press a key to initiate. During this cycle it should disable all your weapons. That way you will have to think about when to use it.

Any kind of user input mini-game is ridiculous. It's automatic weaponry that is known to jam. The designers would have built in a mechanic that allowed it to be unjammed and given that it was designed to be mounted on a mech it's not like the pilot is going to jump out and go work on the gun. It would be a switch or button at most. Maybe he has to switch it on and then switch it off 10 seconds later.

Edited by Allekatrase, 17 November 2012 - 10:43 AM.


#38 197mmCannon

    Member

  • PipPipPipPipPipPip
  • Go-cho
  • Go-cho
  • 265 posts
  • LocationCincinnati, OH

Posted 17 November 2012 - 10:42 AM

I use a macro.

It's the first time I've ever actually used the macro ability of my g15 keyboard that I bought years ago.

Wish I could figure out how to make a key toggle with it for turning my tag on and off.

View PostAllekatrase, on 17 November 2012 - 10:40 AM, said:

I think they should give it a 5-10 second unjam cycle that you have to press a key to initiate. During this cycle it should disable all your weapons. That way you will have to think about when to use it.



Sounds awesome but no one would use the weapon if that were the case. I've had mine jam 5 times in one match before. I've had it jam again immediately after unjamming it.

And when I said it sounded awesome I was being sarcastic. It's a horrible idea.

#39 Allekatrase

    Member

  • PipPipPipPipPipPip
  • 357 posts

Posted 17 November 2012 - 10:44 AM

View PostDaemian, on 17 November 2012 - 10:42 AM, said:

I use a macro.

It's the first time I've ever actually used the macro ability of my g15 keyboard that I bought years ago.

Wish I could figure out how to make a key toggle with it for turning my tag on and off.




Sounds awesome but no one would use the weapon if that were the case. I've had mine jam 5 times in one match before. I've had it jam again immediately after unjamming it.

And when I said it sounded awesome I was being sarcastic. It's a horrible idea.

Well, it's an incredibly powerful weapon even without double firing. I just started using it recently and haven't jammed it at all since then. It has a crazy refire rate and the ability to double fire. If you want to risk the double firing you need to risk putting the weapon out of commission for the rest of that particular engagement. Then, when you're between fights you can clear it.

If it's just a delay or a button press I feel like the weapon is going to be too strong. My understanding is the current "feature" was implemented because it was too strong of a weapon.

Edited by Allekatrase, 17 November 2012 - 10:45 AM.


#40 TheMightyWashburn

    Member

  • PipPipPipPipPipPip
  • Overlord
  • Overlord
  • 281 posts
  • LocationUSA

Posted 17 November 2012 - 10:48 AM

I have a macro for it. Takes about .5 seconds to unjam it. Games should be made so that macros cant make something overpowered (minimum cool downs and the like)

Since this system is unusable as is PGI is not going to do anything anyway. Besides, there is basically no other way a macro could exploit in this game. In fact, compared to other MP games its quite nice how few(none that ive seen) glitches there are. No one doubles there damage or anything. I take it this is because it is run mostly server side? (as opposed to say TF2 where people can use autoaim and instant kill hacks)

I dont use the gun even with my macro though. It still jams every 5 frekkin seconds and it takes me atleast a second to notice and press the macro button. I prefer AC/2s anyway.





5 user(s) are reading this topic

0 members, 5 guests, 0 anonymous users