Paul Inouye, on 22 January 2014 - 11:20 AM, said:
#421
Posted 04 March 2014 - 11:09 PM
#422
Posted 04 March 2014 - 11:11 PM
Satan n stuff, on 28 February 2014 - 02:18 PM, said:
yeah I tend to think the nullify ECM for 30s or 60dmg will be plenty, 30s without a damage falloff could end up being too much.
#423
Posted 05 March 2014 - 12:04 AM
And in those organized groups, the standard provisions apply which always make LRM's lackluster: passive defenses, cover, etc. Folks who're capable of really exploiting NARC are the same folks (and ideally playing against the same folks) who understand how to really shut down LRM's.
#425
Posted 05 March 2014 - 02:10 AM
Kjudoon, on 05 March 2014 - 12:34 AM, said:
orrrrrr.... I was wrong. LOL
I mean, we used to be able to do this ourselves in closed beta, all that needs to be done is modifying a few numbers in an XML file. I can't imagine why that would take them four months to put in for the April patches, and for the same reasons I'm a bit perplexed as to why it's over a month late now. I mean, I can't imagine they went, "Oh hell, this makes NARC OP!" Right now, I see more flamers than NARCs. That's how bad this is.
#426
Posted 05 March 2014 - 08:42 AM
Paul after being hugged by goons said:
#427
Posted 05 March 2014 - 11:34 AM
There was a little re-engineering required to get the functionality I described earlier. When this happens, the internal dev support team needs to further test the changes to make sure something else didn't break with the code change. I have personally approved the change and dev support is just going to ensure that nothing else broke.
Again, apologies for the delay.
#428
Posted 05 March 2014 - 11:43 AM
Paul Inouye, on 05 March 2014 - 11:34 AM, said:
There was a little re-engineering required to get the functionality I described earlier. When this happens, the internal dev support team needs to further test the changes to make sure something else didn't break with the code change. I have personally approved the change and dev support is just going to ensure that nothing else broke.
Again, apologies for the delay.
keep on the good communication... yes I know I need to change my signature.
#429
Posted 05 March 2014 - 11:44 AM
Paul Inouye, on 05 March 2014 - 11:34 AM, said:
There was a little re-engineering required to get the functionality I described earlier. When this happens, the internal dev support team needs to further test the changes to make sure something else didn't break with the code change. I have personally approved the change and dev support is just going to ensure that nothing else broke.
Again, apologies for the delay.[/color]
That right there is all we ask - all of the "hmmmm, what's going on" debate can stop because we know officially. Thanks Paul!
#432
Posted 05 March 2014 - 12:54 PM
Paul Inouye, on 05 March 2014 - 11:34 AM, said:
There was a little re-engineering required to get the functionality I described earlier. When this happens, the internal dev support team needs to further test the changes to make sure something else didn't break with the code change. I have personally approved the change and dev support is just going to ensure that nothing else broke.
Again, apologies for the delay.
We'll survive. Thanks for keeping us in the loop!
Edited by Rebas Kradd, 05 March 2014 - 12:54 PM.
#433
Posted 05 March 2014 - 02:54 PM
#434
Posted 05 March 2014 - 03:44 PM
#435
Posted 05 March 2014 - 06:46 PM
Paul Inouye, on 05 March 2014 - 11:34 AM, said:
There was a little re-engineering required to get the functionality I described earlier. When this happens, the internal dev support team needs to further test the changes to make sure something else didn't break with the code change. I have personally approved the change and dev support is just going to ensure that nothing else broke.
Again, apologies for the delay.
Could you elaborate on what types of engineering changes were required to implement the described changes?
Those kinds of details tend to make us happy, and give us better insight that helps us make better requests in the future.
I think many of us appreciate that you stepped up, said it was gonna be delayed, and apologized though.
#436
Posted 05 March 2014 - 07:16 PM
Paul Inouye, on 05 March 2014 - 11:34 AM, said:
There was a little re-engineering required to get the functionality I described earlier. When this happens, the internal dev support team needs to further test the changes to make sure something else didn't break with the code change. I have personally approved the change and dev support is just going to ensure that nothing else broke.
Again, apologies for the delay.
Thanks for the word. Just good to know what's going on and that it hasn't been forgotten about.
I look forward to seeing how it works on the 18th. Would love to run my 3L as an ewar mech like it was meant to be.
#437
Posted 05 March 2014 - 07:30 PM
Question for Paul:
If 1 Narc cancels the ECM of a single Mech, would 3 lights firing 3 Narc's at 3 ECM Mech's cancel all of them during the same time?
- effectively eliminating any ECM the Enemy had. (if they only had 3 ECM Mech's.)
- could the light's simply cancel all the Enemy ECM at once?
- and would launching a UAV give any additional effects? (possibly boost the Narc jamming radius?)
I ask because we will be moving to groups of 3 of each weight class being fielded soon, and with only 5 Mech's currently capable of mounting that Guardian ECM suite. It may be rather easy to track them down and pop one on them once they are identified.
And might I also ask if there is anything in the works that allows us to keep the Id info/scan info listed once we have acquired the full read-out on an Enemy Mech.
- That does not require the full scan time, every time.
- Once id'd and scanned it will shorten any future scan attempt by the same Mech.
(thinking of something in the line of an add on sensor module, once we get the multi module brackets. Something like "id memory module" upgrade.)
BattleMechs Capable of Mounting ECM:
- Atlas-D-DC
- Cicada-CDA-3M
- Commando COM-2D
- Raven RVN-3L
- Spider SDR-5D
Thanks,
9erRed
Edited by 9erRed, 05 March 2014 - 07:51 PM.
#438
Posted 06 March 2014 - 11:39 AM
9erRed, on 05 March 2014 - 07:30 PM, said:
- effectively eliminating any ECM the Enemy had. (if they only had 3 ECM Mech's.)
- could the light's simply cancel all the Enemy ECM at once?
- and would launching a UAV give any additional effects? (possibly boost the Narc jamming radius?)
I ask because we will be moving to groups of 3 of each weight class being fielded soon, and with only 5 Mech's currently capable of mounting that Guardian ECM suite. It may be rather easy to track them down and pop one on them once they are identified.
The fact that this can even be asked with a straight face is a sure sign of what a terrible state ECM is in.
3 light mechs dedicating 4+ tons and a weapon hardpoint each, after having roamed the map (away from their main force) so that they can (potentially if they all hit) grant their team 30 seconds (assuming they all hit simultaneously) of awareness about the positions those mechs (who, while away from their team are exposing themselves for those shots, and their positions as well, unless they have the magic box too).
That's 12+ tons used to, under optimal conditions, nullify an advantage conferred by 4.5 tons, to gain the benefit of position data and target locks (which the enemy team can do to a team without ECM with any unit at any time as per the normal capabilities of any mech). Those target locks can then potentially be used for LRM locks, which will take at least a few seconds to lock, and then up to 7 more for the LRMs to actually arrive, meaning some 20 seconds of fire. Which can still be mitigated entire by getting inside 180, outside 1k, behind (the ever abundant) cover, or failing that, more heavily mitigated than ever by AMS.
ECM's most powerful attribute is, and always has been, its total nullification of the entire information warfare system in place in MWO.
The joke it makes of LRMs is just an anecdotal icing to the proverbial cake.
The moral of the story for NARC: Glad its finally getting buffed. Still won't be worth a damn in the current environment.
#440
Posted 06 March 2014 - 06:46 PM
The point I was attempting to make was, can a single launching Narc unit fire multiple Narc missiles and have them overlap each other in there canceling of ECM.
(my earlier reference of 3 vs 3 was just to get the multi Narc pods out there at the same time, and confirm that the cancelling bursts do indeed work at the same time.)
- Even if this Narc equipped Mech travels with the main body, it main job is to locate/acquire ECM mech's in the battle and take there function out of the fight. (even if for only 30 sec's at a time)
[This would work much faster when the team is using Comms.]
- And with Narc speeding up LRM as well as Streaks, the ECM carrier would most likely go down faster.
- This would make carrying that 3 Ton and 2 slot element a team asset, and not an after thought.
Within the current Mech variant's we have now there are some stock Mediums, as well as Heavy's that originally carried Narc as a normal weapon assist system. But due to there past lack luster performance, disadvantages they are quickly discarded. I'm hopping that these new additional performance buff's, (or closer to what they should have been to start) will see this element return to the battlefield. And see it return to the sometimes dangerous item it was considered in past offerings of the BattleTech Universe.
Additional note: I do think that Narc should be extended to a full 60 sec's of ECM disruption, this alone would make locating the Narc launcher unit as much a threat as the original ECM mech was. An additional balancing aspect for it's use.
9erRed
Edited by 9erRed, 06 March 2014 - 06:57 PM.
8 user(s) are reading this topic
0 members, 8 guests, 0 anonymous users