This problem is beyond frustrating.

This issue Resolved in Hotfix 1.68. Thanks to all involved

In T122385#1591618, @aviatorboy1996 wrote:

In T122385#1591104, @revengeuk wrote:

Guys this is pretty important, if your having this issue Can you try running the game with the JEMalloc Allocator - 64-Bit (parameters in launcher) ????

Seems it is working for me using this Malloc!??? Can anyone else confirm ???
I also enabled the Large Page support! Might as well :o)

Thank you!!

I've tried it but but it didn't fix the issue sadly.

The crashes were seen with build v08.

Attached are the server config, mission and more crash reports, using a more recent performance/profiling binary build.

Since 1.68 the 'Use Default Action" can now be used on the same button as your primary weapon, to use the currently selected action. Fixing the problem that 1.66 introduced, where "Use Selected Action" would stop you from being able to fire your weapon, as it now brings up the action menu if currently hidden.

UPDATE
switched to 32 started it then switched back to 64 seems to be working now

In T122385#1591104, @revengeuk wrote:

Guys this is pretty important, if your having this issue Can you try running the game with the JEMalloc Allocator - 64-Bit (parameters in launcher) ????

Seems it is working for me using this Malloc!??? Can anyone else confirm ???
I also enabled the Large Page support! Might as well :o)

Thank you!!

didn't take long...crashed immediately upon entering server.

ok, nevermind...figured all that out. I'll try KOTH again and see if I experience a crash

KOTH crash...

https://1drv.ms/u/s!ArqJaPVNmXRHklqD-x3qgZUj-irl

Oops, i see answer of BIS dev : https://forums.bistudio.com/forums/topic/202500-dedicated-server-only-shows-info-in-launcher-with-14-mods-load-15-it-doesnt/
You can close this ticket.

I have the same issue, cannot play the game

OK Fixed on stable branch 1.68.141.112

They don't make electric power neither! You can endless add realism against FPS.
Destroying a wind generator should let the nearest town in the dark.

What I can tell is that there are still problems with this issue. The static AI substituting the player when disconnects are not longer present, but without SaMatra's fix there are problems when a player dismount a vehicle, disconnects or dies in the vehicle. I described what I found in a comment here: https://feedback.bistudio.com/T123940 Since the problems in disconnecting from vehicles (dismounting, dying in a vehicle) are fixed by SaMatra's addon it is possible that the issue described here is not completely repaired by the hotfix.

As far as I could see there are still problems with this module, when destroyed a vehicle respawns correctly, but when abandoned not. It will respawn only once if you use SaMatra's fix described in this topic https://forums.bistudio.com/forums/topic/202822-post-patch-update-player-disconnect/#comment-3164973 but the vehicle will not respawn at all if you don't use this fix, because the vehicle results still occupied when ppl dismount the vehicle, disconnect or dies (without Samatra's fix server side). So it seems this issue too https://feedback.bistudio.com/T123785 is not completely fixed by the hotfix. Tried in dedicated server.

In T124105#1591453, @Polako wrote:

In T124105#1591444, @BISWizard wrote:

It depends on your Steam settings, but by default it should. Check Downloads in Steam client.

You can check the game version in Arma 3 Launcher in Options menu: the version released today is 1.69.141143 (or high

I have no updates

I am also having this issue.

I need a Tech to look into this please

In T124105#1591444, @BISWizard wrote:

It depends on your Steam settings, but by default it should. Check Downloads in Steam client.

You can check the game version in Arma 3 Launcher in Options menu: the version released today is 1.69.141143 (or high

I have no updates

In T124105#1591142, @BISWizard wrote:

@Hikky: the update will be released tomorrow.

In T124105#1591065, @BISWizard wrote:

Hello,
sorry for the late response, we had to mediate over the logs. It seems that the workaround we indented for the issue is not powerful enough to beat the bug in the driver entirely. We've prepped a new and more powerful workaround that will be release to the development branch tomorrow.

In T124105#1591444, @BISWizard wrote:

It depends on your Steam settings, but by default it should. Check Downloads in Steam client.

You can check the game version in Arma 3 Launcher in Options menu: the version released today is 1.69.141143 (or higher).

It depends on your Steam settings, but by default it should. Check Downloads in Steam client.

In T124105#1591442, @BISWizard wrote:

Today's dev branch update should be on its way.

Today's dev branch update should be on its way.

No

I have found using the JEMalloc if you directly enter a vehicle it appears ok for me, but if I enter a building first it messes up again!?!

The same thing happens when the resolution is changed,
The bug is really annoying as arma is unplayable for me on the default fov.

Are you running any mods ?

In T123977#1590734, @BouncingHitman wrote:

Because it's almost been a year.

In T124105#1591107, @Polako wrote:

I have the same problem

In T124105#1591142, @BISWizard wrote:

@Hikky: the update will be released tomorrow.

In T124105#1591065, @BISWizard wrote:

Hello,
sorry for the late response, we had to mediate over the logs. It seems that the workaround we indented for the issue is not powerful enough to beat the bug in the driver entirely. We've prepped a new and more powerful workaround that will be release to the development branch tomorrow.

Since the last update, that zooming bug havent appeared once for me. Before it worked in KOTH as long as i didnt die, after respawn it appeared, after next respawn it was off again etc..... now its working fine to me.
Thx, great work! =)

Tried that resulz is not statisfing nor fixing it.
What i figured out is that in the presence(5m) of a smoke granade the bug is completly gone. As soon as the granade disappears the bug returns.

Upvote from here :)

I tried before and after Hotfix 1.68. No problem on this side. All files were validated.

@Hikky: the update will be released tomorrow.

Could you guys try changing the 64-bit memory allocator in preferences to the JEMalloc one and enable large page support ???

I have the same problem

Nice to see this was completely ignored and rushed into the main build.

Guys this is pretty important, if your having this issue Can you try running the game with the JEMalloc Allocator - 64-Bit (parameters in launcher) ????

It's good now, thanks

So, should I expect by May (the 1 year mark), the devs still have 0 idea what this could be? Not even a recommendation? I've posted video evidence above and full system specs.

In T124105#1591067, @BISWizard wrote:

Would it be possible for you to switch to the development branch and try it?

Thank you. Close Ticket
https://forums.bistudio.com/forums/topic/140837-development-branch-changelog/?do=findComment&comment=3170734

Would it be possible for you to switch to the development branch and try it?

In T124105#1591065, @BISWizard wrote:

Hello,
sorry for the late response, we had to mediate over the logs. It seems that the workaround we indented for the issue is not powerful enough to beat the bug in the driver entirely. We've prepped a new and more powerful workaround that will be release to the development branch tomorrow.

Hello,
sorry for the late response, we had to mediate over the logs. It seems that the workaround we indented for the issue is not powerful enough to beat the bug in the driver entirely. We've prepped a new and more powerful workaround that will be release to the development branch tomorrow.

question, does it still happen with 1.68.141112 (or newer) ?

So guys, can u say me some steps to follow for solve this problem?

It's working with the Profiling, haven't tested with stable version yet.

Hello,
your PC has a corrupted DLL library. Since update 1.68 the game defaults to 64-bit version that uses a different set of system libraries that 32-bit game, so that's why you didn't experienced the issue before.

this issue should be now resolved with the hotfix, can you confirm?

this issue should be now fixed with the latest hotfix. Can you confirm?

Seems I have the same error, but different version:

I decided to retry the key switch * switch control * and nothing happened

Some fixes were made with the latest update, could you please check it out and update the info or confirm the fix?