1.4.0.38
Fixed: Deployable radio was confused by players without a group

Hello, have you tried to just run one server at once? If not, can you try to do so?

In T190533#2820594, @Geez wrote:

Hello, do you still experience this issue on the current version? And if so, can you please show your Head tracking settings (Settings > Controllers > Head tracking)?
Thank you!

now the servers stopped appearing at all in the server browser,new logs show

Hello.
As mentioned in the previous ticket.
This is not going to be changed in Reforger and the current behaviour is as designed.
Regards,
Geez

In T191855#2820587, @Geez wrote:

Update:
The issue with camera being zoomed in when looking around the weapon while looking through the scope is by design.
It won't be changed in Reforger, therefore I am closing the ticket.

Should be resolved now

Hello, do you still experience this issue on the current version? And if so, can you please show your Head tracking settings (Settings > Controllers > Head tracking)?
Thank you!

Update:
The issue with camera being zoomed in when looking around the weapon while looking through the scope is by design.
It won't be changed in Reforger, therefore I am closing the ticket.

Hello Snake1984.
We have checked with the team and there is no issue with this. It works as designed. You need to select the navmesh for the file when placing new SCR_AIWorld_Arland.et.
Regards,
Geez

@lwing Interesting. If this intended behaviour, its a pretty big downturn in realism for reforger. Unfortunate

@stenny833 I have no input on the matter but have noticed one of the differences is that API will flame a vehicle in the same amount of rounds regardless of where you hit it on the body. Tracer requires rounds to hit a fuel tank object inside of the model.

here is another log from a few mins ago server crashed with

i did a grep search of all logs files for RplAuthBackend::OnFailure text and got
NETWORK (W): RplAuthBackend::OnFailure called (identity=0x0000003B, group=3, reason=10)
NETWORK (W): RplAuthBackend::OnFailure called (identity=0x0000001B, group=6, reason=0)
NETWORK (W): RplAuthBackend::OnFailure called (identity=0x00000000, group=1, reason=4)
what do they mean?

You are right, setting the quality of shadows to low resolve the issue, rather disappointing that this is happening when set to high quality.

Still a problem for stable version 1.4.0.31

Still a problem for stable version 1.4.0.31

Fixed in the latest versions...
You can close this ticket, thank you for your work.

Fixed in the latest stable versions...
You can close this ticket, thank you for your work.

Hello,
Can you please provide more info / details about the issue nr.2? As we cannot seem to produce the issue.
Regards,
Geez

Hello.
We have tested the reported issue thoroughly.

Fixed in 1.4.0.34

In T192304#2819932, @Geez wrote:

In T192304#2819697, @byNautiic wrote:

Hello @Geez
Is it correct that creating new tickets for the same issue will lead to it being looked at sooner?
As in this case
Regards

No, this is not correct.
It is up to our QA teams internal priorities. As to why this ticket has been addressed before the one you have posted I do not know. It is possible higher priority issues had to be dealt with back then and we apologise for any inconvenience.

Resolved for one of the future updates.
Regards,
Geez

In T192304#2819697, @byNautiic wrote:

Hello @Geez
Is it correct that creating new tickets for the same issue will lead to it being looked at sooner?
As in this case
Regards

Resolved for one of the upcoming updates.

Cannot reproduce this issue on our end.
Closing the ticket.

Cannot reproduce.

Hello.
Changing the quality of shadows makes such effect. Wont fix.
Regards,
Geez