3 Commando Brigade

Yes the error is 100% linked to the armory.

My RPT's are pointing to different mods each crash.

interestingly the crash seems to be based on the second time you access to box i.e. after a couple of hours etc.

It's very stable - had 35 players in two different zones with over 200 Ai spawned !! even the odd Russian was seen !

It's just at that bloody VA box.  Hmmm

:Let's just hope it's the russians etc as that is imminently gonna get updated - hotfixed etc

if it's the map we'll have an issue


SJ

I saw 6 people crash out while nowhere near an Armoury box, all at the same time.
Sam crashed twice while speaking on a radio.

yes we're at slightly more dis-advantage than usual with this map.

I'm going to tone down the ai just a tad at the next revision.

Alpha experienced this last night. I think you were with us Parks. Two ai managed to suppress and engage us over 100m and even with 3 break contact moves we still really struggled to get traction or see where they were. All good players.

It took some bansai flanking move to get behind one before we could capitalise on our number @5 and beat them back !

Scary stuff

we really need someone that can decode and interpret  mdmp crash dump files ?

Any coders with the right tools ?

Yes spot on... we've proved they don't see through bushes, BUT they are much better at spotting you when they DO

Camo works Better for them.


Note based on our Jackals wheel out experience last night causing the vehicles to despawn I've Changed fn_vehRespawn.sqf from 60 second timeout to 3600 and 1200 - respectively.

No version change, but Apollo could you re-download your master copy ?


I've also done some more configuration on the ai for you.

Without the source code alongside, its like looking for a needle in the proverbial haystack.  Forget it ...

Real life is over-taking me, so I'm not going to have time to work on this now, probably until the new year.

What I suggest is that you fall back to the tried and tested approach of adding only mod 1 at a time, and only doing so after they have been tested and shown to have no significant rpt errors.

This is what has changed from Capraia (largely stable) to Bornholm (largely unstable):

ArmA 3 v1.36
Headless Client implementation
@Bornholm
@ASR_AI_RHS
@TPWCAS_A3
@RDS_CIVPACK
@RHS_AFRF3
@RHS_USF3
@3CB_BAF_Units
@3CB_BAF_Vehicles

This would be my procedure, allowing at least 1 day for each part and not moving on if ANY crashes are detected:

1. Revert to Bystrica mission, or another which we know was 100% stable, test it for a short while to make sure it is still stable; ie. recent ArmA update isn't causing significant ctd's in the baseline stable modset.

2. Then add @3CB_BAF_Units

3. Then add @3CB_BAF_Vehicles

4. Then I would re-jig Hammer & Sickle to work with completely vanilla units, no AI modifiers and CQB on the server or players (not HC), so we were only testing @Bornholm.

5. Next add HC to the CQB element.

6. Then add @RDS_CivPack

7. Then add @RHS_AFRF3

8. Then add @RHS_USF3

9. Then add @ASR_AI_RHS

10. Then add @TPWCAS_A3

Not much fun, and time consuming, but ultimately worth it for the stability.

Op tonight...
Multiple ctd's seen incl.:  Goodson, Klawc, Gav
FPS never above 20 regardless of settings (AA off, grass off, draw distance low etc), often around 10-15 (average 30-40 on other maps).
Shame because it would be an awesome map, but imho it's just not enjoyable to play on.

Yeah - I agree it seems to be bad for people.

I had a good frame rate throughout, but having said that I'm Zeus, so it's not a fair comparison

I wonder how optimisable it is.. probably not much we can do given the scale ?

All the guys getting bad FPS: Can you please go and check out the map in the editor and see what frames you get there?