I just had a very frustrating experience in an Assault match on River City. When my team started getting close to the enemy base, the targeting key started to fail. I had several situations where I would be at point blank range with an enemy mech that was not under an ECM field, and the targeting key would do nothing. The problem got worse as my team got closer to the enemy base's turrets. Has anyone else been experiencing this issue?
1
Problems Targeting When Turrets Are Nearby
Started by Dth2Vwls, Feb 10 2014 03:47 PM
4 replies to this topic
#2
-
-
- Legendary Founder
- 1,859 posts
Member
- LocationCanuck transplanted in the US
Posted 10 February 2014 - 05:04 PM
Dth2Vwls, on 10 February 2014 - 03:47 PM, said:
I just had a very frustrating experience in an Assault match on River City. When my team started getting close to the enemy base, the targeting key started to fail. I had several situations where I would be at point blank range with an enemy mech that was not under an ECM field, and the targeting key would do nothing. The problem got worse as my team got closer to the enemy base's turrets. Has anyone else been experiencing this issue?
Haven't run into this yet, but have limited experience with turrets so far. Have you also submitted a support ticket with the description and a rough estimate of date and time? Good luck with resolution.
#3
-
-
- Bridesmaid
- 461 posts
Member
Posted 10 February 2014 - 05:35 PM
I believe I have experienced what you are speaking of.
What it seemed like to me, was that turrets were stealing priority over Mech targets.
What I mean by this is that in a similar situation, on a map without turrets, when there are 2 or more targets in your front view, you can prioritize which one you will target by getting your cursor/targeting reticle closer/closest to that one. You can even go so far as to turn your view screen so that only one target is still visible and that target will get priority when you press 'R'.
The turrets seem to count as "in front of you/under your reticle" no matter what position they are relative to your view. And when there are numerous turrets revealed by friendly target sharing, even if you have one and only one target in your forward view, if that target is a Mech, all the revealed turrets will cycle indefinitely and your desired Mech target will never receive a high enough priority to become your selected target.
I've encountered this at least two times, the most recent was on River City. Towards the end of a match, I saw an Atlas (AS7-D, I think) in the water walking only a few meters away from the out-of-bounds line that is parallel with the docked freighter. The Atlas was heading towards the freighter. I closed to within 200m so that my view consisted entirely of Atlas and out-of-bounds and I still could not target the Atlas to get a readout of what location I should aim for. We exchanged several volleys during which I continuously pressed 'R' thinking repetition might eventually cycle through to the Atlas. It never did.
What it seemed like to me, was that turrets were stealing priority over Mech targets.
What I mean by this is that in a similar situation, on a map without turrets, when there are 2 or more targets in your front view, you can prioritize which one you will target by getting your cursor/targeting reticle closer/closest to that one. You can even go so far as to turn your view screen so that only one target is still visible and that target will get priority when you press 'R'.
The turrets seem to count as "in front of you/under your reticle" no matter what position they are relative to your view. And when there are numerous turrets revealed by friendly target sharing, even if you have one and only one target in your forward view, if that target is a Mech, all the revealed turrets will cycle indefinitely and your desired Mech target will never receive a high enough priority to become your selected target.
I've encountered this at least two times, the most recent was on River City. Towards the end of a match, I saw an Atlas (AS7-D, I think) in the water walking only a few meters away from the out-of-bounds line that is parallel with the docked freighter. The Atlas was heading towards the freighter. I closed to within 200m so that my view consisted entirely of Atlas and out-of-bounds and I still could not target the Atlas to get a readout of what location I should aim for. We exchanged several volleys during which I continuously pressed 'R' thinking repetition might eventually cycle through to the Atlas. It never did.
#5
-
-
- Overlord
- 13 posts
Member
Posted 10 February 2014 - 10:59 PM
Domenoth, on 10 February 2014 - 05:58 PM, said:
Yup, that's exactly what I've been experiencing. It's good to know that the devs are aware of this. I sent an email to support about this.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users
