![]() The positive thing I noted is that, after using this workaround, the problem does not come back after a match when Warthunder enters the hangar again. I have a good two dozen output devices to choose from in Warthunder but none that looks promising other than 'pulse audio' and 'default' which are probably the same thing and which do not work with this workaround. The downside of this procedure is that the in-game sound of Warthunder stops working as well. If I start mumble after having killed pulse audio I get Warthunder and Mumble seemingly working side-by-side, which is great. are open when killing pulse audio then this will not get the input levels back). I can get my microphone input levels back if I kill and restart the pulse audio process after loading the hangar in Warthunder, under the condition that there is no other program open that uses audio input/output (if youtube or mumble etc. I played around a bit with killing the pulse audio process. Perhaps one has to play at least one match? Launching mumble *just* after launching Warthunder does not work unfortunately. I shall investigate this further and see if this actually is a solid workaround or just a dead end. I launched mumble on a whim long after warthunder (after having played a couple of hours) and the input meter was responsive at that point but I didn't test whether mumble in fact worked as intended and whether the input might crash again at a later stage. The other day I found some evidence that the problem may be fixed by a workaround but I had no chance to investigate this further. Trying to switch interfaces (from Pulse Audio to ALSA for example) causes the mumble settings dialogue box to become unresponsive and it eventually has to be shut down. The input level is completely frozen, both in pavucontrol and in mumble. I had pavucontrol installed briefly to see whether that would give me any more options to diagnose or remedy the problem. Thank you very much for your swift reply. I am a beginner with the Linux OS so I have limited knowledge about the diagnostics capabilities I have on hand here. Switched to ALSA and OSS).Īny advice would be much appreciated. Switched input devices on mumble (Standard is Pulse. The only thing that seems to remedy this is to relog the Linux user or restarting the PC. The ingame voice chat also does not work. The issue: The very second the hangar finishes loading my sound input cuts out meaning I can no longer talk on mumble, team speak etc. ![]() The installation was done via the Gaijin launcher, no steam or proton involved here. I only recently moved to Linux (due to the end-of-life for Win7) so I can't if this is a new issue or would have also been there with one of the last major Warthunder versions. The background: I am running Linux MINT 19.3 Cinnamon with the 5.3.0-46-generic Kernel and I've been experiencing a weird problem with Warthunder ever since I installed Warthunder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |