Same issue here with ARMA 3 Epoch mod, which defines a number of custom radio channels

In T178800#2561736, @Geez wrote:

In T178800#2561734, @Gobs wrote:

I believe OP is refering to server side FPS / tick rate being limited by this function, not the client side FPS. Yes, client side may be capped to 60 FPS but server side requires much, much higher FPS / tick rate, in the thousands (minimum) or server operation is severely throttled and as OP suggests highly unstable. That performance of Nitrado hosted DayZ servers is highly unstable is beyond dispute. Please look into this further.

No, we are talking about server FPS as well. Anything above 100 server FPS should have pure placebo effect and will unnecessarily exhaust CPU.

Also our wiki does not seem to mention anything about 1000fps? https://community.bistudio.com/wiki/DayZ:Server_Configuration

All is working again with signature verification on. Thanks very much for the fix here

Great. Appreciate that! :)

For example in the uniforms that exhibit this behaviour, the hithands hit point position in the array is matched to the head_hit hit selection value... in all the other uniforms it is matched to the hands hit selection

It is the inconsistency in the *ordering of the hit selection array*. I do not know whether this has an adverse affect which is why I asked for confirmation of whether it is actually an issue.

Note that all vanilla ARMA 3 ghillies have the same issue. Tested in the Arsenal as well now

Should be DayZ NJ 2-13 (108.61.129.68:2302)