New anticheat broke all 3rd party app support?
Check this reddit thread for more info. Basically no popular recording, overlay, color management or other statistic measuring apps work in 2042 anymore. Please forward this to the team.
Forum Discussion
@SP0000kS is right. If you use your Focusrite for recording or the same I would not recommend it either. But if you just have your headphones on the Focusrite, I don't see a problem with that.
If i have to put 192 samples to 1024 on a professional soundcard to not have pop/crack/sound then totally crash the driver.
Assuming if i use different focusrite driver that make different sound problem but still at 192 buffer size.
As windows dont use buffersize in the same way there will be probably problem with other audio configuration.
If you have an interface its probably to plug instrument or XLR pro microphone and of course you try to lower the buffersize as much as possible as your cpu can handle it. So you need the manufacturer driver.
Since 3 days i play at 1024/48khz with the last focusrite driver even with discord and not pop/crack problem.
If an audio developper could read the thread it will probably take 10min for him to understand that it come from BF2042.
Do any of you also have a problem with mouse and keyboard input lag since the update? The game is literally unplayable since then. I've reinstalled it, deleted settings, exchanged the mouse and keyboard, and I'm still stuck with the problem.
I have tested a buffer size of 1024 tonight and played for a couple of hours with no issues, so can confirm this workaround... though my friends say I'M crackly sounding running my mic through the interface. They're just going to have to deal with it I guess for now, it's better than my entire audio being garbage...
I haven't fully tested yet, but I restarted the game in buffer size 512 and the menu audio wasn't broken, so I will attempt that one next to see if I can find a decent middle ground to work with... my guess is they'll take their sweet time finding and fixing this horrendous bug so...
Yes it works for me too.
@JD_W0LF wrote:I have tested a buffer size of 1024 tonight and played for a couple of hours with no issues, so can confirm this workaround... though my friends say I'M crackly sounding running my mic through the interface. They're just going to have to deal with it I guess for now, it's better than my entire audio being garbage...
I haven't fully tested yet, but I restarted the game in buffer size 512 and the menu audio wasn't broken, so I will attempt that one next to see if I can find a decent middle ground to work with... my guess is they'll take their sweet time finding and fixing this horrendous bug so...
Update to this: I skipped testing buffer size 512 because discord friends said my mic was still sounding bad... so I went to 256 buffer size tonight and played for about 2-3 hours with no audio issues from either ingoing or outgoing audio.
So it looks like at least Scarletts set to 256 buffer works for now. I will continue testing lower buffer until the problem happens and report which ones work for me and don't.
@JD_W0LF wrote:
@JD_W0LF wrote:I have tested a buffer size of 1024 tonight and played for a couple of hours with no issues, so can confirm this workaround... though my friends say I'M crackly sounding running my mic through the interface. They're just going to have to deal with it I guess for now, it's better than my entire audio being garbage...
I haven't fully tested yet, but I restarted the game in buffer size 512 and the menu audio wasn't broken, so I will attempt that one next to see if I can find a decent middle ground to work with... my guess is they'll take their sweet time finding and fixing this horrendous bug so...
Update to this: I skipped testing buffer size 512 because discord friends said my mic was still sounding bad... so I went to 256 buffer size tonight and played for about 2-3 hours with no audio issues from either ingoing or outgoing audio.
So it looks like at least Scarletts set to 256 buffer works for now. I will continue testing lower buffer until the problem happens and report which ones work for me and don't.
Another update to this: Tried 192 buffer and I thought it was going to work, as I tested 5 minutes one night and it was fine... didn't have time to play for a while, came back the other night and tried and 192 buffer did NOT work anymore. Same issue as default. Bumped it back up to 256 and was fine once again, so it looks like at least for ME 256 is my go-to buffer size. No issues with it still.
