9.1.4: Combat Event blocks goal count

[bru888]

This is an obscure one but can be reliably reproduced.

If Combat Event is set for a trigger with a Check Unit Count condition, the game does not include the goal count in the Turn Overview window:

Screenshot 3.jpg (445.69 KiB) Viewed 1391 times

Screenshot 4.jpg (229.93 KiB) Viewed 1391 times

If Any Event is used instead, the goal count appears:

Screenshot 5.jpg (445.76 KiB) Viewed 1391 times

Screenshot 6.jpg (256.47 KiB) Viewed 1391 times

I may have been seeing this in 9.0.6 but certainly in 9.0.7. I happened to stumble across the Combat Event / Any Event relationship in this latest scenario that I am working on because I left Any Event in the trigger by mistake. The goal count was displaying at that time. When I changed the trigger to Combat Event, it disappeared. I subsequently flipped back and forth and reliably reproduced the error.

[bru888]

Heh, rearranged some objectives, forgot this problem, changed back to Combat Event, encountered the problem (again), and had to rediscover the Any Event workaround.

[bru888]

By the way, here is evidence of the issue in a DLC scenario. Scroll down to what I said about the "Destroy 15 Axis land units" trigger condition, the linked objective, and Combat Event as the trigger event:

viewtopic.php?f=264&t=107786

[bru888]

I'm not sure what this meant on the 9.1.4 changelist:

• [EDITOR] Fixed bug with Check Unit Count

but if it refers to this issue, it's still not fixed in version 9.1.4:

Screenshot 3.jpg (534.8 KiB) Viewed 987 times

Screenshot 4.jpg (533.93 KiB) Viewed 987 times

Screenshot 5.jpg (518.89 KiB) Viewed 987 times

Screenshot 6.jpg (531.32 KiB) Viewed 987 times

Screenshot 7.jpg (552.79 KiB) Viewed 987 times

[terminator]

The "solution" could be to create a Trigger with Trigger Event = Scenario Start which only counts the number of units (at the beginning of the scenario)

Crimea(1).jpg (491.55 KiB) Viewed 978 times

[bru888]

The "solution" could be to create a Trigger with Trigger Event = Scenario Start which only counts the number of units (at the beginning of the scenario)

That would work only once, wouldn't it? Then it would disappear on Turn 1?

Besides, it is broken as of a patch or two or three ago and it should be fixed. For now, the easiest workaround is to schedule the trigger for "Any Event."

A long time ago, an OOB sage advised that, to enhance scenario performance, it was best to keep the amount of checks that the game must perform down to a minimal number. He said "Any Event" worked against this idea because the game literally checks the trigger every time ANYTHING happens in that case. Every time any unit moves, for example.

I haven't noticed any difference in performance, really, when I use "Any Event" but the theory is there. Then again, a while ago, I upgraded my game playing with a laptop that has a very large brain. I may have noticed a difference if I was still using my old clunker.

[Shards]

FWIW, I would actually advise to use Any Event on Check Last Kill now anyway. As you'll need that to test for Disbands (which that trigger now supports).

I don't think the occasional use of Any Event like your examples here, should kill performance, just as long as you've not got dozens all running at once

Ta

[terminator]

The "solution" could be to create a Trigger with Trigger Event = Scenario Start which only counts the number of units (at the beginning of the scenario)

That would work only once, wouldn't it? Then it would disappear on Turn 1?

The problem remains when we Save & Load the counter no longer appears