Page MenuHomeFeedback Tracker

Issue with Sound in 1st person on 64-Bit ARMA 3 stable - Lag - Stutter - USB 7.1 headset & AMD CPU
New, NormalPublic

Description

Following the release of the 64-bit update, everytime you go 1st person in a vehicle or in some buildings the game becomes unplayable with huge amounts of stutter and crazy noises to the point where it can hurt your ears!! Does not Crash the game.

This does not happen if you force run the 32-bit version using USB 7.1 surround sound
This does not happen on 64-bit if using the onboard 7.1 surround sound (3.5mm) jacks (motherboard)
This does not happen if you disable the 7.1 on the USB headsets and set them to stereo only

Updated drivers for both USB headsets with no luck
Used Both the USB3 Etron and USB2 connections no change

I can confirm they appear to work on a Intel rig i tried it on.

Under Sound playback devices it appears to be fixed at the following:
8 Channel, 16 bit. 48000Hz
Both Allow applications to take exclusive control of this device, and give exclusive mode applications priority are ticked.

Included are both the DX Diag with the previous Corsair headset and the latest with the Corsair VOID headset. you can also see the config for the 7.1 Realtek onboard sound.

This is a follow on from another thread on advice of Dwarden which can be found here: https://feedback.bistudio.com/T122385
Thank you

Details

Severity
Major
Resolution
Open
Reproducibility
Always
Operating System
Windows 10 x64
Operating System Version
1607 - Build 14393.969
Category
Sound
Steps To Reproduce

Using an AMD CPU
Using a 7.1 USB Surround Headset (Corsair Void RGB 7.1 Gaming headset)
Using 64-bit ARMA 3

  1. Go first person in any vehicle or aim down sights in vehicle 1st person
  2. 1st person enter buildings and notice lag/stutter with sound breakup
Additional Information

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

I think it might be time to get our money back from Bohemia.

Little to no communication on this issue, no details of even a time plan for a fix, not even true acknowledgement of there being a real problem.

Don't take your players for granted. We buy into the game for our enjoyment but crucially your employment.

@OneTwo9th @tspate I don't unfortunately have much more info about the progress, it is being worked on, no need to worry about that, but as much as it might appear as a simple issue, there seems to be more to it.

Anyway, a new update is being prepared which means new RC is out. Have anyone here, who's experiencing the issue, tried it? And if so, could you please provide some update on the current state in the RC version.

For those who do not now what is or how to get the RC branch, follow this LINK

@razazel I'll put it up right now and try it.

Hi, is this issue specifically targeted in this RC?

After following the link, I can't see any notes about issues that are addressed in it.

Sorry... I found the notes. Audio isn't mentioned though.

RC testing of Update 1.72 has started.
Steam branch access code: Arma3Update172RC
Arma 3: ~6 GB / Arma 3 Server ~1 GB (depends on Apex ownership)

Areas of focus (pseudo-changelog):
Added: Malden Free DLC
Added: Malden 2035 terrain
Added: Combat Patrol game mode
Added: Escape from Malden
Added: Escape from Tanoa*
Tweaked: Tanoa props are now available for all Arma 3 players

  • Restriction apply to those who don't own Arma 3 Apex.

@razazel Tyhe issue still persists. Although I will say It seems to be less consistant than before. I was able to fly the hummingbird but once I get around ~100ft above the ground the sound bug really starts to kick in. It seems like it may be related to reverb (or the reflection of sound off objects) specifically.

as I was. It hasnt changed at all

jimbobstan added a comment.EditedJun 12 2017, 10:16 AM

I agree with you tspate.

I think I've mentioned either in this post or another that I also feel that it's related to the reverb engine.

Reverb is one of the most computationally difficult things to do in audio, especially in a dynamic, multi source environment. It can't be preprocessed since the player can and will alter the environment almost immediately just by moving.

Then you throw in the head related transfer function, and binaural processing on these "virtual surround" headsets and get these type of problems.

I'm really unsure why this isn't a problem on other games and can only guess that the processing used in Arma for this has not been optimized and it bottlenecking somewhere... Perhaps the CPU. Why it doesn't occur (at least for me) in 32 bit also confounds the problem since more resources will be available to the game to process this stuff in 64bit.

My vote goes on the reverb processing too since in freefield (not inside a building, vehicle etc) the issue rarely if ever occurs.

Bohemia, I'm an audio and acoustic expert and can help if needed.

