Page MenuHomeFeedback Tracker

Mortar fire location known with out spotter
Closed, ResolvedPublic


I like how the mortars are not precise when your location is know by the enemy but the problem is they know where you are without anyone spotting you. You can be sneaking up a hill with no one in sight and the next thing you know a mortar lands on you.

If the user needs to call in the location of a mortar to the mortar team the AI should also need to do so. Unless they guess but it seems much to close to be a guess.

Note: Even if the enemy has called in a direction of attack, they should be putting rounds down in a situational spot instead of directly on top of the unknown location of enemy contacts.

EDIT: This can be hugely problematic when you get a radio call about mortar teams firing and the only thing you can do is run around like a chicken with your head cut off in the open hoping no enemy AI spot you when doing so.


Legacy ID
Steps To Reproduce

Play any game mode against a mortar team. Once rounds start coming in they are almost ALWAYS with in 40 yards of you with NO ONE around to spot. If this is done via UAV then our intelligence team should be relaying that there is a UAV over head and taking cover would avoid the same situation.

Additional Information

This is not the same thread as the precision of artillery, though it should also be considered (which it has been)

Event Timeline

jakeryan760 edited Additional Information. (Show Details)
jakeryan760 set Category to Explosives.
jakeryan760 set Reproducibility to Always.
jakeryan760 set Severity to None.
jakeryan760 set Resolution to Open.
jakeryan760 set Legacy ID to 3429392439.May 7 2016, 3:45 PM
Peter added a subscriber: Peter.May 7 2016, 3:45 PM
Peter added a comment.Jul 30 2013, 7:50 PM

Yeap. I was in a mission in the editor with two AI mortar teams and try it alot of times and at the end I decide to not put them due to their accuracy but I miss to report.
Upvoted mate.

MadDogX added a subscriber: MadDogX.May 7 2016, 3:45 PM

Mass closing ancient tickets with no activity for > 12 months; assume fixed or too trivial.

If this issue is still relevant in current dev build, please re-post.