When in an indoor space or vehicle in first person the game audio will begin to heavily distort and turn to a broken "white noise" whilst also decreasing the game FPS to unplayable levels and/or freezing it completely. I believe the issue may have to do with 7.1 surround sound headset software due to the fact that anywhere I've looked, others who have had the issue have been using such headsets, more often than not they are using Logitech 7.1 surround sound headsets but i have seen a post in which a different brand is used. All affected headsets seem to be specifically USB headsets.
- Operating System
- Windows 10 x64
- Operating System Version
- Windows 10 Home
- Game Freezes
Using a 7.1 surround sound USB headset spawn in game and step into any indoor building or vehicle, (the glitch is most prominent in vehicles) switch to first person mode if not already, the glitch should become obvious rather quickly.
It seems even if multiple people have the same system specs, the glitch affects those using 7.1 surround sound USB headsets only.
Apologies for the salt but communication is important.
What difference is there regarding the audio stack on 32 and 64 bit in Arma? Is there some conflict between the game and Dolby virtual surround? Can it be reproduced in BI because that would be a good start?
Also, does anyone have this problem on anything pre-windows 10?
This is the only game that i experience this problem on, although I acknowledge that not all games I play will be 64 bit, but some are like Elite Dangerous.
Anyway, thanks for the reply.
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:
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?
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
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.
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.
Can confirm the voicemeter suggestion works for me as well with an Logitech G35. Bistudio please fix this already!!! It has been an on going issue for a long time. There is no excuse for not fixing bugs when someone paid $60 for the game. Pair this bug with my 20 FPS using higher than recommended specs and at this rate I'll be amazed if I, let alone anyone else with the issue, continues to buy your products.