3 Commando Brigade

Ah yes, you're quite right (just woken up, yes I know it's 11:20AM in the UK  )

Let's hope we get to the bottom of this.

That is what I was referring to. We have had joint rails and Trixies weapons running together on the server for weeks now without issue and did the incremental testing with them when they were first introduced (i.e. we added joint rails, tested and passed. Then we added Trixies, tested and passed). Neither of these mods have had new updates so nothing has changed in that regard. Then we added AGM, followed by Stkr_BI. For me, the issues seemed to start with the last AGM update. If I recall, when we initially added AGM again there was no major issue and a very small RPT log (I think Apollo posted that). Then there was an AGM update roughly a week into our usage and immediately the RPT log began growing size (Again I recall Apollo posting that).

However, that doesn't explain the issues happening without AGM, but that could be down to Stkr_BI. I would keep AGM off, remove Stkr_BI, but put joint rails and Trixies back on. Leave it like that for a week and see what happens. After all there are many client reasons for CTD's and Steam ticket failures so it might not just be the server. Were the people crashing new to the public server? Are they running something in the background? Do they have stable internet etc.. etc..

Given that it seemed to be stable we've added back in @AGM today to see whether we can pass that off as ok (as everyone loves it and keeps hassling me!) before tackling the longer process of bug tracking @asdg, @trixie, @stkr_bi.

Modset 30/10/14
@african_conflict
@agm
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@nato_russian_sf_weapons
@rh_m4_a3
@st_nametags
@sthud_a3
@stkr_bi
@task_force_radio
@trixie_britishweapons

Optional
@st_stamina_bar
@tao_foldmap_a3


Mission
3CB_BMR-Insurgency_v16.Takistan

No, a mixture of existing and new. 
All had crashes at some point, including myself.
No red chains, TS comms fine.

Test was so conclusive - crash crash, change modset, same people, same internet, 4 minutes later, complete stability.

I want to check back through these pages and see if it's true that we recorded ZERO ctd's after introducing asdg, trixie, stkr_bi?

So this is the report on the AGM Test thread from October 24th. It was looking good at this point. Have any of the mods listed been updated since then? I can't remember when @AGM was updated last and I am at work so I can't check. I know TFR went through a burst of updates. Is it possible people are running different plugins of that? Would the bikey pick that up? Just trying to work out what has changed in 6 days if we rule clients out.

Report from today's Dev Server AGM test session with 15+ players:

Mission: 3CB_BMR-Insurgency_v15tAGM4.Takistan

Ran for 6 hours straight, from Midday to Midnight.
RPT file size: 169KB   -- brilliant!


Server Command Line:
__a3__\@cba_a3;
__a3__\@allinarmaterrainpack;
__a3__\@african_conflict;
__a3__\@agm;
__a3__\@beretpack2;
__a3__\@chinookpack;
__a3__\@nato_russian_sf_weapons;
__a3__\@asdg_jr;
__a3__\@rh_m4_a3;
__a3__\@stkr_bi;
__a3__\@task_force_radio;
__a3__\@trixie_britishweapons;

Bikey's on, BattleEye off.

Client Mods:
@african_conflict
@agm
@allinarmaterrainpack
@asdg_jr
@beretpack2
@cba_a3
@chinookpack
@nato_russian_sf_weapons
@rh_m4_a3
@st_nametags
@st_stamina_bar
@sthud_a3
@stkr_bi
@tao_foldmap_a3
@task_force_radio
@trixie_britishweapons


P.S. Folding maps and Stamina bar (either both or one of the two) are known to have caused issues for some. Should we not completely remove the optional mods first and test again?

TFAR - bikey's prevent people running the wrong version of TFAR, but don't check what plugin they have in TS.
I, however, did check what plugin everyone was running during the crashes by looking at the TS info for each client and they were all 0.9.7.

During the testing yesterday we took off the optionals(folding map and stamina bar) and it didn't make any difference to the crashes. I'd like to see a link to where confirmed problems with these mods are reported as so far I think it's a rumour only?

I'm pretty sure AGM has been updated since 24th Oct.

I don't believe the optional mod issues were posted on the forums. As I recall, that discussion was held on Teamspeak while we were ingame which is why they were made optional? I am tempted to say Skinny or Panda were involved, but I can't say for sure. From memory I am tempted to agree that AGM has been updated since the 24th, which as I mentioned earlier, was when the RPT leapt up to 900kb due to leg damage?

I also just noticed that yesterday's modset#2 (see apollo's post for 2014-10-29) still contained TAO, so if Apollo's list is correct the crash -> no crash change was actually "Tao folding map, asdg, trixie, stkr" ....
Please,please,please let @tao folding map be the problem...it's nice, but I want asdg/trixie/stkr way more since they're required by @3CB_units  

Apollo, is it possible that with the optional mods, the mixture of some people using them and others not may cause instability. I understand these are supposed to be client-side mods only, but I do wonder if it could possibly effect who is crashing (i.e. people not running it crash, others using the optional mods don't crash etc...). After all we don't allow JSRS and other client-side mods to be used.

Also, it might not be the server. It could be the optional mods, and / or others, actually crashing the client machine running them. However, if that client crashes at the wrong time while they are doing something that somehow effects others players or the server (lets say during a healing animation or piloting a helicopter etc...), it could affect others and possibly the server, leading to further crashes.

Sorry typo. I took off both the optional mods first. It should have looked as below. I've edited that post now.

Modset #2
Optional
@st_stamina_bar
@tao_foldmap_a3