Bugs from Campaign, Missions and World categories.

[.kju 3245]

Might be useful to update the first post and to give an overview about remaining

training/mission/campaign issues ordered by (personal) priority or ticket quality?

[Hanzu 10]

Might be useful to update the first post and to give an overview about remaining

training/mission/campaign issues ordered by (personal) priority or ticket quality?

Thanks for the opinion PvPscene! You can see by the editing date that I have been updating it quite frequently, but since editing is not giving "Instant email notification" and not so many may notice that I have updated it, I have decided to add new replies every now and then.

I would like to hear more opinions what readers of this thread would prefer.

1) For me to update the first post only

2) For me to update the first post and write reply when something new is beeing assigned, rejected, resolved or closed.

But I will also try PvPscene's suggestion to add overview about remaining

training/mission/campaign issues ordered by (personal) priority or ticket quality.

Pretty much all tickets here have good repro's so it is not hindering their fixability as much as lack of worktime from a couple of people able to do the job, but with good hopes I still keep updating this to give better chances of getting more fixes for these categories.

[.kju 3245]

Maybe it would be useful to bother / remind Dwarden about an a2 beta patch to be able confirm the content fixes. ;)

[Beagle 684]

All that I would demand is that all units in game have at least the same level in functionality. It simply can't be that a BRDM has "RADAR" for the driver but a BTR90 or LAV25 has not. Same goes for BMP3 and T90 ATGM not beeing steerable and shooting out of aim. And its time to make the G36 colimator sight on A2 G36 functional again... like in v1.0.

And why do neither MV22 nor UH1Y feature countermeasures???

[.kju 3245]

@Beagle

Did you read the topic name?

[OMAC 254]

maybe it would be useful to bother / remind dwarden about an a2 beta patch to be able confirm the content fixes. ;)

YES! :)

---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------

I would like to hear more opinions what readers of this thread would prefer.

1) For me to update the first post only

2) For me to update the first post and write reply when something new is beeing assigned, rejected, resolved or closed.

#2 :D

Edited November 6, 2011 by OMAC

[Hanzu 10]

Maybe it would be useful to bother / remind Dwarden about an a2 beta patch to be able confirm the content fixes. ;)

According to my information I got those fixes will come out with soon to be released 1.60RC (release candinate).

Edit: Well they did come out but with A2 1.11 beta first.

Edited November 27, 2011 by Hanzu

[Hanzu 10]

Closed: http://dev-heaven.net/issues/11778

Good work BIS!

[Hanzu 10]

Tested bunch of bugs with CO 1.60.76705 to be successfully fixed in ARMA 2 beta 1.11.86688 and happy to set these issues status as Closed:

Fixed: Boot Camp 01: Basic Training - MOUT Saber team attacks too early if player is doing Anti-Tank range first (http://dev-heaven.net/issues/16362)

Fixed:

---

First To Fight [Multiplayer] helicopter insertion kills human players 2, 3 and 4 (http://dev-heaven.net/issues/25633)

Fixed:

---

Manhattan mission Cpt. Shaftoe is sometimes killed by his chair because his feet are sticking through it.(http://dev-heaven.net/issues/25560)

Fixed:

---

Manhattan mission GPS COORDS 000003 marine misplaced at top left corner of map (http://dev-heaven.net/issues/20154)

Fixed:

---

Manhattan mission Task: Escort contact to LZ Lagushina can teleport herself to helicopter (http://dev-heaven.net/issues/12265)

Fixed:

---

Delaying the Bear mission subtitle texts and dialog voices in wrong order (http://dev-heaven.net/issues/13113)

Fixed:

---

Dogs Of War mission Notes->Situation has typing error - Vybor airoprt should be Vybor airport (http://dev-heaven.net/issues/25631)

Fixed:

---

Dogs Of War mission Tasks Deal with Russians has error saying Russian base is at Krasnostav airport when it is at Vybor airport (http://dev-heaven.net/issues/25632)

Fixed:

---

Dogs Of War mission GPS COORDS 075101 Chedaki POW killed by NAPA supply trucks (http://dev-heaven.net/issues/25629)

Fixed:

---

War That Never Was mission looking around in helicopter is not working when playing [Combined Operations] (http://dev-heaven.net/issues/18503)

Fixed:

---

War That Never Was mission Rodriquez and O'Hara movement is terribly out of sync (http://dev-heaven.net/issues/18504)

[Hanzu 10]

Confirming these fixes:

Fixed:

---

Manhattan mission is not launching for me at all. (http://dev-heaven.net/issues/26602)

Fixed:

---

Bitter Chill is broken - black screen not removed after mission start (http://dev-heaven.net/issues/26603)

Fixed:

---

Bitter Chill mission Get In destroyed HMMWV (M2) traps Razor Team inside forever(http://dev-heaven.net/issues/18658)

Assuming this is fixed too although nothing visible seems to have changed:

Fixed:

---

Bitter Chill mission GPS COORDS 081060 two NAPA scouts and NAPA fighters are sometimes killed at NAPA safehouse yard (http://dev-heaven.net/issues/25634)

Disappointingly still not fixed with all recent MP fixes:

---

Bitter Chill mission [Multiplayer] Task: Reach NAPA positions will not complete after end scene dialog stops and mission will not end like it should. (http://dev-heaven.net/issues/15536)

[Jezuro 452]

---

Bitter Chill mission [Multiplayer] Task: Reach NAPA positions will not complete after end scene dialog stops and mission will not end like it should. (http://dev-heaven.net/issues/15536)

Got fixed today, not sure when it will be released though.

[Hanzu 10]

Got fixed today, not sure when it will be released though.

Very nice! I edited the subject name to match what you BIS found out. Also let me add that same issue occurs with "Reach CDF lines"-objective. See my latest comment at previous ticket: http://dev-heaven.net/issues/15536#note-23

[britishlegion 1]

Thanks Mate this could really help! :D

[Jezuro 452]

Also let me add that same issue occurs with "Reach CDF lines"-objective.

Fixed as well.

[Hanzu 10]

Fixed as well.

Very nice, thank you! We also just tested with zGuba and noticed it really was because of human controlled Rodriguez in this objective too. With human zGuba playing Rodriquz mission did not end and with zGuba playing O'Hara mission ended normally.

Also tested some other issues in same mission and noticed they were gone:

Closed: http://dev-heaven.net/issues/25676

Closed: http://dev-heaven.net/issues/15537

[Leg 10]

I'm still getting the issue on Dogs of War: "alliance between guerrillas and BLUFOR has ended", and then NAPA starts firing at you during the conversation.

[Hanzu 10]

I'm still getting the issue on Dogs of War: "alliance between guerrillas and BLUFOR has ended", and then NAPA starts firing at you during the conversation.

I have completed Dogs Of War in CDF side. Same message always appears there when you start mission and everytime after savegame is loaded. In the halfway of the mission, CDF and NAPA will reform alliance (in case Prizrak is eliminated) and after that the message stops coming.

I can only imagine these reasons for NAPA shooting at you in the start:

1) Playin with very old patch (this bug was present in A2 1.03 or something)

2) Using endmission cheat in any of the previous missions (which can cause anything)

3) Using mods

4) Old bug has been resummoned by some other data changes

Just for coincidence I'm currently trying to complete Badlands once again. I will try to start Dogs Of War with NAPA to see if I can reproduce your bug (and one other bug that appeared only in Dogs Of War with NAPA).

This will take a while, so in the meantime you could tell what patch and build are you using and if you have used endmission cheat or mods?

[Leg 10]

Just for coincidence I'm currently trying to complete Badlands once again. I will try to start Dogs Of War with NAPA to see if I can reproduce your bug (and one other bug that appeared only in Dogs Of War with NAPA).

This will take a while, so in the meantime you could tell what patch and build are you using and if you have used endmission cheat or mods?

I'm using Beta 86652 at the moment.

I recently went (1.60RC1 -> Reinstall -> 1.59 -> Beta 86652). I had better performance with RC1, but I downgraded to use JayArma2Lib(mod) with a group last sunday.

I am on NAPA's side. But it seems to work now that I replayed Badlands straight into Dogs of War. I recall that I exited the game right after beating the mission, so maybe some data wasn't saved properly. Anyways, it is fixed thank you.

[Jezuro 452]

Also let me add that same issue occurs with "Reach CDF lines"-objective. See my latest comment at previous ticket: http://dev-heaven.net/issues/15536#note-23

Can you please confirm this is fixed in 1.60 RC2?

[Hanzu 10]

Can you please confirm this is fixed in 1.60 RC2?

Confirmed to be fixed (with 1.60.87580 FINAL) and closed (with some comments):

http://dev-heaven.net/issues/26916#note-2

Edited December 27, 2011 by Hanzu

[Hanzu 10]

Closed: http://dev-heaven.net/issues/25628

Closed: http://dev-heaven.net/issues/15536

Closed: http://dev-heaven.net/issues/25634

Re-Assigned: http://dev-heaven.net/issues/25676

[Hanzu 10]

Assigned: http://dev-heaven.net/issues/27396

[Hanzu 10]

Re-assigned: http://dev-heaven.net/issues/25627

Assigned: http://dev-heaven.net/issues/27298

[Hanzu 10]

Re-assigned: https://dev-heaven.net/issues/18491

Assigned: https://dev-heaven.net/issues/27442

Edited: https://dev-heaven.net/issues/25636

[Eclipse4349 0]

---

- v. 1.60

4th mission

The mission that has you searching for Lopotev and you have the support option of help extraction from Starforce 21:

Calling for extraction works, the chopper flies to your location and lowers to the ground, hovering until your squad is all in. Then nothing happens. There is no prompt to do anything, and the help just sits there hovering. I only have played in single player, and I hadn't played ARMA for quite a while, until 1.60 and it's mp fixes was released. I do not know if the problem was a result of v1.60 or a previous patch.