No, a radar Fox1 missle tracking someone we are are not tracking is not in our hands
Then why do you fire in such an instant?!?
At this point just dont bring IR missles and dont kill anyone in game and you wont TK… LOL hilarious
Ok, so we jump from one statement and exaggerate it into ridicule…
I’m talking about trigger discipline, situational awareness, mindfulness of the possible consequences of a shot, not “woe, woe, they don’t want us to use our missiles anymore!”
To be fair, your earlier statement about trigger discipline is…questionable.
In the screenshot you see that the enemy is locked, being tracked and moving towards the player. This is all we know about trigger discipline, as this indicates that things are good to go.
If the missile then decides to ignore the radar lock and go for a completely different target…not self destruct or anything, but actively going after a different target, then that is hardly the players fault.
If you counter that argument with trigger discipline, then you seem to be unaware of how a 16 vs 16 game lobby works in game.
My man I just wanna grind get as many kills I can, If I got radar LOCKED im shooting and if Im gonna be punished for that let it be. Simple as that…
Ok, that’s of course your choice to decide like that. = )
Since the screenshot was from someone else’s clip, I can’t tell you why he shot a radar missle instead of a IR missle. My guess is that at the time he shot the radar missle he was to far away to shoot a IR missle and expected the Enemy to easily flare it. the radar missle did not lose Lock since it went for the Friendly right after being launched
I mean I have like 20 examples just from today where I lock target at 20km with F-4S then shoot AIM-7f sparrow while still having radar lock and missle after like 200 meters just goes to who knows where or just explode… But hey again that has to be my mistake and game cant be bugged right?
Gotta wait until they are 10km or less away if you use the AIM-7F/M :)
I’m not saying that those things may not be buggy. What I’m saying is that - knowing that such things are possible in the game, in such a situation, why fire then, being fully aware that this can go wrong?
Sure, we all want that kill, and I’d be a terrible liar if I claimed I don’t fall for this again and again as well. But I try not to, if it can be avoided.
- Where is Blue? How does he move? Where will he be in 5 Seconds?
- Where is Red? How does he move? Where will he be in 5 Seconds?
- Is anybody using countermeasures?
- Where’s the sun? Where is the ground, mountains?
- Is there anyone else around? More Blues? More Reds?
- Am I really sure that Blue is blue and Red is red?
- What weapon do I want to use? What are its limitations? What the limitations of my radar?
And even:
- May the game be bugged in a way that firing now could lead to unwanted and even unrealistic results?
But of course it can. That shouldn’t be a free pass to TK though…
Because I expect from devs and Gajin to fix this and give us all bug free radar missles… Do I expect too much?
So launch range 100km means nothing and Lock range of 40KM also means nothing?
I get this but when I have 2 hours and 420k reserch points to go I really could not care less…
I think that bug should be fixed, Im not saying it should be used to TK someone…
Not saying you’re wrong, but…I’ll make an assumption here.
Your target audience for the game is rather young, has no military experience and wants a fast, action packed experience.
Gaijin wants to provide a conflict oriented, fast paced action that caters to the (predominantly) younger audience, who is willing to spend disposable income to gain progress in the game or access modules/weapons/features that are locked behind a grind wall.
So if the audience wants action and Gaijin delivers action, then the expectation of people exercising trigger discipline is nothing but wishful thinking.
I’m sure Gaijin has recognised this already, but I fail to understand why a friendly fire mechanic in Air RB is active and in Ground RB it is disabled.
Anyways, I’m not against punishing Teamkillers, but I’m against regarding an accidental Teamkill the same way as a Teamkill made on purpose. Especially, when the mechanics to prevent that exist in the game.
Then instead of 16v16 make its 3v3 with current map size, greatly expand team communication options (i.e. mandatory voice chat), give everyone a free HOTAS and silly costume, then we can pretend we are in the air force. Otherwise that’s not happening
After watching YouTube gameplay of top tier I am honestly terrified to play it. Your description of the gameplay is a very rose tinted glasses version of it.
It’s absolutely not in the player’s hands for a SARH or ARH missile to IGNORE a prior AND/OR current locked aircraft and just go where else it wants to go.
That is not how it functions in real life and that’s not how it should function in the game. The burden is on Gaijin to correct flagrantly obvious egregious bugs such as incorrect missile behavior. That is their duty as developers of the game.
I never said that it would be. I said it’s in the players hand to fire or not fire in such a situation.
I fully agree, and I do hope that this (along with other things) get fixed.
But that still does not change my personal opinion that even if it’s buggy or not optimally implemented, knowing this and still taking the shot makes me responsible for the TK. And such TK’s can be prevented by the player.
If the players fire on the basis of “but it should not be like tis”, they still accept the potential risk that the will commit a TK, and this (as this discussion here shows), even if they’re fully aware of the risk, be that risk based on correct or wrong implementation of real life aspects, or indeed based on faulty mechanics or bugs is quite irrelevant, I find…
So it’s the player’s fault that Gaijin can’t code the game to function properly? So because Gaijin can’t code the game properly I and everyone else have to absolutely play passively in nearly every situation?
Your logic and argument stance in all this is so fundamentally flawed it’s genuinely irritating.
This is kind of the spewed nonsense that makes people doubt whether mods, admins and even Gaijin themselves actually play the game or not.
When you stub your toe on your bedside drawer, you move it. Gaijin says cut off that toe because it’s in the way.
It’s so asinine because I’ve lost count of how many times I fired sparrows at hard locked enemy aircraft in open sky with no friendlies in the zone anywhere and the Sparrow has still done one of two things; Pissed off in a random direction to explode or tracked down an allied aircraft that wasn’t even on the screen and killed them.
But according to these guys, that stuff is still our fault when it happens.
Rrrrriiiigggggghhhhhhtttttttt.
Tell the players to just not play in the BR range with SARH/ARH missiles without telling them to just not play in the BR range with SARH/ARH missiles.
Or Gajin can put this as priority same as they put TK disabled yesterday and FIX IT ASAP?