Location: Frozen City night
Match: Skirmish
Mech: Stormcrow
Description:
At approximately 600m away from my position a brawl was taking place near the ridge between 6 mechs. At this distance I could see a Dire Wolf with no friendly blue triangle coming out of the tunnel near the ridge. I suspected he was supported by an ECM mech and began hitting him hard with LPL.
He turned and looked at me but did not fire. Luckily right next to him was a friendly Dragon Slayer and I had assumed his attention had changed to the DS. I moved closer to under 400m and hit the DWF again.
But then I realised something was not right as the two mechs started moving together side by side. I was stood right behind them both and the DS had the friendly blue triangle while the DWF had nothing.
This error cost us the game as we lost by one man and if you were the pilot of the DWF then I apologise.
It didn’t happen again over the next few drops, but pilots beware of this.
TR 3
![](https://static.mwomercs.com/forums//public/style_images/master/icon_users.png)
![](https://static.mwomercs.com/img/house/lonewolf.png)
No Friendly Blue Triangle On Teammate.
Started by T R3, Sep 06 2014 02:51 AM
8 replies to this topic
#1
Posted 06 September 2014 - 02:51 AM
#2
Posted 06 September 2014 - 08:11 AM
This just happened my first match today....
![Posted Image](http://i.imgur.com/YwsA958.jpg)
#3
Posted 06 September 2014 - 09:07 AM
This has been going on for a while and the devs know about it. Whether or not they'll do anything to fix it is another matter.
Please devs, I've killed and been killed by this bug, it needs some priority.
Please devs, I've killed and been killed by this bug, it needs some priority.
#5
Posted 06 September 2014 - 10:42 AM
Darth Futuza, on 06 September 2014 - 09:09 AM, said:
They do? Do you have evidence of this? Seems like they keep ignoring it and I've never seen a response about it yet.
I believe they addressed it (along with desyncing which I've also seen continue post patch) as one of the major reasons there was a server overhaul besides just moving the data center.
Edited by lockwoodx, 06 September 2014 - 10:42 AM.
#6
Posted 07 September 2014 - 02:10 AM
I can totally concur.
I noticed this at least five times last night and it almost caused me to alpha strike a poor (team mate) firestarter in the back.
I noticed this at least five times last night and it almost caused me to alpha strike a poor (team mate) firestarter in the back.
![:(](https://static.mwomercs.com/forums/public/style_emoticons/default/sad.png)
#7
Posted 07 September 2014 - 03:35 PM
Yeah, I've noticed it several times.
(Also @The Luggage: Wellington representin')
(Also @The Luggage: Wellington representin')
#8
Posted 07 September 2014 - 04:09 PM
I reported this bug first on April 18th 2014. (Still got the email)
The answer was that it is a known bug and efforts are taken to solve the problem.
For several month I didn't see ist - but for some reason it reappeared some months ago. I see this in about 1 out of 5 games (me or teammates).
And it is a matchbraker. Pretty please, PGI, give us a statement about this.
The answer was that it is a known bug and efforts are taken to solve the problem.
For several month I didn't see ist - but for some reason it reappeared some months ago. I see this in about 1 out of 5 games (me or teammates).
And it is a matchbraker. Pretty please, PGI, give us a statement about this.
#9
Posted 07 September 2014 - 05:12 PM
This just happened to me on Crimson strait. I was in an Ember and the unmarked friendly was in a summoner. He was real banged up and came into my view. So I finished him off. Needless to say he was upset. I am also not pleased about the TK penalty for a hud bug. Please look into this.
I did notice one or two friendlies without markers at the start of the match but paid it no mind. In my prior experience the issue would correct itself during the first couple minutes of the match. Not so this time.
I'm not sure how I would reproduce this, seems server side.
I did notice one or two friendlies without markers at the start of the match but paid it no mind. In my prior experience the issue would correct itself during the first couple minutes of the match. Not so this time.
I'm not sure how I would reproduce this, seems server side.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users