8 replies to this topic

[Moogy]

I have played many versions of battletech simulations. MWO has a very interesting feature that drives me crazy when playing.

The Radar is horrible in game play when being hunted by a Jenner.

You are running along and nothing on the radar... Low and behold you get shot in the back with lasers. Nothing.... on radar. You try and move from side to side to avoid getting shot... Still nothing on the radar and you are still taking damage in the back. After a few seconds of this... still nothing on the radar... and then you go BOOM and you see the Jenner run by like nothing happened.

After being shot the first time... I should be able to see who shot me on my radar with in 30m to 50m let`s say and see his direction.

I also remember being able to put 2 medium lasers in back to fend off this type of attack.

Getting attack from the back with this type of radar setup without the ability to defend myself is just not fun... and creates a BIG exploitable hole in the game play.

If I can't look back, If I can't shoot back... at least let me see something on the radar...

[Zenner]

Consider equipping your mech with a 360 target acquisition module.

As a light mech pilot myself, this sort of technique is really the only way to fight much larger mechs.

I would recommend turning around and looking for the threat rather than relying on your radar and not turning around because you don't see anything...You know you are getting shot in the back so turn and engage...If he's smart, he'll run away and leave you alone.

[flackee]

Quote

After being shot the first time... I should be able to see who shot me on my radar with in 30m to 50m let`s say and see his direction.

After being shot the first time, HUD and audio cues should give you an approximate idea of where he is, and usually enough to twist and target him. Of course, thats not so easy for an assault class but you really shouldn't be off on your own with nobody to cover you/target them so they do show up on your radar.

Another thing you can do is get in the mind of that pilot behind you, that is to play a light and see the situation from the other side. It helps immensely with visualizing how to counter it.

[Taryys]

It is there partially there for the team work aspect - need someone to watch your 6.

[Matte Black]

It is actually not Radar like it has been in the past, it is a line of sight sensor array. The 360 Module is the way to go.

[Moogy]

Thank you guys for all your input.

I am not sure where to find this "360 target acquisition module."

To give a better incite in to this I am running a light mech that is fast.

The idea... is like dog fighting in plains. I need to see what is on my six... if all my team is dead.... what is the point... nothing is on radar...

Again

If I can't look back, If I can't shoot back... at least let me see something on the radar...

Thanks for all the help.

[Redshift2k5]

Moogy, on 29 November 2012 - 10:55 AM, said:

Thank you guys for all your input.

I am not sure where to find this "360 target acquisition module."

To give a better incite in to this I am running a light mech that is fast.

The idea... is like dog fighting in plains. I need to see what is on my six... if all my team is dead.... what is the point... nothing is on radar...

Again

If I can't look back, If I can't shoot back... at least let me see something on the radar...

Thanks for all the help.

go to the Pilot Lab, click modules. Click sensors. Buy 360 target retention for 15000 GXP

Go to mechlab, go to the module stab, buy the module for (how many?) million c-bills.

not cheap. note that it requires you to have already targetted the enemy and to maintain them as your target, and they will remain visible on your minimap even if they are behind you. It is target retention, (ie, you do not 'lose' your target) not 360 radar.

[gamingogre]

I saved up a long time for the 360 target retention. I slapped this very expensive (15000gxp and 6,000,000 c-bills) module into my COM-2D armed with 3 SSRM2. As soon as the target was not in front of me it was gone. The module changed nothing. I was the only ECM for both teams so this was not a factor. I reported it as a bug to the support e-mail.