@jimbostan as i mention somewhere earlier Witcher 3 had exactly the same problem in its early stages. Same headsets same bug. There are more reports about the surroundheadsets with this bug than it might appear. Mostly it was kind of a bug in the code since it got fixed fast but that sone kind of a common problem.

Just tested the latest release of ARMA 3 ... appears now turning off the virtual surround no longer works!! Only by using the 32-bit Client is this game playable with a USB 7.1 Surround headset and AMD CPU.

Any update or ideas on when this may get looked into further???
Thanks!

Still having this issue, this is my updated .rpt file if it helps... vanilla game no mods.

jimbobstan added a comment.EditedJun 23 2017, 10:54 PM

I have a workaround that works completely for me and may help the developers understand the problem. It's not a solution, but makes the game playable, but first a bit of backstory:

BACKSTORY

On Windows 8.1, I *think* my Logitech G35 showed up as a stereo output device in the windows sound manager, playback devices. Then the 7.1 virtualization was entirely controlled by the Logitech Software. I certainly know that my Razer Kraken shows as a stereo headset in Windows 10 and uses a different type of 7.1 virtualization.

On Windows 10, the Logitech G35 headset shows as a 7.1 device (despite only being a stereo headset with 7.1 virutalization from Dolby). This means that programs/games that can output audio in 7.1 channels will try to do to the headset and this could create all sorts of problems since the headset isn't designed for this. I don't know if Arma 3 does output in full 7.1 since it's not visible in the audio settings in the game. However, it is the only game that I have that conflicts with the headset, so i think it might do - Perhaps the devs can answer this.

So I started thinking about this and how to make my headset show as a stereo device again and let the Dolby do it's thing, instead of the algorithm receiving 7.1 input, it will receive stereo and work fine. Good theory, now how did I do this?

MY WORKAROUND:

Firstly, I couldn't change anything about the logitech driver or in the settings of windows to stop it identifying as a 7.1 headset. So, I created a virtual stereo device, and from within that program I route the sound to my logitech headset and have my 7.1 virtualization enabled. Guess what? IT WORKS.

The program I used is called "Voicemeeter" and is completely free. It takes about 5 minute setup but works fine. Here are the steps I used:

  • Install Voicemeeter (find it on google as "VB-Audio VoiceMeeter")
  • Set Voicemeeter as the default device in Windows sound/Playback devices.

**Also make sure in the voicemeeter Input properties, advanced tab, that you have the same bit depth and sample rate as your headset uses or you'll hear some strange sounds like aliasing. I chose 16Bit 44100Hz as that is my headset maximum**

  • Open Voicemeeter
  • In the top right hand corner, there should be something flashing that says "choose output device" - Choose the USB headset that causes the problems. For me this was Logitech G35)
  • You don't need to change anything with your microphone.
  • Check it works in Arma 3.

NOTE/ Don't forget to change the audio output settings in your favourite voice chat client if you use one to output to Voicemeeter. Leave the input as the headset default microphone input because this isn't the thing causing you problems.

If anyone needs more help with this, just ask.

If im correct Arma uses the full setup of speaker configured in Windows. Since you change that to stereo you do the workaround some prople did before (but yours is compatible with all possible devices).
Workflow of a G35
Arma -> 7.1 sound over DirectX-> Dolby -> G35 (with Dolby encoding)
Workflow of your workaround
Arma -> 2.0 sound over DirectX -> Voicemeter -> G35

GodsGrampa removed a subscriber: GodsGrampa.
GodsGrampa added a subscriber: GodsGrampa.

that voicemeeter didnt work for me

unfortunately after installing the latest Logitech driver this doesn't work

I realized I was still using an old driver for the g35 from 2015 that was the result of some earlier test I did.

So, please disregard my voicemeeter post.

I am still having this issue, it has been quite a while.

Here's my stuff:

OS: Windows 10 Home

Processor: AMD FX(tm)-8300 Eight-Core Processor

NVIDIA GeForce GTX 1060 6GB

Logitech 933 Headset

Also have the stuttering fps error and is annoying as hell

Specs;

OS. Windows 7 64-bit 
CPU;  AMD FX4100
Headset;  Trust GXT 340 7.1 
Rammemory;  16gb ram 1333
GPU; AMD R7 370

wil try some of the thing previous post wrote but that does mean a bit of a downgrade cuz 24 bit, 48000hz is still the best. hoping it will be fixed soon.

I found that you can sometimes avoid this issue by opening the map when you're being transported. But this is somewhat of an inconvenience for many reasons. It makes the game at least, playable. It appears that most of us have AMD processors.. ? Please fix this issue.

I have yet to see a pilot to fly with his map open

