In T192649#2822848, @dedmen wrote:

Well if the server crashes, then we need the crash report files from the server.
Of course you loose connection when the server crashed.

In T192598#2822812, @LouMontana wrote:

It is present in the Known Issues list:

The fact that this info is in the Known issues list is just an excuse. And a bad one at that. The known issues list wasn't even updated until a few hours after the update (at least the date of last update mention in the Known issues main page), which means this was an unintended result, aka, a screwup. If this was an intentional change (or even an issue that had been noticed before the update in internal tests) this information would have been in the changelog, not in the known issues. Please stop gaslighting your loyal players.

How can I assist?

It'll be a simple issue in the shaders. But the impact is probably too low to invest time into it

The backpacks in vehicles (not just quads) are generally hidding to prevent clipping issues.
For example sitting in a seat with back support, you wouldn't want your backpack glitching through it.

https://github.com/WolfCorps/gf_scripts/blob/master/addons/gf_scripts/functions/fn_p_makeUnitCurator.sqf
I use this script to give units zeus access.
It spawns ModuleCurator_F in script, same as you show it.

There is no way to reproduce this problem.

@Geez

But what if both muzzle and magazine have different soundTypeIndex, how do we choose?

It was a BattlEye outage

A proposed fix was pushed in Profiling branch v31
It will reappear in 2.20 v1

The 16000/18000/19000 hardcoded limits I assume you mean.
Yeah we could probably raise that a bit, it'll still be limited by video settings anyway, but you can change them in config then
particlesSoftLimit/particlesHardLimit in config somewhere, they are just currently clamped by hardcoded in-engine maximum

BattlEye as having outages. this looks like it was caused by it.

Send the RPT/crashreport then: https://feedback.bistudio.com/w/ft_a3_howto/gamecrash/

Well if the server crashes, then we need the crash report files from the server.
Of course you loose connection when the server crashed.

Should be removed now.

Removed! :)

It is present in the Known Issues list:

• Changing some settings with the mouse or controller will instantly jump between maximum and minimum values
  • Changing character speed
  • Changing stance
  • Changing leaning to left or right - on the controller only

Hello.
This is a design chance that was intentional.
Regards,
Geez

Bro you shouldn't even be able to hit anything AT ALL with the RPG at those ranges.

In T192233#2822285, @StevieB wrote:

I have had this problem for a while. Sometimes switching into windowed mode for a minute, then back to full screen fixes it for a bit.

Here's the latest console log:

Как решить задачу ???

Camo netting would be better if it could lay over the wall entirely

Certain areas could be intentionally cleared and surrounded by large bushes.

Also happening here, on a vanilla chernarus and a modded Livonia server.

Can we expect a fix on this?

Hello P4X.
Please go to documents > mygames > Arma Reforger Workbench > logs, and send us the latest one where it failed. Console.log file
Thank you.

Hello Veaxity.
We have been testing this on our end but so far we were unable to reproduce the issue.
Regards,
Geez

Hello FascinatedViewer.
Does this occur on vanilla with no mods as well?

@rennug88 same bug also applies to radio backpacks.

I think the amount of water and gasoline could just use the existing quantmin and quantmax in types.xml.

Revision: 152941

Just adding my notes to getting this bug resolved and increasing priority, it's broken a fundamental part of reforger's Infantry movement, engagement and ability to react and adapt to situations. Can no longer adjust quickly to peek through a small opening for monitoring/sniping, can no longer appropriately sneak into positions (moving faster and slowing gradually during the up tick in gun fire for example).