15 replies to this topic

[GingerBang]

Seriously. Now AC/2 macros within like 200 meters just TANKS the FPS for literally every person i know who plays this game. It is ridiculous. IF it wasn't an exploit before, it sure is now since you just get in anybodies face and lag them out of play.

Edited by Prosperity Park, 07 July 2013 - 08:04 PM.
title changed to reflect the OP's intentions

[Wintersdark]

Again, you can do exactly the same thing as the macro just by rolling your fingers across the numbers then holding one down.

You don't need a macro to staggerfire AC/2's. The above method fires them slightly faster than your normal macro, too.

Ban fingers and keybinds!

Silly monkeys.

[MonkeyCheese]

Wintersdark, on 06 July 2013 - 10:50 PM, said:

Again, you can do exactly the same thing as the macro just by rolling your fingers across the numbers then holding one down.

You don't need a macro to staggerfire AC/2's. The above method fires them slightly faster than your normal macro, too.

Ban fingers and keybinds!

Silly monkeys.

I like the part where he complains about AC2s affecting the frames per sec and you think he is complaining just about macros alone... cute

[Wintersdark]

MonkeyCheese, on 07 July 2013 - 01:35 AM, said:

I like the part where he complains about AC2s affecting the frames per sec and you think he is complaining just about macros alone... cute

Yeah, isn't it? I mean, when he said:

Quote

Now AC/2 macros within like 200 meters just TANKS the FPS for literally every person i know who plays this game.

... How could I have assumed he was just ragging on macros? Clearly he meant they should just ban AC2's.

Edited by Wintersdark, 07 July 2013 - 05:09 AM.

[Modo44]

Maybe it's because you don't need macros for UAC5s, as they work best when just holding fire.

[LastPaladin]

Wintersdark, on 06 July 2013 - 10:50 PM, said:

Again, you can do exactly the same thing as the macro just by rolling your fingers across the numbers then holding one down.

Sure, but if there is an FPS drop issue, it should probably still be addressed, just not by banning the macro. Instead, by looking at what about the rapid fire is causing the FPS drop.

Also, I've experience massive FPS drops twice in the last day, but I didn't associate it with AC/2 macros or rapidfire. Once was on frozen city near theta cap, when two dragons rounded the corner. The FPS drop actually started slightly before we started exchanging fire. The second time, it was on frozen city, again, when a Quickdraw hopped over the ridge between the dropship and the mountain.

Both times on the same map, only when a particular enemy or enemies came near. Both times I had heat vision turned on, and both times it didn't seem to matter whether they were firing anything, much less AC/2s. The drop was continuous until I died. I have a high end machine and no problem running the game even on the highest graphics settings, so I am certain this is a situational issue and not some run of the mill hardware issue.

[Wintersdark]

LastPaladin, on 07 July 2013 - 12:15 PM, said:

Sure, but if there is an FPS drop issue, it should probably still be addressed, just not by banning the macro. Instead, by looking at what about the rapid fire is causing the FPS drop.

Absolutely. If there is a problem, fix it.

My objection was to the op and his irrational or ignorant rage at macros, as if they had anything whatsoever to do with the problem.

[LastPaladin]

Wintersdark, on 07 July 2013 - 12:21 PM, said:

My objection was to the op and his irrational or ignorant rage at macros, as if they had anything whatsoever to do with the problem.

Yeah, I know when I get killed by framerate rather than the enemy, it is infuriating though, so I can understand why he's looking to rage against something. It's just misplaced I think.

[Drunk Canuck]

Modo44, on 07 July 2013 - 05:47 AM, said:

Maybe it's because you don't need macros for UAC5s, as they work best when just holding fire.

When they are in chain fire mode, sure.

[Felicitatem Parco]

I would suggest the OP perhaps change the thread title and opening passage to remove the term "macro" and replace it with "Staggered AC/2s" because that would both eliminate ambiguity about the thread's purpose and [thereby] reduce comments related to how to stagger-fire AC/2s.

[FREDtheDEAD]

If there's an FPS drop with staggered AC2s, imagine what a six machinegun Jager will do! That's like a hundred bullets on the screen at once or something! Crazy!

How can any gaming PC cope with this madness?

[El Bandito]

My LRMs laugh at FPS drops.

[Asmosis]

Modo44, on 07 July 2013 - 05:47 AM, said:

Maybe it's because you don't need macros for UAC5s, as they work best when just holding fire.

If you hold fire its still 0.5sec between shots, its better to click rapidly or even better have a macro.

As for topic, I'm going out on a limb here, but i think PGI are better off fixing w/e is causing the issue (which must've been introduced recently) rather than banning people for having a bug.

Not that it should matter, if you fire 6 at the same time or (macro) chainfired its still 6 individual projectiles and all their own animation etc going off every 0.5 seconds, so i strongly doubt macro's have much to do at all with the lag they introduce.

Ban jaggermechs with 6ac2 in general then?

[Modo44]

Drunk Canuck, on 07 July 2013 - 12:48 PM, said:

When they are in chain fire mode, sure.

No. Someone tested this, and the UAC5 DPS turned out to be much better when simply holding fire than with double tap macros, because the macros generated more jams.

[Asmosis]

^ ah, lol.

of course holding down fire will generate less jams per second as its firing slower than either clicking fast or using a macro. Thats just common sense.

[Modo44]

The point is, holding fire also auto-double-taps every few shots. You get less jams and a better overall firerate than with macros. ah lol

Edited by Modo44, 07 July 2013 - 10:40 PM.