Jezuro

Nice.... Seriously though, there are some more and some less valuable evidence pieces scattered throughout the campaign. Some of them (the most important ones) are even primary mission goals. You really don't have to worry that when a mission ends before you found all the evidence you'll be punished later.

She stops the car and gets out to greet you when she sees you (i. e. if you're not in a vehicle).

If you have a command menu opened at the same time as your map, you have to use Ctrl+Mouse Wheel - the wheel alone is by default scrolling through the menu. Hope this helps.

Don't forget that you can't use either sleep or waitUntil in the FSMs as they're pre-compiled. If you need to add a delay into the code, you have to start a new script scope via spawn. ---------- Post added at 12:16 PM ---------- Previous post was at 11:51 AM ---------- First post updated with main advantages and manual conversation control.

The strings I used are defined in the core stringtable. The engine looks there if it can't find the string ID in the mission's stringtable.

The fix will be present in the upcoming patch 1.05. I edited the first post with the Interrupted event and the example mission (note that you won't be able to hear the voice samples before updating to v1.05).

Currently it's not possible to use sound files stored in the mission directory itself for the new system of conversations (the path in the bikb files starts in the addons folder). I consulted this with our programmers and they kindly made a quick hotfix. Still waiting for the commit though, I'll prepare an example mission as soon as this fix is released.

After finally identifying the problem, the fix will be present in v1.05.

Delaying the Bear is one of the "intermezzo" campaign missions (Amphibious Assault, One Week Later, Delaying the Bear) which basically just tell you what happened "on the way" between the actual missions.

http://forums.bistudio.com/showpost.php?p=1438937&postcount=11

We haven't been able to reproduce this bug. However, we've noticed some reports suggesting that Shaftoe might die occassionally with no reason, so we added some precautions for that in the recent patch. Should you still experience this issue with version 1.04, please let us know. Thank you.

We've recently identified this issue with the mission not ending properly sometimes and the fix will be released ASAP. So far, it looks like you won't have to restart the mission in order to successfully finish it. Again, sorry for this unfortunate bug.

Well actually... :)

Hi P4thog3n, are you sure you have the batteries as well? You pick them up automatically wit the designator, but you could have swapped them for another piece of equipment during the mission.

There might be some confusion about Marny's intel since the mission design underwent some major changes before the release, when it wasn't possible to change the conversation with Begunov anymore. Marny does have some vital information, but will share them with you only when the time is right.

So it definitely wasn't Dogs of War then... See, there's a catch there that you shouldn't be spotted killing him in Dogs of War. In Badlands, it doesn't really matter as he's in a quite remote location.

Hi hondobob, are you sure it's Badlands you're talking about and it's Prizrak you're killing?

Hotfix linked here: http://forums.bistudio.com/showpost.php?p=1409212&postcount=6

Yes, unfortunately. You have to either revert the mission or

As some of you have surely noticed, Steam users have been able to download a hotfix for the 1.03 patch which (apart from a couple of other things) solves this problem in Badlands. We're working hard on the next patch, and until it's done, here's the hotfix direct link: ftp://downloads.bistudio.com/arma2.com/update/Arma2_Patch103_CampaignHotfix.exe Sorry for this bug again and thank you all for your patience and understanding.

Actually, this one isn't triggered by the SecOp Manager (which is disabled throughout the whole campaign). You get this task only if the chopper gets shot down, which of course doesn't have to happen every time ;)

Recent, was introduced as a side-effect of some other changes. We're sorry for this problem, will be fixed again ASAP.

What you see on the map ingame is not a precise reflection of what's going on. All the unit positions as you see them on the map are based on your knowledge about those units. So, for instance, if you saw an enemy tank near the village of Guglovo like 5 minutes ago and then lost contact, the tank icon will stay there for some time. If you then meet the tank again say 2 kilometers away, it will "warp" on your map as well.