Will be fixed once Stable branch is hotfixed

Should be fixed now in the Dev Branch

Hey guys, have you by any chance tried the latest RC build? The potencial fix mentioned in the SITREP is already there so, it might be worth a shot giving it a try and reporting back in case something is still broken :)

In T85673#1650457, @RueLight wrote:

thrown just 4 smoke grenades for cover... ehmm yes... ai had good laugh.

In T119284#1649281, @shukari wrote:

Is it pushed to development branch... i cant find something in the changelog (https://forums.bistudio.com/forums/topic/140837-development-branch-changelog/?do=findComment&comment=3241357)

In T119284#1649277, @supertruite wrote:

yes, random particle disappearing seems to be fixed!
Particles still disappear when getting close to them though (the bigger the particle, the farther the disappearing distance)
example:
https://www.youtube.com/watch?v=N_RI-5NlM4M
Should I make a new ticket for it or is it already worked on ?

Probably just missing in the changelog, will fix

So, progress was made, a fix has been prepared and should be available in tomorrow's [development] branch update, so please, try to take a look there and if you can, report back whether it was fixed or whether the fix is still a bit lacking :)

Fix is already in progress, unfortunately it did not make it into the latest hotfix, we will do our best to include it as soon as possible.

You might also try Profiling branch, it contains some crash fixes that did not made its way into a stable update or emerged afterwards and had to be fixed. You can use the profiling branch to play on the stable servers.

Thanks for the dumps. Could you please try to switch to the Development branch of the game and try to reproduce the issue with the Diagnostic Exe?

@Georg_Ravioli Fix is still in progress.

@Muzzleflash thanks for the heads up, I did miss that, will take a look into that

@Muzzleflash I tried the repro steps mentioned by Amontieri and it seem to work, Quad bike respawned after being deserted. Could you perhaps provide your testing setup so I can reproduce it?

Should be fixed with the release of 1.76 update, can you confirm?

Should be fixed, can you confirm?

Thank you for the confirmation :)

Sorry guys, unfortunately it's a very tricky bug and we are still struggling to fix it properly without breaking something else :(

Hi guys, anyone poked around the RC who can confirm it was fixed? :)

@Liveandletdie No ETA on the update itself, however, and RC is out now and it contains fix for this issue.

As mentioned on the Twitter we are looking into the issue together with BE developers, searching for a suitable solution. Unfortunately that is the only info I have for now, I'll try to keep this updated with the progress (once I know something).

The 1.74 update was merely a hotfix for a different critical issue, this issue should be fixed in the next proper update. It is a very complex issue that was not really easy to fix so unfortunately it took us long.

Thank you very much, we will look into that.

Fix is in progress, do not worry about that.

could you please tell me what exactly got deleted? I am a bit confused as we do not delete any tickets or comments.

@Afgfighter Old repro still valid? I am having trouble reproducing the issue, seems to work fine.

Closing, reported as fixed in T126044

Could you please try the repro provided by @SpyderBlack723 and tell me if its valid for you? If it is, there is perhaps only something I missed.

Thank you very much :)

@reschke Hello, sorry for the late reply.

thank you for the feedback.

thank you for your feedback.

thank you for the feedback.

thank you for your feedback.

thank you for your feedback.

thank you for your feedback.

Disabling Steam overlay and running through Steam might do the trick as well.

thank you for the feedback.

thank you for the feedback. Could you please also provide info about the specific area you need to enter for the game to crash?

thank you for your feedback.

thank you for your feedback.

Thanks for the feedback.

thank you for your feedback.

As you have already noticed, this issue should be fixed in the Dev branch, please let me know whether the fixed worked.