Addendum: similar applies to the Kuma MBT - mirrors cannot be re-textured.

We've found out that a palette colliding with a tent was the root of all evil. Seems the AI somehow sensed the palette cracking and imemdiately went to COMBAT mode. While this ticket might not refer to a bug it's certainly important to tweak this AI behaviour and make it more believable.

Follow the discussion here: http://forums.bistudio.com/showthread.php?189736-Units-Are-In-Combat-Mode-On-Mission-Start-Since-1-40

Ticket may be closed. Contrary to the information posted in the thread linked under Additional Information it actually is possible to re-texture the NVGs using hidden selections: http://forums.bistudio.com/showthread.php?187206-Re-Texturing-NLAW-and-NV-Goggles&p=2851587&viewfull=1#post2851587

FT doesn't allow me to attach the .mdmp. Not sure if it's helpful anyway but I've uploaded it on my dropbox instead:

https://www.dropbox.com/s/qn9b3enhkf5alnn/arma3_2014-11-08_15-58-42.mdmp?dl=0

Always happy to help. ;)

Hi,

description file attached. Publisher version is 1.0.126977 though I don't know if it was the same when I opened this ticket.

Steam Addon Name: [SP-Campaign] M.E.R.C.S. - 0.55 ALPHA
Steam Link: http://steamcommunity.com/sharedfiles/filedetails/?id=314091056

True, but the biki states that if you use the trigger in timeout mode the condition must be satisfied throughout the whole given time. When the condition is met in countdown mode the onAct is simply delayed. I'm just saying that the way it is now, is redundant even if it's not a bug. In this case here it doesn't matter whether you use timeout or countdown - the outcome is the same. And that should be changed in my opinion, so we don't have to use (simple) workarounds to achieve the desired goal.

Hm, if it's not a bug then it's at least not a good feature. You can achieve this functionality also via setting the trigger to countdown. So there's in my opinion more point in changing it like desired in this ticket than to keep it this way.

@Killzone_Kid: Thank you very much, that seems to work!

@MulleDK19: Why is this not a bug?

Can confirm this behaviour. Have to find a scripted solution then...