You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Arma 3 Version:x.xx (stable / rc / dev) CBA Version:3.x.x (stable / dev + commit hash) ACE3 Version:3.x.x (stable / dev + commit hash)
Mods:
- CBA_A3
- ace
Description:
After headshot, you go straight to CardiacArrest, so you do not bleed at all. To fix such a status you simply perform CPR and wake patient up.
proposed to be solved by not circumventing the unconsciousness on instant fatal injury when you cannot simply die from it but you go to Cardiac arrest, instead let the one hit go unconsciousness and cardiac arrest could then only be reached by bleeding out.
Add the list of modules you have placed on the map. Use 'None' if the error occurs without any modules.
RPT log file:
Add a link (gist or pastebin) to the client and/or server RPT file. An instruction to find your RPT files can be found here.
If possible at the time the bug is encountered, go to ACE Options and select "Debug To Clipboard", this will print extensive debug information to the RPT file.
The text was updated successfully, but these errors were encountered:
Arcanum417
changed the title
Severe injuries are better then bloodloss
Severe injuries are better then blood loss
Nov 27, 2017
Arma 3 Version:
x.xx
(stable / rc / dev)CBA Version:
3.x.x
(stable / dev + commit hash)ACE3 Version:
3.x.x
(stable / dev + commit hash)Mods:
Description:
After headshot, you go straight to CardiacArrest, so you do not bleed at all. To fix such a status you simply perform CPR and wake patient up.
proposed to be solved by not circumventing the unconsciousness on instant fatal injury when you cannot simply die from it but you go to Cardiac arrest, instead let the one hit go unconsciousness and cardiac arrest could then only be reached by bleeding out.
Steps to reproduce:
Where did the issue occur?
Placed Modules:
RPT log file:
The text was updated successfully, but these errors were encountered: