3 Commando Brigade

I've not had any issues with it today at all

Gonna wait until you guys start demanding that we remove AGM, otherwise you're gonna hate me.

Notification:

Due to the continued instability (clients crashing to desktop), we will unfortunately be taking a backward step on the public server in order to try to find out what is causing the problem. The process will be along the lines of:

- remove @agm, @african_conflict, @nato_russian_sf_weapons, @rh_m4_a3; we'll be using BTC Revive and fighting AAF
- test
- re-add @agm
- test
- re-add @rh_m4_a3 / @nato_russian_sf_weapons

So the public server will go down in the early hours tonight, at 00:30 29th October.

The mission will revert to the previous non-AGM version (3CB_BMR-Insurgency_v15t.Takistan Changelog) and the Public Repo will be updated with the reduced mod list.
Make sure you have your favourite Armoury load-outs saved without any equipment from the mods to be removed, or you'll end up re-making them from scratch.

It's a shame, none of us want this, but it's necessary, so please don't be hating.  ;-)

If you get crashes, please continue reporting them here (date/time/circumstance), this is vital information.

Modset 29/10/14
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@outlw_magrepack
@st_nametags
@sthud_a3
@stkr_bi
@task_force_radio
@trixie_britishweapons
@vts_gesture
@vts_weaponresting

Optional
@st_stamina_bar
@tao_foldmap_a3

Mission
3CB_BMR-Insurgency_v15t.Takistan  Changelog

Admin Notes
BattleEye off, Bikey's On.

Thanks andvik.

Mission reverted to last known 100% stable configuration, v9.

Let's try again.

Admin Note for 29/10/14.

Server started off fine for a few hours on modset #1 (5-6 players), but as more players joined in the evening (12+) crashes became more and more frequent. 1 every few minutes. Everyone affected.

Changed to modset #2, same player base, same mission - crashes just as frequent. Game became pretty much unplayable with frequency of client ctd's.

Changed to modset #3, same player base, same mission - instant stability, no client crashes over 2 hours.

Conclusion? Looks like either @asdg_jr, @trixies_britishweapons or @stkr_bi causing ctd's,

Modset #1
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@outlw_magrepack
@st_nametags
@sthud_a3
@stkr_bi
@task_force_radio
@trixie_britishweapons
@vts_gesture
@vts_weaponresting

Optional
@st_stamina_bar
@tao_foldmap_a3

Crash crash


Modset #2
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@outlw_magrepack
@st_nametags
@sthud_a3
@stkr_bi
@task_force_radio
@trixie_britishweapons
@vts_gesture
@vts_weaponresting

Optional
@st_stamina_bar
@tao_foldmap_a3

Crash crash


Modset #3
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@outlw_magrepack
@st_nametags
@sthud_a3
@stkr_bi
@task_force_radio
@trixie_britishweapons
@vts_gesture
@vts_weaponresting

Optional
@st_stamina_bar
@tao_foldmap_a3

Stable.


EDIT
Added late on, 6 players:

Modset #4
@african_conflict [Added]
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@nato_russian_sf_weapons [Added]
@outlw_magrepack
@rh_m4_a3 [Added]
@st_nametags
@sthud_a3
@stkr_bi
@task_force_radio
@trixie_britishweapons
@vts_gesture
@vts_weaponresting

Optional
@st_stamina_bar [Added]
@tao_foldmap_a3 [Added]

Was also stable.

That is somewhat odd as Trixies and asdg_jr have been on for a while now with no issues and there have been no updates for them. The most recent addition is Stkr_bi. What happens if you just remove that?

Can we go one step further and do it in order of dependency? So just add asdg_jr for a day or two, then add trixie for a few days, then add stkr_bi? (It's the only order that we can do, thanks to dependencies)

Howl had a good idea last night - with the current stable modset (minus Trixie/ASDG/STKR_BI) can we try adding AGM to see if the crashes resurface or not? I don't think this is something we've tried yet.

I'm not sure what we can do about the issues with Trixie/ASDG/STKR_BI since they are all dependencies of eachother, making it hard to pinpoint exactly what one is causing the issue (and we can't try running one without the other).

As I said above, we can do *some* elimination testing, if we do ASDG_JR, then ASDG_JR && Trixie and then ASDG && Trixie && Stkr_BI