Additional screenshots taken from today which showcase more key spawns which are inaccessible.

Hi Geez. I can add a video if you need it. Could it be my own visual bug?

In T192505#2820826, @cflynn93 wrote:

I play on Xbox and to be honest, I can't say I've encountered this issue personally, but maybe I've not noticed yet. I've played on several deathmatch servers and not noticed any wild discrepancy in bullet placement.

@cflynn93 I can’t comment on Xbox or PC as I’m on PlayStation when it happens. Had it happen again just now with a longhorn. Bullet landed to the left. Done with sniping until it’s fixed.

I have a video clip of this happening if that will help

I haven't looked at it since the ship was added,
But the mapgroupproto should be adjusted as items do spawn in unreachable locations in the water.

https://feedback.bistudio.com/T191949

I play on Xbox and to be honest, I can't say I've encountered this issue personally, but maybe I've not noticed yet. I've played on several deathmatch servers and not noticed any wild discrepancy in bullet placement.

@Dadtylikez @cflynn93 Agreed. Couldn’t have said it better. Hoping they can correct it soon. I personally prefer to snipe, but I feel forced to just stash away my long range weapons for now and only do CQB until this is fixed, which sucks. But I don’t want to risk giving away my position and possibly losing a ~4 week character as a result of a missed snipe that’s out of my control.

I have a PS5 and have the same issue. I deleted the app. Reinstalled it. Deleted any saved progress and left my PS5 off for about 4 hours. It’s still giving me the same error code.

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

It's still happening in 1.28. Only this time the Heli Crash sounds occurs, and when arriving there within minutes only the smoke is present. No crashed heli, no zombies, no loot, just the smoke...
..

@Geez There are still some UI that have not been fixed yet!

I am having the same issue but then with Reason 4 and 6.

all bugs are here:
https://www.youtube.com/watch?v=wmQt5FsC3fU

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.

<3

Thank you.
Forwarded to the team.

Also just to inform.
For plastic bottles it is intended that you cannot boil cholera out of it. For the other three (pot, canteen and glass bottle) we have confirmed it is possible to remove cholera once they hit appropriate heat level.
Regards,
Geez

Should be resolved now

Half of this issue remains in the game as of 1.28. Running and sprinting does affect hydration loss - but heat level still does not. This makes overheating (yellow heat symbol) only cause an annoying gasp and animation without actually having any gameplay significance whatsoever. On a server running summer temperatures this downplays the significance of managing what clothes you use and how to move in the heat to not lose hydration too fast. This needs to be addressed.

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!

Hello Sgt.Pepper.
According to the devs it should be:
0 = Never obstruct (Always lift)
1 = Obstruct + Lift
2 = Always obstruct (Never lift)

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.

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Thank you for the report.
We have tested this on our end but we were unable to reproduce the issue.
Regards,
Geez

Hello, we have tested this thoroughly but we were unable to reproduce the described issue.
Regards,
Geez

Hello.
The crash dump points towards nvppex.dll file, indicating a problem with your GPU drivers. Please do a clean installation and check your OS for any corrupted installations/files. Also make sure your system is up to date.
Disabling HWAA in the game might resolve the issue but the root cause is somewhere on your system.
There is also a chance that if you are running Nvidia app instead of Ge-force experience that that is the cause of the problem.
Regards,
Geez

Hello Alphawolf8911.
We will require a .mdmp file from the occurrence as well.
Regards,
Geez

Hello Luckystrike!
Thanks a lot for the tip, yes, the problem was the switch in this submenu, my voice chats were muted, I turned it on a long time ago, because I always used the "Party" on the PS5 with my friends. It's good that we understood what was going on, now there is information on the Internet for those who will face the same problem with their forgetfulness :)

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

i did a grep search of all logs files for RplAuthBackend::OnFailure test 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?