Karaoke

Ksksjksz

Now with a video. Even worse, one group placed, another placed by half and then disappeared adding +10% instead of +20%, third group didn't appear at all. I don't know what's going on with this but at least bugged units should not forever lock away the AI limit.
https://www.youtube.com/watch?v=hhAWEEaCWGk

Not sure if Bohemia realizes that the community basically keeps this game alive... all official servers are full of cheaters, only new players that are unaware play it, simply cause they don't know that there is no admins handling cheater issues, BE of course is just a joke at this point.
I'm pretty sure all community owners here would appreciate some much deserved love back from the game devs, as simple as at least keeping us updated.

Yo hize lo mismo pero no permite la migración de servidor. Ni permite ingresar al mismo Server.

Welp......

Heck at least tell us something. Other then oh it’s number 1 priority.

And this Bohemia is why you’re losing so many players. Just roll it back to the old update. Let them play. Let us enjoy the game we love. When you get your mistake fixed. Then release it. Enough enough.

Can we get some kind of update from Bohemia? this is basically impacting all community servers...

Deerisle lan server. 26k entities, 50 mods, 4-5k fps before patch, 900-1800 fps after. Stuttering and hard on the eyes. Rollback?

And when a server is shown and i try joining it, it shows another error (0x0001000E)

Please fix it I was enjoying the game and can't even play no more

Same issue ps5 uk brought this game two days ago starting feel like this is waste of money

Did you ever figure this out?

.

Hi apologies for the delay.

.

Ayuda no me deja entrar ah ningún servidor soy de ps4

@dedmen ?? any idea if we can just have a rollback? remove the patch

roll back that update already.... dont think, just do please we beg..!!

going on 3 days to fix this now, when will you actually bite the bullet and just roll back?

@Geez Thank you for the prompt response and update. Do you have a time frame for 1.29 release date?

@Geez Can we just roll back the patch and let us play? why is it so hard to do a roll back? clearly the hotfix isnt working, so just remove it fix it then roll back and deploy update when its actually stable??

same here, this not fun and of course it is unintentional, but hopefully you can investigate and find this problem soon

It's borderline unplayable, requiring a disconnect every 15 minutes to fix the bug. Do we have any word on this?

@Geez maybe rollback patch better for all of us now? So many servers are damaged with patch...

Camera-like eye adaptation/auto exposure should be thrown away completely (and in all games). People forgot that photorealism not equal realism. In real life it does not matter where you look (down or up) in bright day except if there painfully bright light source like reflection from sun on snow or sun itself - and these are not so bad with sunglasses. There might be slightly dimmed area around light source but whole vision keeps kinda same "exposure". Take your smartphone and in dark room point it at computer display then at desk then again at display, notice that if you do same with your eyes it works completely different.

Can confirm this is still an issue as of 06/08 - it's not a game crashing bug but it is annoying (Latest patched windows 11/7950X3D/7900XTX - All drivers up to date etc).

*update* it started working again randomly on it's own literally mid game. no settings were changed during that time. had to be some bug within the game.

Additional workaround but awful lot of work is using random action in conjunction with Action AI/Add waypoint.

This is related to the ability of the framework to use the slotwaypoint.et when it is randomly selected by the layer. If I set random one on spawn children but only have one waypoint enabled in the layer it works. But if I have more than one waypoint enabled and random on spawn children it fails to work.

In T190516#2840598, @CashewSan wrote:

This is still a prevalent issue for me since the 1.3 update happening seemingly randomly. No errors, no crash log, just CPU being spiked to %100. Freezes my computer most of the time to the point of hard reset, sometimes it'll recover after a couple minutes. Would love for this to be looked further into or given some guidance on how to avoid it

CPU: Intel i9 9900K
OS: Windows 11 Pro x64
OS Build: 26100.4652

Turning "Controller freelook in aircraft" OFF solved my issue

Revert the old suspension

game crashing

Same problem

I Have tested now couble servers and they have same issue with heli and boat you cant fly or drive those also some stuttering or lag spikes.. heli have some 2-3 second delay when you turn this happends me everyday when test also boat have some delay when you drive. Hope so BI fixed those soon as possible. Thanks

Sorry forgot to add the layer from the scenario. This is the state at the beginning of the video.

Nothing I can share at the moment, but rest assured we are working on this with the highest priority.

@Geez any update?

Are we making headway on this? 2 days in and my server is all but dead due to this issue.

Hello again!

stopped our fps freezes

remove your zeds for now peeps

Please with all the respect in the world would it be possible to roll back the last update whilst you resolve this problem. This is decimating community servers of its player count thus affecting the moral/game overall. I'm sure I can speak for everyone on this as a quick work around for now.

We have all uninstalled and will be playing Tarkov for the rest of our gaming days - we are never going back to DayZ. Every official server is filled with obvious cheaters.

We have tested this on our end across various platforms but we could not produce the issue on our end.
Seems like your weapon on the screenshot is off coloured as well. Might be some sort of specific issue.
Regards,
Geez

Hello,
On community servers you should be able to manipulate the night brightness via lightingConfig server.cfg parameter.
0 for brighter night
1 for darker night
2 for Sakhal

Thank you for the report.
We have identified the issue and it has been resolved for one of the future updates.
Regards,
Geez

Resolved for 1.29 update.