stoney-dsp added a comment.EditedJul 5 2017, 6:27 PM

All possible solutions that i could find have been tested and didn't work.

Bohemia PLZ fix this cuz the game is UNPLAYABLE right now

@shiftrider92; driving & flying with the map open is almost impossible.

Also the turning sound of isn't helping much neither cuz of the framedrops and i can't even hear when i get shot

shiftrider92 added a comment.EditedJul 5 2017, 7:53 PM

@Scrable & @stoney-dsp allow me to clarify: I wasn't piloting, I was a passenger. It is the only way to get anywhere far on the game when this problem occurs. As we know, even if we aren't piloting/driving the vehicle, this issue still happens. This work-around, while inconvenient especially for those who even purchased the helicopter DLC (etc).. seems to work, sometimes. It will not fix the issue however.

Try opening the map as soon as you enter the vehicle, this seems to keep the game from killing your FPS when the problem occurs. I also use the feature F1 to lower the sound, if only to dampen the choppy sounds if they occur (which they always do if I do not open the map as soon as I enter the vehicle!). While this doesn't always work, it has more often times than not.

BTW its not only an AMD problem I have an i5 dual core and am having the same issue. Probably has something to do with sound drivers and the game as I have seen many Logitech headset people having this problem.

It a problem of slow singlecore cpus . Somewhere in the middle of this ticket someone uograded his system from a AmD FX to a ryzen boom problem gone.

Well... Nobody will upgrade his CPU(which would also require to buy a new Mainboard as well as new RAM) for just a game.
There are thousands of other games and well... This is taking far too long.

It a problem of slow singlecore cpus . Somewhere in the middle of this ticket someone uograded his system from a AmD FX to a ryzen boom problem gone.

Why do you keep saying "slow singlecore CPU"?

I have an fx8350. It is not singlecore and not that slow.

http://www.cpu-world.com/CPUs/Bulldozer/AMD-FX-Series%20FX-8350.html

I think TheMasterofBlubb is referring to my comment in the other ticket:

https://feedback.bistudio.com/T122385#1590839

So, the theory is that the problem is the weak performance (IPC) of each of the cores.
As you can see in that ticket, too, I also used to have the AMD Fx-8350, but not a Logitech Headset but one from Sennheiser.

Ahhh understood. I was just confused about the terminology used. 🙂

as mentioned in my original post, if I use a 7.1 surround speaker system connected to the onboard sound card setup for 7.1 it DOES NOT happen, for me it is something between the CPU and USB connections as I assume everyone here is using a USB type headset? This could be a CPU architecture issue or northbridge issue regarding bandwidth I assume.

however no other game running 7.1 has this issue currently which I own.

any news from the devs on a planned fix?

Not really. The problem is that with a USB headset you CPU is your Sound calculator. Low IPC and a huge load(from arma) cause that problem. If connected to the Soundcard what ever type the Sound Calculator is used there

jimbobstan added a comment.EditedJul 18 2017, 6:04 PM

@razazel Is there any more information on this problem?

Many people are suffering from this issue and cannot play the game properly. Unfortunately, despite this issue being game breaking for many, it's still not listed in "known issues"´here: https://dev.arma3.com/known-issues

This line under AUDIO, is not the same issue: "If you experience stuttering during scenes with a lot of sound effects after the 1.54 update, you can try configuring your Windows sound Default Format to 16 bit, 44100 Hz as a temporary work-around."

Please keep us up to date if possible.

Same issue for me, recently installed a Corsair VOID RGB Wireless 7.1 headset and immediately began having same issue. Game rev 1.72. Only occurs when in 1st person in vehicles.

Please, BI. Please.

I think TheMasterofBlubb has a point. It makes sense that a USB headset relies on CPU. Too bad nobody makes a soundcard for wireless headsets so the load could be transferred. Not that I'm aware of anyway.

For now, I just switch to my local sound card when I know I'm going to be using vehicles.

I think it may also be an AMD issue

Issue still exists

I tried multiple "fixes" from different forums. Right now, after completely deleting logitech's driver (I've been using G430), using 2-channel onboard sound card, issue still exists with 64-bit binary.

AMD-8320, radeon 280, asus m5a97 and windows 7

Still persists for me too, feel like this is getting ignored.

rosfeld604 added a comment.EditedAug 20 2017, 11:24 AM

I also have the issue as well, only solution so far is run the game in 32 bit. RIP 16GB Ram

This problem still persists on Update 1.76!

BI don't care pal.

BI don't care pal.

