Hello GorgorB.
Since you are running a lot of modded content, can you please confirm that this occurs in vanilla version with no mods as well? We have had reports of this happening in the past and were testing this on our end but we were unable to reproduce the issue.
Regards,
Geez

Resolved for one of the upcoming updates.

OK, it looks usable through the terrain processor.

Nex time please at least try run and do regression tests of all workbench app when touching his code. For Anim editor and Particle editor we not have alternative yet.

can we expect some bugfixes of anim editor when we see his code was touched and new bugs appear?

the problem still persists. I have a separate layer for small rocks -> create a shape -> give Fill (add a new objects) -> select rocks (e.g. stone1, stone2,stone3,stone5) -> density 30, average cluster size 2/+-1 rest default -> OK and with high probability it freezes immediately. I turn off and on the builder, make a new shape in the same place and there is a 50/50 chance that it freezes again.

Surprised @Sbeve linux didn't fix your hitching. Are you having minor stutters or massive hitches? My issue on windows was all the hitching and CPU maxing out which is a non problem for me on linux. Arma has always had little stutter problems especially on modded servers which I think most people have just accepted, the Massive 5- 10s hitches and crashes from hitches however need to be addressed. What proton were you running on bazzite? Could it be an issue with that version of proton?
The bazzite system I run with a 5800x3d and 9070xt handles it fine with GE_Proton 9-27

Well I finally got around to installing Linux (bazzite) on a SATA SSD to see if that would fix the problem. It doesn't, stuttering still exists on Linux. I guess it's just part of the game? I've seen my friend's game stuttering on an i5-9600k and rtx 3060 as well. I'm excited to play this game if/when the heavy stuttering is fixed.

When it comes to the crashes you've mentioned, the only real way to debug them is by having full access to the game's C++ engine codebase. Even with that access, unless you're highly familiar with the systems and structure of the code, identifying the root cause would still be extremely challenging.

Hi Geez,
Here is the .dze file along with a video. In the video I have placed loot under the dry sacks that represent where the object were deleted (haybales, tree, and bush) I have also turned on ESP to show the distance of the static obj in relation to the deleted object. Here is the coordinates of the test area on Chernarus.

This problem is still relevant, deleting armareforgertools from the registry editor helped me

No not using the Vanilla Roads Parts Mod. Some further info and location provided.

I for example, for my server, placed the sakhal bunker in Livonia bunker, and added gas to the power room + increased gasoline usage + made that if you "miss" with those 4 levers it will damage the glowplug.
It is the same but different, feels fresh and challenging

it can cause that afaik

Are you sure that you are not using the Vanilla Roads Parts Pack mod?

I hope they turn this into intended feature - when a player gets to inaccessible positon for infected - they will find another target.

And ofc. container is repainted using the addon prefix method, but aside from that - it is 1:1 vanilla scenario (p3d and proto)

NOTICE: I decided to test this, after some player mentioned to me that is is possible - I assume that the vanilla mapgroupproto indded may support such edge cases...

As of yet again the latest update, the freezing and crashing still persists. PLEASE FIX THIS ALREADY, how long are we supposed to wait?

Hello,
Can you please provide more details and possibly send your init.c or json or .dze project so we can check? As we cannot seem to reproduce the issue so far

Resolved for 1.29

I think I have found a fix. I Have an ASUS B650-E Motherboard, updated the "ArmouryCrate" and used that to update the BIOS as well as downloading ASUS "DriverHub" and that had a new driver for the chipset. Also set the BIOS into "Performance" mode also turned on the "GameMode" in advanced settings.. so far game works well again..

Hello,
Please contact BattlEye as they are responsible for ban distribution and administration https://www.battleye.com/contact/

Hello.
A fix will be released with 1.29 update, please let us know if it has improved the situation.
Regards,
Geez

Hello.
A fix will be released with 1.29 update, please let us know if it has improved the situation.
Regards,
Geez

Resolved for 1.29

Hello,
This will not be addressed at the moment as the issue is too trivial.
Regards,
Geez

Hello,
We have tested this thoroughly but we were unable to produce the issue on our end.
Regards,
Geez

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

Another fix coming with 1.29

sorry, i set the wrong tags, can someone delete it

If your Arma 3 isn't launching and throws a launcher error, first verify the integrity of game files via Steam. Next, try running Steam and Arma 3 as an administrator, and ensure you're opted out of any beta branches. If issues persist, reinstall BattlEye, update your graphics drivers and Visual C++ Redistributables, check for conflicting software, or delete the launcher cache in your AppData folder.

I have also had this problem. I have to shoot a non armored freshie 2 times up close with buck shot to knock them unconscious. Buckshot has become so useless since this previous update.

This is another clip of the issue I am talking about, even at point blank range you have to shoot people twice to knock them unconscious or kill them, even if the are lightly armored of unarmored.
https://youtu.be/BKnlKWTkrHk?si=9SLguxAbAI2mvlGT

:)

After researching this, I logged out, went to xbox settings, reset mac address, restarted xbox and re entered game. The PA systems then worked correctly.

Another example:

Note: I have completed game file repairs for Chernarus and reloaded the game files onto the server with no difference in the missing road surfaces. I have also had this issue confirmed with other players with different PC setups having the same issue.

This is still happening in 1.28.