SignorMagnifico

Any insight from the devs on this? Should I attach more track files?

Attaching my DCS.log, dxdiag, some screenshots, and a track file. FPS went from 80 down to 45/46 just by looking from right to left in the Chinook on the ground. DCS Performance.rar

Thank you for making this right! Although, this was an unnecessary roller coaster.

Yep. I feel the same way. I don’t see growing pains. I hear a death rattle.

I agree with you. I don’t think Ugra has the right to change their minds a year after the fact. The map was already approved like it was. Ugra, ED, and OnReTech knew about the overlap from DAY ONE. They don’t have the right to bully another third party. OnReTech should have run to ED right away. These disputes SHOULD go through ED and not between the third parties. I also don’t think OnReTech has the right to remove features customers already paid for. This is a violation of the agreement they had with paying customers who already bought the map. Imagine if Hellfires get removed from the Kiowa because another dev has a module that shoots Hellfires and doesn’t like it.

I’m starting to see the picture that it was Ugra who demanded OnReTech to remove parts of the Sinai map people already paid for. Sorry, Ugra, but you don’t just get to change your mind after a year. BOTH of these maps are great. Please get your heads out of the sand and listen to ED’s customers. This really is not the time for third parties to be fighting with each other.

Which third party demanded it?

NOT COOL to remove features after we already paid for the product. I hope this is just a bug or an oversight you all can fix.

I also experienced this issue. The gun firing sound on the Sabre sounds like the cannon on the Frogfoot instead of .50 cals. I think a sound file got replaced by mistake in this last patch.

On my end, I seem to have really low FPS once I get close to the ground at airfields. (Tested at Kandahar.) FPS randomly dips into the 20s-30s. Not always, though. Once I get above 500/1000ft, the problem goes away. RTX 3080Ti and i7-14700K. 96GB RAM. DxDiag.txt

Issue has been fixed for me after I rebound my Steam account to my DCS account, transferred the purchases, and redownloaded the modules in question. No issues after that.

I am also experiencing this problem. Why have my purchases been taken from me? I have owned these on Steam since February 2014. Pretty sure this qualifies as a "stopper issue" prior to releasing a patch.

I also experienced this issue.

When typing in coordinates manually using lat/long on the Jester menu, if I accidentally click lat/long again without typing any numbers after the cursor is visible, the game crashes immediately. Happens every time. Log attached. dcs.log dcs.log-20240601-070309.zip

Thank you, Heatblur, for setting the bar again when it comes to DCS modules.

Thanks.

Is this issue fixed in the upcoming patch?

No, I can’t be heard at all. Fails at the test and in-game comms.

Update: Tried changing around the settings again to see what is causing the issue. The microphone test is now working with the following settings without needing to use Nvidia Broadcast as the microphone audio source. I can use the microphone input directly from my sound card. To fix this, I had to lower the microphone sample rate to 48000Hz. I also cannot set headphones to be the same audio output as the main audio out on my sound card. DCS main audio out through my sound card works fine. The root cause of DCS not detecting my microphone appears to be that DCS cannot handle audio input exceeding 48000Hz. My sound card supports up to 32Bit 96Khz on the microphone input and audio output.

I had the same issue on my end with a PCIe sound card. Had to use RTX voice as a workaround, but if I do that, my frame rate tanks when using Shadowplay. I don't know why DCS Voice Chat has such a hard time with audio inputs when every other program I use, including SRS, works fine.

Found a workaround which is allowing the audio test to work. Inspired by this: 1) Enabled Nvidia Broadcast for both speakers and microphone. 2) Set main audio out to the sound card (Sound BlasterX AE-5) which plays through my headset. 3) Set headphones to Nvidia Broadcast speakers. (The output also happens to be my headset plugged into my Sound Blaster card.) 4) Set microphone to Nvidia Broadcast. (The input source is my headset microphone plugged into my Sound Blaster card.) Based on the solution to this problem, it seems DCS voice chat has two issues: 1) It does not support voice chat audio being played/mixed through the same speakers as the main game audio. 2) The game has issues detecting microphone audio from an external sound card. However, it's able to detect microphone audio passed through software like Nvidia broadcast. I'll have to see how well it works in practice on servers, but I can at least hear myself in the menu now. Update 3/16: Voice Chat works now as expected after applying the workaround.

My experience: The in-game interface is great. Having HOTAS controls work for the in-game VOIP radio is a cool idea. In-game server implementation makes it easy to enable. In practice, though, I have not yet been able to enjoy this feature because the game does not detect my microphone because I’m using a PCIe sound card, and it works fine with everything else. No fixes, yet, from the dev team. Seems like 87% of DCS players also experienced technical issues getting it to work according to the poll. Update 03/19: After finally figuring out a workaround, I was able to use in-game voice chat on multiplayer this weekend. It worked great. I especially like the line of sight modeling and integration with the cockpit as well as the overall sound. My only complaint is that the audio engine in DCS should do a better job of capturing microphone input and playing it on the same audio source as the game audio. I shouldn't have to use a workaround with Nvidia broadcast. I'd prefer to have everything mixed in my headset instead of needing to use two different audio sources. Also, it appears that DCS doesn't like detecting audio input exceeding 48kHz, and my sound card supports up to 96kHz.

@Flappie Any word on a fix for this?

Any word as to whether this is a confirmed bug or is being tracked? Looks like we have another thread opened for a similar issue. Not sure if we should merge these threads? Looks like most of the DCS community has not been able to get the integrated VOIP to work.

Me, too. It also looks like we have the same sound card. The mic test has not worked for me using my SoundBlaster card since VOIP was introduced in 2.9.https://forum.dcs.world/topic/335815-no-audio-dcs-crashing-at-audio-test/?do=findComment&comment=5385542