3 Commando Brigade

Status update:

- public server continues to give crashes with modset 8 and Alive v5.6
- TvT (no AI) ran fine last night with high player counts and no crashes (?)

Conclusion: maybe it's not all down to A3 bugs? Possibly @alive? One of the later mods? A script change?

So, for testing purposes we're reverting to the last known stable modset and mission which are:
Modset 4
Invade & Annex r9

This is now running on the Public Server.

Update your public Repo on PwS.

Modset 4
@asdg_jr
@cba_a3
@sthud_a3
@st_nametags
@task_force_radio
@trixie_britishweapons
@vts_weaponresting

Trying to progress this quickly - server was stable all yesterday according to the players online.

Re-added Chinook helicopter mod (to modset 5).
Slightly modified mission to add Chinook, no script additions or significant changes - mission version 9a, changelog below.

Update your Public Repo on PwS.

Modset 5
@asdg_jr
@cba_a3
@chinookpack [Added]
@sthud_a3
@st_nametags
@task_force_radio
@trixie_britishweapons
@vts_weaponresting


Mission r9a
- Ahoy Admin Script disabled (admin_uid.sqf)
- Added Chinook (@chinookpack)
- Removed free view camera option for unconscious player (BTC_camera_unc_type)
- Removed restriction on which classes can fly (can be re-enabled in parameters)
- Removed free view camera option for unconscious player (BTC_camera_unc_type)
- Removed map marker on injured player (BTC_injured_marker)
- Fixed TFAR error on load (#include in init.sqf)

Sorry to rain on your parade, but yesterday evening there was a note-worthy 'mass'-crash on the public (modset4, I&A9). We were getting the usual desync issues and then 5 people (including me) crashed simultaneously. We were in the AO with 6-ish people, not doing anything special. There were <10 people on the server, some of them random pubbies.

The rpt files haven't yet shown anything useful unfortunately, but we do need reports of crashes on here as soon as they occur.
I personally checked at least three times throughout the day yesterday and each time players told me it was running nicely, including a 4 hour stretch from 7 to 11pm 'ish.

There was one period of desync reported (Arf and others) leading to a mass disconnect of players (5-6), but NOT ArmA crashes. i.e. ArmA stayed up and they could rejoin the server.

Alexander, can you confirm that your game actually crashed ("ArmA has stopped responding", had to restart ArmA)? 

Thanks.

Thanks andvik.

@Apollo: Yes, I can confirm that (just like the others) I crashed with the "ArmA stopped responding" dialogue. 

PS: Sorry for not reporting sooner, I sort of rage-quit directly to bed after that crash

Thanks lads.

I'm not sure if it's good or bad news!

This was what we believed to be a stable modset/mission from before the 1.26/1.28 patches, where we can't see or remember any crashes being reported. Yet now we have them.
So on the one hand this might mean that the crashes are A3 bugs, but on the other hand it means we can't really progress until that is fixed.

As I'm out today can someone report on how the public server has been behaving today (Tuesday) please?

People playing on other groups vanilla (no mod) servers are also reporting BattleEye disconnects and client crashes to desktop, so we'll freeze the public server at it's current modset until Bohemia release a new stable patch.

Work can continue on  testing individual mods for rpt errors though.

Try putting this handy sticker on the back of the Hunter:



(but thanks for the heads-up!)

No, you are actually correct with the loading hunter bug, i always put it down to Arma being Arma