That isn't going to stop me from reporting it!

you can report all you want. After KK left, nobody will read it :(

BI don't care pal.

That isn't going to stop me from reporting it!

No of course not! Sorry I didn't mean to imply that you shouldn't! I've just stopped caring now since the game is unplayable.

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

One most important thing I realised was, it persists even with onboard sound card. I've even removed all logitech drivers, tried with onboard card and razer drivers, then I uninstalled razer and tried with normal drivers - all the time there was this issue.

Can confirm this issue is still present on FX machines.
My rig:
Fx 9370
16Gb G.Skill Trident X ram
120gb Samsung ssd
GTX 1080 G1

To combat the issue make sure you are using 32-bit client instead of 64-bit.

32 bit client has inferior performance as well as the 3FPS problem, which glitches the game out completely limits the framerate to 3FPS

latest crash report

Woulff added a comment.EditedOct 25 2017, 5:20 AM

Here is another video of the issues. I noticed when flying over water, the issue didn't occur. The video is long and you can probably skip the high altitude part. The last 5-10 minutes show most. Around the 12min area there is some interesting sound position issues.

At 17min there is some visible freezes and then the land vs water issue.

The frames per second are on the bottom right corner. Switch to 1080p to see the drops in FPS.

tgb added a subscriber: tgb.Nov 1 2017, 3:12 PM
kogs added a subscriber: kogs.Nov 2 2017, 9:34 PM

Will there be a fix soon?

I started seeing this issue after I started using a 7.1 headset, never happened with stereo. I thought it might be caused by some soundmods I had installed, namely JSRS and Enhanced Soundscape, but they have no effect. I also noticed severe audio artifacts and frame drops in towns, not quite as unplayable but definitely noticeable, probably something to do with the buildings and reverb. First person in a vehicle, especially going at a higher speed, consistently brings this problem. Switch to third person and instantly fixed. Does not occur in 32-bit.
System:
Windows 7 Home Premium 64-bit
FX-8320 CPU
16GB 1866 Memory
HD 7970 GPU
Patriot Viper V370 7.1 Headset

I have the same issue, crackling sounds and huge sound lags and it doesn't matter if i am in a vehicle or just walking around.
It appeared first around July and now it is even more worse. Reinstalled basicly my whole OS, drivers etc. still nothing.

Tried almost all workarounds, suggestions so far without any luck. The only fix is to use the 32-bit Version.

AMD FX-4100 (yeah its a bit crappy but i never had issues before and after the 64-bit launch - the issue came up around July for me)
Onboard Sound

OneTwo9th added a comment.EditedNov 22 2017, 9:18 AM

RECOMMENDED:
OS: Windows 7 / 8 / 10 (64bit)
Processor: Intel Core i5-4460 or AMD FX 4300 or better
Memory: 6 GB RAM
Graphics: NVIDIA GeForce GTX 660 / AMD Radeon HD 7800 Series with 2 GB > > > VRAM
DirectX®: 11
Hard Drive: 25 GB free space, SSD / Hybrid HDD / SSHD storage
Sound: DirectX®-compatible soundcard

AMD FX Processors are recomended system requirements... One more reason this should be fixed or the Recomended specs should be changed at once.

It hasn't been fixed since over a year now. This gamebreaking bug exists ever since the 64bit version was released.
So, my hopes for the devs actually doing something are quite low. They already have every bit of important information about the setups, as in, Logitech Headset with Surround Soundcard and FX Processor. Yet they do nothing.

Very disappointed in this dev, I guess with time everything turns into a steaming pile of shit.

Too bad, i can't possibly play with 32-bit its so bad - game deinstalled waiting for this update...

Balder added a subscriber: Balder.Dec 13 2017, 11:10 PM

PLEASE FIX, The game is almost unplayable at this state....

@mrpacman @Balder
Your hardware specs, please.

cliff696 added a subscriber: cliff696.EditedDec 19 2017, 11:04 AM

When you fix this problem?
I have steelseries siberia v2 3.5(mm) jacks headset and i have this bug
Win 10 Pro 64bit
Memory 16 Gb 1600 Mhz
amd fx-8120 4.5 Ghz
msi 970 gaming motherboard
asus radeon hd7850 GPU
SSD Samsung 850 Evo 250 Gb+HDD 2Tb
it's impossible to play comfortably on 32bit client with 3fps bug, and on 64bit client with 16bit 48000 Gz audio settings

Lenhador added a subscriber: Lenhador.EditedDec 28 2017, 7:10 PM

I found a work around for those who can't change the audio format due to the option being greyed out in the properties tab in Windows.

Download and install Voicemeeter Banana:
Voicemeeter Banana

  1. After installation reboot your PC. When initialized open Voicemeeter Banana.

http://prntscr.com/htgjzd

  1. Click on A1 to choose the output:

https://prnt.sc/htglhv

  1. Choose your corresponding audio device in the MME format.

http://prntscr.com/htgmbu

  1. Check if the sample was change right below Hardware Out info:

http://prntscr.com/htgns1

  1. Choose Voicemeeter aux input as default device in Windows.

This should solve the issue for now. Run the game with the app open. In my case the dafult format is 48000 Hz. However i can't change that under Windows 7 options. This app allowed me to reproduce 44100 Hz as shown in the print screen above. This solved the issue for me and now the stutttering is gone when driving and flying in first person. No stutter when firing from inside a building as well. I hope this solve the issue since BIS is making us waiting on a solution.

Cheers!

EDIT1: This actually works. I've been playing for a couple days now with no crackling sounds on 64bits version of the game. I'm using FX processor as well.

I am having this problem of lag and audio stuttering in vehicles in first-person, but my specs seem different from most other cases.

Windows 10 Pro 64-bit
Intel Core i7 950 3.07 GHz
12GB Ram
Nvidia 970 GTX 4GB
1TB HDD

My headset is a typical 3.5mm stereo headphones.
My sound device is an ASUS DX Xonar PCI-E sound card with 7.1 virtualization. If I set the audio to 8 channels there is lag, if I set to 2 channels the game is completely smooth, even if I still keep the virtual speaker and Dolby Headphone settings enabled. The problem seems to be based on ARMA not handling sound channels properly.

I included some pictures of the ASUS sound card settings and info, I hope this helps.

This is still a thing as of now, please fix this :(

Hi
same thing here too. The problem also occurs when you're switching to/from the map display ("M" key). The sound is getting clean and loud when displaying the map, but when you're going back to first-person view (in a cockpit) all's become choppy and huge FPS drop occurs.

it is like at some point, ARMA 3 try to apply some "interior" sound effect over something and break everything.

Windows 10 Pro 64-bit Version1709 build 16299.125
AMD 9590 950 4.7 GHz
16GB RAM
AMD Radeon 4GB
350 GB SSD disk
All drivers up-to-date

Corsair VOID RGB 7.1 (all latest drivers + firmware for both headset and CUE)

Not to point out the obvious, but the problem still stands. I know this is obviously a very complicated problem as this has taken over a year to try to solve but the least we could get is an update :/ Or at least advise us in whether or not we will have to play 32bit for the remainder of the game's lifetime into ARMA 4

Hey guys can you try the dev and RC build. I yesterday played with a friend and he was sure he had not the bug anymore

Hey guys can you try the dev and RC build. I yesterday played with a friend and he was sure he had not the bug anymore

I've tested dev build and the problem is still present, but less noticeable. I'd try the RC build but I forgot how to activate it haha

Use Arma3Update182RC as beta code in steam

The issue remains for me in both the RC 1.82.144547 and Dev 1.83.144562 builds.
7.1 USB wireless head set.

It actually seems worse. I was testing out the new LOAL missiles and had a drone positioned above the target area. When in a Rhino, switching to the drone, the game would come to a crawl. I still have the same issue with helicopters also. It is really bad when flying over land and buildings. Switching to on board sound card @ 5.1 works fine. 5.1 or 7.1 with USB or wireless head set becomes unplayable.

CNTObi added a subscriber: CNTObi.Apr 21 2018, 3:55 PM

This is still an issue for me. Can reproduce it every time with the Razer virtual surround. It does not seem to clash with the windows spatial surround emulation though.
x64 only.

I didn't have this issue for a time now, mainly because I deleted all drivers and went with windows provided ones. And today I've got G933 headset. Guess what - issue persists, 64 bits client hangs after any sounds are played.

Has gotten even worse now for me, using voicemeeter to try and reduce the effects but I get huge fps drops when flying over buildings or just being near buildings on the ground.

Can officially say the only permanant Solution I have found is upgrade of CPU and motherboard .... This is an issue with ARMA3 and Surround Sound using USB emulation with AMD FX Processors.

The exact same problem happens to me. I have an AMD FX-8320 processor. Please BIS solve this.

You know what? This has been going on since back in June. I've got other games to play that don't wreck my ear drums. I'll reinstall when I hear that this issue has been fixed. This game is actually pretty amazing, but I'm not dealing with this.