Had this exact issue twice and lost paid for items, just died at a normal exit aswell they owe me so many premium items due to bullshit issues
Recent Activity
Today
Update: Also tested LXC's and its the same issue.
I've tried to clear my favorites list as well.
This issue has been here since update 1.25
@Geez This has been fixed in the newest experimental update 1.3.0.102. It no longer drops FPS when ADS'ing in armoured vehicles.
Sounds _Engine_RPM_ are very important - they set the main audibility of the tank engine in space. At the moment from the tank during the movement comes only the sound of its turbine, they are quiet but the main problem is that their distribution occurs in the rear sphere of the tank and for the most part are additional SFX
This particular crash that has appeared after 1.27 is on our end and we are working on a fix
I haven't seen anything, I did see they posted 5 days ago on X, that they were "consolidating" servers due to less demand from previous launches.
Hi, so this is related to the BackendID?
Has there been any communication with BI about this issue? I haven't checked back on Expansion Discord, but last I read they were also thinking these are BI issues.
This is most probably because authentication with backend passes before client connect to the server and since both client have same Identity ID it will not allow second one to join.
You can try running with -noBackend CLI https://community.bistudio.com/wiki/Arma_Reforger:Startup_Parameters#noBackend
Additionally by using this method of being able to use only 1 slotai and adding the repeated respawn delay reduces the stuttering effect of spawning large amounts of AI when you crossover the area threshold.
Revision: 152708
Revision: 152707
Figured it out... The guy in the deer tower created this strange path. Normally i gave them a "Scout" Waypoint. I now changed it to regular "Defend" and the path is gone
Thank you, banned
Forced to run these scripts for pumpkins to grow normally. We are not the only ones suffering form this. Hopefully they can pitch in here shortly
Can you put on your own list “Stop using X-Ray” glitch 😉. Thank you for your time!
Hello Cpt.Sauna.
we have tested this on our end but we were unable to find any issues.
Regards,
Geez
Hello gabriel931314.
Please click on "show details and prepare report" and upload the generated archive to this ticket when the crash occurs.
Regards,
Geez
Thank you for the report.
This has been reported previously and it is scheduled for a fix.
Closing the ticket as it is a duplicate.
Regards,
Geez
Fixed in 1.3
Hello Rodrigo.
This is a known issue and it is scheduled for a fix.
Closing this ticket as it is a duplicate.
Regards,
Geez
I am having this issue as well since update. Invisible wall in the center of our watchtowers.
it is programmed in the engine to destroy second rotor if first is destroyed, I will look at config to see if it actually gonna make any difference
Yesterday
I’ve had this issue too.
fixed in future update
Please correct the error
I'll try to check in the new version
So here are some of my observations regarding this issue:
- For me it never happens when I just fresh started steam/dayz, found a server I want to play (that I knew could throw an error)
- However it can be quite often reproduced when I jump out of a game on a community server A and trying to reconnect to server B
- Restarting Steam fully resolves it (not just restarting DayZ). BTW those that do full PC restart - can you try to just get out of steam and go back?
- It feels almost like a timeout occurs while / when the game tries to resolve character state differences
- Retrying after a timeout often triggers another random error (most often a mod/add-ons mismatch error and its kinda clear that Dayz expects mods from thenew server I am joining while my client still points at previous server mod (I realized that by seeing which mods the game thinks I am missing)
- So the game incorrectly remembers the server’s mod setup, as if it kinda not flushing previous server stuff.
пожалуйста помогите решить эту проблему
Please pay attention to this problem!