Livewyr, on 29 April 2014 - 06:07 PM, said:
The detection modifiers in the book are referring to active sensors that do not (need to) have line of sight, as compared to LoS spotting (P. 221). That is largely a moot point in MWO as (aside from seismic) we don't have non-LoS detection, at all. We have IR sensors for LoS detection.
Guardian does not effect LoS detection, or targeting computers.
Given that we've been granted a built in pseudo-C3 network in the translation to real-time movement/fire dynamic, unless the mech is within 180m of the ECM, it should be able to pass on the LoS/Targeting computer detection through his Pseudo-C3 connection to team mates.
Target I.D. and other information may be hidden (as they are a product of the sensors and not the targeting/Mk1 eyeball) but the targeting computer's (C3 Master) lock is unaffected.
(Caveat: I'm perfectly fine with ECM delaying the lock-on time for tracking missiles, as the importance of tracking missiles is increased in a dynamic movement system compared to turn-based.)
Firstly, there is a difference between "LOS detection" and what TacOps is describing on pg. 221, which is "visual spotting" (which relies on the pilots own eyes & a set of optical cameras installed on the 'Mech) in contrast to sensor spotting (which relies on non-visual-spectrum sensors - e.g. radar (which isn't always LOS-dependent), lidar (which is strictly LOS), sonar (which is also dependent on LOS for monostatic/non-
bistatic systems), thermographic, seismic, magscan, and so on).
Obviously, Guardian should/would not interfere with visual spotting (as it cannot make the 'Mech visually invisible - that is the purview of
CLPS and VoidSig).
PGI then evidently made a design decision to model their rendition of IR sensor spotting on how
thermographic cameras and
passive infrared (PIR) sensors work in reality - both are strictly LOS sensors, incapable of seeing through walls or terrain.
We also have seismic sensor spotting (where a design decision - based on feedback from the playerbase - was made to change MWO seismic spotting so that it could only display data when the spotting 'Mech was both on the ground and not moving its feet... as would be expected from a
seismometer array ), but we do not (yet) have magscan spotting in MWO (despite it having meen explicitly mentioned in earlier planc for EW/IW, and which shouldn't/wouldn't be dependent on LOS if modern
MADs are used as the basis of its behavior).
While Guardian does affect the primary sensors that the BattleMech's Targeting-Tracking System (the "lower-case"/colloquial targeting computer), the TTS is a wholly sepatate entity from the "upper-case"
Targeting Computer (which is described (on page 238 of
TechManual) as "more than just a basic sensor tracking and targeting array" and is more of "a series of recoil compensators and gyroscopic stabilizers that combine to counter much of the routine weapon drift caused by the shooter’s own lurching motions, muzzle recoil and other environmental conditions"); Guardian does not interfere with the operation of the gimbals and actuators/stabilizers that make up the TC, but it does interfere with the sensors that would provide information to the TTS.
As Guardian can and does interfere with the sensors' ability to establish the presence & identity of any unit within its hemisphere of influence, what information is a forward observer going to send back to its lancemates?
If said forward unit is unable to sense anything, it has no sensor data to send. And if it's also within the umbrella of an emeny Guardian (which is evidently capable of jamming microwave/radio transmissions), its ability to send any messages at all is largely (if not wholly) negated.
Evidently, PGI made a design decision to combine the basic ECM rules found in
Total Warfare (including, most notably, the statement from page 134 of TotWar: "The ECM’s disruptive abilities affect all enemy units inside this bubble,
as well as any line of sight traced through the bubble", with the sensors' LOS evidently being included in that description) with the advanced capabilities found in TacOps.
----------
Livewyr, on 29 April 2014 - 06:07 PM, said:
1: Given that we all have access to IR vision- one can assume we see that through IR sensors on the mech, which just as we do in game, only operate on a LoS basis.
Those aren't effected by ECM. (It takes Null-Sig/Stealth tech to do that, as you just stated yourself.)
2: You keep saying that about LRM launchers, and on the most basic technical level, it is true. However, where as that might work in a static, turn-based system where the target doesn't move, 160meters per second will not hit anything aside from a target sitting still for several seconds. (An extreme rarity in MWO.)
3: I've love to see some Fire & Forget ECM tracking missiles, just to make it a little more interesting.
4: I think ECM should be reworked to remove the lock prevention, in favor of T2 tech countering *AND* an addition of limited T1 information equipment. (non-LoS mech sensors etc..)
This would allow more ECM capable mechs to be added and create an information warfare.
1.) Indeed - MWO "thermal vision" is limited to LOS observation (just as real-world thermographic cameras are) and is not affected by Guardian's influence (that is, Guardian does not make one less-visible or invisible to thermal vision - that would/should require Stealth Armor, NullSig, or VoidSig).
2.) The speed of the LRMs is independent of the fact that they can be visually-aimed at an opponent and fired without a lock, and be expected to arrive at the targeted position (assuming said position is within their range); whether the intended target is still in that position when the missiles arrive is also a separate matter.
3.) There are
a whole host of alternate munitions, for both standard missile launchers & standard autocannons, that should be implemented to provide more varied capabilities for the 'Mechs and "make it a little more interesting".
4.) PGI's implementation of Guardian is largely fine as-is; it is the sub-par implementation (or outright non-implementation) of the other EW/IW systems that needs to be rectified - Beagle, the Command Console, the as-yet-unimplemented C3 System, and a couple other things should have a broader range of useful & potent capabilities, to the point that EW/IW should be very nearly a game unto itself.