|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Nikka witagun
Inner.Hell
3
|
Posted - 2014.04.02 12:35:00 -
[1] - Quote
Ok, I want to let all the forgers in on +á little secret. This bug will work to your advantage with the IAFG. Pull out the assault variant, if you have specced into forges then go ahead and forget about your reduction to the charge time, the gun will charge And firethe ghost round at 2.25s, keep holding the trigger for the remaining .75s from the skill reduction, the gun will be quarter to half way through the next charge, then release and wala it will fire every time. A reload or two and the bug is fixed.
How can this benefit you? Between the dummy round and when you actually release the round, you will hold the charge. Basically the IAFG turns into the kaalikiota for the 1.5s window between shots. Very effective for moving tanks and ads.
I'm not sure I want CCP to fix it, the IAFG is all I use and it gives you much more accuracy with the increased damage and reduced charge time.
|
Nikka witagun
Inner.Hell
3
|
Posted - 2014.04.02 14:46:00 -
[2] - Quote
Just so we're clear, the Forge gun (any variant) is still firing all the shots. The gun works normally*. I have the forge tree maxed and run it 95% of the time no matter the game mode (When I'm not in the MURDERTAXI MWAHAAHAHA).
PROBLEM:
The only problem is the 25% reduction to charge time is NOT applying consistently.
It tends to be worst at the beginning of matches, and when first spawned.
EDIT: Problem # 2 -The reload bonus is not applying correctly, consistently.
SOLUTION:
for a lvl 5 Forger, the gun will charge and try to fire the round at the reduced skill time (2.25s for IAFH, 3 for Kaal, 4.5 for breach) However in order to expel the round & fire the round accurately, you must hold the trigger down for the FULL CHARGE TIME (3s for IAFG, 4 for Kaal, 6 for breach). The shot will be ready to be fired AFTER the base charge time on the gun. If you wait for the second charge to finish the gun will discharge 1 round not 2. You MUST release the trigger after the base charge time and before the next charge. Basically you have a 1.5s window of opportunity to aim and fire the IAFG.
IAFG window of opportunity with Bug Base charge = 3s skilled charge = 2.25s
after 2.25s gun will ghost fire round and begin recharging for next round. The gun is not able to expel the round before the 3s mark. However the gun WILL discharge the next round at the 4.5s mark (2.25+2.25/1st shot & 2nd shot). This means that while holding the trigger down, you will have from the 3.0s-4.5s mark to expel your 1st round. The Assault forge will hold the round just like the kaalikiota during this window allowing you to be much more accurate with your shot.
Well its broken, why is this relevant?
Yes it certainly is broken, however with the IAFG, you gain the accuracy of the kaal but maintain the damage of the assault all still with lower charge time than Kaal.
While it is not "working as intended", this will fix the bug 100% of the time. If you spawn and a tank is closing, this technique will spare you some clones.
If you spawn in a safe zone, expel a round then reload. You may have to do this once or twice before the gun works normally, but again, it works 100% of the time.
(With the reload, I am specced lvl 5 reload, I know the gun is ready when I stop reloading at the reduced time, and it reverts to the unskilled reload time. When this happens THE GUN WILL PERFORM NORMALLY.
I'm not saying CCP shouldn't fix it (although its actually VERY useful on the IAFG) to all forgers out there worth their metal, you will figure this out and be back to forging in no time. For the rest of you scrubs ruining the forge by running militia and QQing its broke, stop posting in GD and but that **** in technical support/bugs section. |
Nikka witagun
Inner.Hell
6
|
Posted - 2014.04.02 14:53:00 -
[3] - Quote
Jake Diesel wrote:
I've been forging since before 1.4 and this random firing glitch has never happened until 1.8.
Read 2 posts up, it is not random at all. |
Nikka witagun
Inner.Hell
6
|
Posted - 2014.04.02 15:24:00 -
[4] - Quote
DUST Fiend wrote:So it's not a bug if you ignore it?
Please, continue to enlighten me with your wisdom.
It is a bug that had numerous reports filed on day 1. Within hours of patch being released. If you keep up with the bug fixes, it has NO timetable to be fixed and is probably very low on the priority list.
You can continue to be useless and complain, or you can take some friendly advice on how to still be effective AV.
I have filed 3 bug reports and posted in the tech support section.
You are welcome for the wisdom, scrub. |
|
|
|