The cause of it seems to have been a hardware issue. We haven't had any crashes since our server host replaced the hardware.
Thank you for your help. o7

Yay! Steam update 13:30 today 16th seems to have fixed the problem. Nice one!

Very unlikely to be fixed

Just right click Arma 3 in steam> properties > Betas > fill in Arma3Legacy206 where it says code.

I could check that in like 10 hours because it's currently midnight for me.

it crashes as soon as i get to the main menu

The difference between a dedicated server & client seems to be a missing 0, as in Dedicated server is 2.8.148892 & client 2.08.148892

yeah with a GM update it just disappeared

Hello thank you for reporting the bug.
Could you check if its solved in Profiling build v6 (latest)?

This seems like it would be pretty useful.

@BIS_fnc_KK Did you miss the comment?

Is there something missing from this ticket?

@CG-Delta is this the same bug? https://feedback.bistudio.com/T71386

sorry but for me this is chinese. Is more easy if I see photos!

@simao1234
Read this page.
https://community.bistudio.com/wiki/Arma_3:_Steam_Branches
The code for legacy 2.06 is: Arma3Legacy206

can you show me a print where i click to download legacy 2.06?

The narrow field of view (NFOV) and wide field of view (WFOV) lamps in the Titan interface don't switch either (both variants including "compact" with AP ammo). It can zoom, but the lamp remains on, on WFOV regardless.

Working as intended with Arma 3 2.08 and Global Mobilization 1.4. Tested on both 32 and 64 bit. Tested both Summer and Winter version of Weferlingen.

@Faly Great, looks like the ammo property has been updated with correct value since current public release

Last update of this config part: 2022-01-02 - All is OK.

If the mission display is not closed, then the eventhandler staying is indeed intentional.
Usually it does close between missions though, but "restart" specifically might indeed not.

Hello could you press this button and follow the steps
Then attach the .zip file that gets made when you finish to this ticket

Crap, didnt mean to delete that.
Sorry about that.
I'll ask KK to repost it

Thx dedmen, figured that out on sunday, the thing is that if using main branch on dedi server and local machine, server browser still says "different version" with red cross and looses connetion very soon. Hopefully main branch is updated to .149044 very soon. And btw: profiling branch still got t. he rifle firing in bursts bug until firing mode is switched.

I figured out the server steam update is not updating to 2.08.149044 but only updates to 2.08.148892

149044 is profiling branch. Many of the bugs were already fixed on there

Here are the 2 missions I used to test.

Thank you for the report, we'll look into it.

Thank you for the report, we'll look into it.

Thank you for the report, we'll look into it.

Add: it only happens on the Profiling branch

Also what is hosted dedicated server? There are 2 types of servers, player hosted, you can start it from main menu, in which case you are hosting server, or dedicated, which runs on its own on dedicated machine. Which is it?

could you upload your mission here?

The UserActions on CSLA_soldierBase needs onlyForPlayer = 1; or the radius to be smaller

il gioco si chiude in maniera anomala con il codice 0xc0000006 status_in_page_error come mai?

Add: It even happens when you had a weapon in your hands and put it in your backpack, it will start spawning tracers out of your head and keep spraying.

I can also relate to this problem since the 2.08 update.

Same here, red chain, loosing connection on mission start.
I figured out the server steam update is not updating to 2.08.149044 but only updates to 2.08.148892

On our dedicated server about 90% of missions that were all playable last week, are since the 2.08 update unplayable; as in after about 3 to 4 minutes into the mission all players lose connection at the same time. The dedicated server does not appear to have crashed & is still running, but players have to disconnect & re connect to try a different mission.