Page MenuHomeFeedback Tracker

I am always wounded when firing from a mortar.
Closed, ResolvedPublic


Having shot three groups on eight charges I got wound. It occurs always and doesn't depend on a firing distance.
Shooting from the second mortar I receive a critical loss and I perish.
I can sometimes be lost on the first mortar.
Management of AI mortar. AI died, the mortar burned down.
It is possible to correct it?

Pure Arma3, no MOD.


Legacy ID
Operating System
Windows 10 x64
Operating System Version
Steps To Reproduce
  • Editor
  • Choose a mortar
  • Choose the second empty mortar
  • Mission start
  • Shoot all charges from the first mortar
  • Sit down at the second mortar, to shoot all charges
Additional Information

Sometimes I receive a critical loss on the first mortar. Likely depends on how steadily there is a mortar. If to look narrowly, each shot is followed by a push. I receive blow in feet about the earth from a shot.

Event Timeline

Lex edited Steps To Reproduce. (Show Details)Aug 31 2015, 11:52 AM
Lex edited Additional Information. (Show Details)
Lex set Category to Health System.
Lex set Reproducibility to Always.
Lex set Severity to None.
Lex set Resolution to Open.
Lex set Legacy ID to 2961132858.May 8 2016, 12:36 PM

People, please read rules of ticket creating!!!!!!!!!!!!!!!!!!!!!!!!
Its just another duplicate of issue :

Lex added a subscriber: Lex.May 8 2016, 12:37 PM
Lex added a comment.Aug 31 2015, 4:40 PM

The ticket with the status "new" for 2015-01-31? How I could find it?
There are differences in tickets. The player or AI receives damage always. Doesn't depend where the mortar is established and under what corner firing is conducted.
I agree that it is repetition. But I was surprised by its status).
If the reporter doesn't watch promotion of the ticket, it doesn't mean that the problem is partially solved.
Vote against - too I surprised.

Just just can add comment onder that ticked - it will be first on the list, just like new one, no need to create new tickets.

Bah, the best thing to avoid duplication could come from BI who let "new" for more than one year or declare "solved" or duplicated" some topics which aren't (see inputAction "adjust").
To be more constructive, the mortar problem is probably linked to the wound a unit catches each time you attach/detach an object to him. It seems a collision occurs with object. It is also the case if a player "bumps" an attached object on another unit. Make this experiment: attach a fuel canister or something in editor to a unit/player. Reach his position and "touch" the attached object. You're wounded. Make the unit/player prone with attached object, detach it. This time, this unit is wounded.

Lex added a comment.Jun 13 2016, 12:32 AM

When I fix this?

Lex updated the task description. (Show Details)Jun 13 2016, 12:35 AM
Lex edited Steps To Reproduce. (Show Details)
Lex set Operating System to Windows 10 x64.
Lex set Operating System Version to DEV APEX.
Lex changed Category from Health System to General.Jun 13 2016, 3:16 PM
Lex added a comment.Jul 12 2016, 9:22 AM

How much can you think, decide or not decide this issue?

Lex changed Severity from None to Tweak.Jul 12 2016, 10:07 AM
razazel claimed this task.Jul 12 2016, 10:51 AM
razazel changed the task status from New to Reviewed.
PiepMGI removed a subscriber: PiepMGI.Jul 12 2016, 3:21 PM
Lex changed Severity from Tweak to Major.Jul 13 2016, 12:26 AM
Lex added a comment.EditedJul 16 2016, 10:54 PM

It isn't cheerful, solve the ticket. It influences game process, progress.
We receive a problem there where it shouldn't be.

Lex added a comment.Sep 12 2016, 1:08 PM

As before, the player and AI receive damage to health using a mortar.

Lex removed a subscriber: Lex.Jan 28 2017, 1:56 PM
Lex added a comment.Jan 30 2017, 12:57 PM

It is reproduced in DEV 1.67 as before

razazel added a subscriber: Lex.Feb 9 2017, 4:12 PM

@Lex should be fixed one of the next Steam Dev updates (tommorow most likely) ;)

Lex added a comment.Feb 9 2017, 4:18 PM

@razazel Thank you so much

Lex added a comment.Dec 5 2017, 6:34 PM

The problem is solved. Thank you. Close this ticket.

razazel closed this task as Resolved.Dec 6 2017, 1:35 PM
razazel changed Resolution from Open to Fixed.
Lex removed a subscriber: Lex.Aug 8 2018, 1:56 PM