75%

https://www.tiktok.com/@gordonyamsee/video/7476591970392001823

To be honest i do have a Mayflower Electronics ARC sound card which i haven't tested it with the game yet but i cba that much since such issues shouldn't exist in 2025

I recently swapped OS to Linux Mint, and bought a new sound card with full Linux support, the Fulla Schiit (yes, for real). Ever since, I haven't noticed any problems. People seem to be able to hear me always.

Alex any changes? I haven't hopped into the game ever since since i can't talk to anyone...

Since originally posting this bug I have upgraded my video card, and operating system, and can no longer replicate it.

I Have 32 Gb Of Ram, Well Over The Recommended For the Game- As Well As My Specs- And A 2tb Storage Dedicated to the Game, I Should Have Probably Mentioned Those Sorry-

Also you can also find the amount of ram sticks in task manager in the "memory" tab

Welp, only thing that will yield result is testing memory sticks.
However, running just one is suboptimal.

Update On that, I Don't have Any Extra Ram Sticks, But I Took it into a shop not to long ago, and they Looked at everything Said it was Fine and Sent it on it's merry Way Back To me.

I Didn't do the Ram And Don't Really Know How Exactly to take it out, I'll Watch a Video Though, Got it?

Hello,
Can you please try to produce this on completely vanilla non modded server?
Regards,
Geez

https://www.memtest86.com/ can also possibly detect issues, but there are cases where it does not find the issue.
The issue also could be in any other piece of your hardware

To obtain the DirectX Diagnostic Tool (DxDiag) report, open the Run dialog (Windows Key + R), type dxdiag, and press Enter. Then, click "Save All Information" and save the output as a text file, typically to your desktop.
Here's a more detailed breakdown:
Open the Run dialog: You can do this by pressing the Windows key and the R key simultaneously, or by searching for "Run" in the Windows search bar.
Type dxdiag: In the Run dialog box, type dxdiag and press Enter.
Run DirectX Diagnostic Tool: The DirectX Diagnostic Tool window will open.
Save the information: Click the "Save All Information" button. This will open a save dialog box.
Choose a location and save: Select a location on your computer (like your desktop) to save the file, and click "Save". The file will be saved as a text file (e.g., dxdiag.txt).
Exit the tool: Close the DirectX Diagnostic Tool.

Do You Know How I Can Do This? Also The Dxdiag files are like the logs and all such? Correct? If Not I Might Need to be Guided through this-

Working for me too! Thanks for the fix, devs.

Every time there's a new update I eagerly read the changelog to see if this one has been fixed.

I just got banned chillin on a pve dayz server and I was the only one there LOL

Fixed for me after a quick test.

Hello TheUnderJoker.
Is it possible one of your RAM sticks could be faulty and causing the issue? We believe this could be caused by hardware problem on your end.
Also dxdiag file would be useful, thank you!

Hello, if the crash was caused by spawning a modded vehicle, then the issue has to be resolved by the mod creator.
Regards,
Geez

Will also test this out today, big thank you to the team for the speed in resolution!

Yay thank you, I'll test it out today

Fixed today ☺ https://reforger.armaplatform.com/news/update-june-19-2025

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

In T191308#2797008, @HideoutKitty wrote:

Hello,
I suppose so since the description is really similar, what i can tell for sure is that it's been mentioned in the arma reforger discord here : https://discord.com/channels/105462288051380224/976155351999201390/1355521871096971417/color block jam level/105462288051380224/976155351999201390/1355521871096971417

All I know is that it's the same issue that's been causing all (modded) servers to force a restart since the update instead of simply loading a new Scenario.

Video of mod working for BM 21

:(

Suggestion: Put the main ticket link on the known issue line. It allows users to track an issues progress and hopefully help contribute (not just moan)

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

Sorry for the generated frustration, I was also surprised to deliver with this being broken. You did all the good steps and are not to blame, we were slower in updating Known Issues - that line WILL disappear soon™ from the page though!

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

As designed according to the dev team.
Regards,
Geez

Hello,
We cannot reproduce the issue on the latest version.
Regards,
Geez

In T192598#2823054, @LouMontana wrote:

gaslighting

yeah right, that's what we do!
so we are both editing the issues list and not admitting to having issues by not adding them to the Known Issues list. I guess we just can't win :-)
or, hear me out, the page was updated a couple of hours later because of not being synchronised with the data release… but that may just be an excuse again!

Additional comment:
Seems the randomization is broken as well on restore layer to default.
A test to randomly spawn 1 object it always spawns the same object when using restore layer.

Thank you.
These are being looked at.
Regards,
Geez

In T192598#2822812, @LouMontana wrote:

It is present in the Known Issues list:

The fact that this info is in the Known issues list is just an excuse. And a bad one at that. The known issues list wasn't even updated until a few hours after the update (at least the date of last update mention in the Known issues main page), which means this was an unintended result, aka, a screwup. If this was an intentional change (or even an issue that had been noticed before the update in internal tests) this information would have been in the changelog, not in the known issues. Please stop gaslighting your loyal players.

It is present in the Known Issues list:

• Changing some settings with the mouse or controller will instantly jump between maximum and minimum values
  • Changing character speed
  • Changing stance
  • Changing leaning to left or right - on the controller only

Bro you shouldn't even be able to hit anything AT ALL with the RPG at those ranges.

In T192233#2822285, @StevieB wrote:

I have had this problem for a while. Sometimes switching into windowed mode for a minute, then back to full screen fixes it for a bit.