I just had the exact same problem and after some trial and error I found out that Riva Tuner for MSI Afterburner caused the crashes for me on startup. It worked perfectly fine after I disabled Riva Tuner.

I have the exact problem. The strange thing is that I can log into other servers without a problem?

I was unaware of the crew collision boxes. https://forums.bohemia.net/forums/topic/143930-general-discussion-dev-branch/?do=findComment&comment=3277032

also while we are at the position of the crew. The commander of the MBT-Kuma is still clipping out of the turret near the turret ring:

well on RC is no different from dev branch in these regards

Its already live

Sorry about the late reply

In T127940#1670553, @TheMasterofBlubb wrote:

Is that still present in the RC?

Is that still present in the RC?

Still get the error when i have disabled HW acceleration

Yes

Thank you for the report. Could you please upload the mission with whhich you tested this here?

Thank you for the report, we are aware of the issue.

Fixed, should be in the next Dev branch.

Hello feldmarschel.
We have moved your character and it should not be stuck any more. In case there are any issues with the character still, please let us know under this ticket.
Regards,
Geez

This was tweaked relatively recenetly. This is more about the geometry of the vehicles than anything else, if the geometry doesn't allow it well it would be hard to explain it how it works when it shouldn't . Although I admit in my opinion that Zamak is a bit crazy and should be toned down.

By default a crew member inside a vehicle can only be killed if he (his model) is present inside the vehicle.
Its best to show it at this example for AWC 301:

Uploading a new Arma report with new dumps we might have a look at it if anything has changed. Also have you tried the Dev branch of our game if the issue happens even there?

Have you tried launching the launcher in safe mode and disabling the HW acceleration?

Could you please explain what you mean by hittable crew. Do you want to shoot at a crew member that is inside an armored vehicle and be able to kill him? Or are you saying that they are missing the turn out feature which would enable you to kill them? Because right now I am not sure what you mean.

Are there any updates on this issue? Hopefully this issue can be fixed for the next update.

Are there any updates on this issue? Would be great if it could be fixed for the next update.

Still odd this is open.

Update: I have since had to rebuild my pc due to water damage, I now have a new motherboard z370a, processor i7-8700k, and new ram 16gb trident z 3200mhz cl14. This hasn't mitigated the issue. I also tried unplugging all my joysticks and uninstalling all software but still the same crashes everytime. I did however get a suggestion from another user, running without msi afterburner seems to improve the chances of a successful launch however its still very hit and miss (1/4 or 5 tries). And the crashes happen or don't regardless of making any other changes such as joysticks unplugged or not i.e. With msi disabled - when it does run, it can run with the joysticks connected. Can I ask where in the rpt you found where it says the crash occurs - like detecting joysticks etc. As I've looked through the rpt file, but there's no mention of the cause, it just says the memory address code and all the mods that were loaded?

Hello Wulf,

This one is not at all about your arma game files. It has to do with how the new windows 10 Game app function is coded to help potatoe computers run better. Please go into your windows 10 settings and look for the xbox integration and turn everything off thats related to the xbox function on you windows 10. Turn off Game mode, turn off background applications that use the record video while playing function. This is the worst thing Microsoft could have done to the gaming industry. They really have no reason to snub into our gaming experience. True gamers will have the hardware to play.

I have update my drivers but still i get the error message

Thank you for the report. Yes, we are aware of the issue, we will have a look at it.

we are aware of the issue.

Thank you for the report. Please update your video drivers, and/or try different video hardware in the problem machine(s).

Thank you for the report, we will have a look at it.

Thank you for the report. Can you please upload your Arma report? Here is how to do it.

Maybe related. Would explain the MP aspect.

@Wulf Regarding the 2nd part of my report - I have attached a video which shows what I am trying to explain to you. When you did your testing was this with AI in the vehicles or actual players? From my own testing I believe collision issues are only happening in multiplayer.

@TheMasterofBlubb Nope, No mods at all

@Ben1295 are you using ace? I know the problem from there.

I will get this updated with a video some time in the next 24 hours @Wulf

I would say that this bug depends on the server fps. The lower they are the higher is the occurence of the bug

Is there any chance this'll be resolved in the Tanks DLC?

Is there any chance this'll be resolved in the Tanks DLC?

@Wulf In the editor, you can create a script, for example, there is a big fight between AI infantry and equipment.
Starting the mission, the mission will be done with some lag. At this point in time, you can reproduce how the bushes break the wheels of the car.
The script of the breakage of the bush lags behind, breaks the car and takes away the health of the character.
Here is the result on the video, as I have reproduced.
https://youtu.be/BuZY6zqF8uk
So it happens on servers where there are more than 10-15 players, a lot of AI, a lot of actions and events.

The Angara's lighta are a touch too small IMO, though the issue is corrected. Thanks

Corrected in build 470