Muddy Jets: PvE mission of the month for Sat 16 Sep '23

Couldn’t get comms working at all - very frustrating evening after it was all working so well in the pre-op flights on the miRage server.

Mic was shown as working as it should in Discord, yet nothing was being sent/heard. Rebooted n times and kept going to set up to check and every time the same - mic shown as working well, but nothing happening in the chat channel.

Then DCS World was freezing on starting (after a reboot - I’d joined the server successfully to start with but again, no comms) … and so it went on.

At least you guys had a good op so my apologies for being AWOL.

3 Likes

Judging from my practice attempts in pre-ops, though, I wouldn’t have been much use…

that was CCIP - this was auto this afternoon and I heard someone else complaining their CCRP shots were going long, too…

but at least I can hit 'em with my rockets. Well, who couldn’t!

I’ll keep practising for next time - maybe I’ll hit something :roll_eyes:

8 Likes

Sorry your PC didn’t cooperate, I was sure missing have a hornet flight lead or wingman. Keeping up with them Eagles sure makes the bug thirsty. :joy:

7 Likes

This is what Musapike is all about. I had to work but I know I would have had fun alongside @NEVO in the F-5. Thanks for sharing the experience guys!

4 Likes

This is the only way that I can get Discord reliably transmitting and receiving. In Windows sound settings, set my Oculus as both the playback and recording device. In Discord, do the same. Then have a Discord PTT button on my throttle programmed. If I let Discord decide which device is used for what, it ends in failure.

And our missions are mostly designed to be fun, which doesn’t mean that folks don’t get shot down once in a while. No one is keeping score. We make a very loose attempt at doing things correctly, but the emphasis is more on enthusiasm and comradery. The MUDSPIKE way.

6 Likes

I noticed you mentioned earlier that you have to keep a browser open to use Discord; are you using the browser client? You might download and install the discord client; once you’ve set it up and got the proper audio input/outputs it should remember those settings where the browser might not.

1 Like

I told you guys last night that the Mudhen was easy to refuel. Proof is rendering right now :stuck_out_tongue:
I’ll update this post once it’s on YT

Edit: video is live :saluting_face:

3 Likes

***sorry - long post warning for detailed explanation! :smiling_face:

I used to use the app, but don’t since their blatant disregard for their clients was revealed a few years back (laid bare by Malwarebytes) - I just don’t trust them any more and have found so much material on the 'net that confirms their security is a shambles and their attitude apathetic. When malware was found on their servers instead of taking the required action they simply told clients to switch off their AV progs when using Discord. Totally unacceptable. In the end, after months of denial, they gave in and cleaned the server.

That’s why I only use them in a portable browser - the same one I used to use for Facebook before I deleted my account there a couple of weeks ago, now I no longer need it. But I’ll never install anything from Discord again. I don’t even like using it in that browser - but as it’s so popular and used by communities like this one as well as many developers, I decided to do it that way.

Anyway, to get to last night - I went through my settings on Discord and the frustrating thing was that on the microphone test tab, it was showing my strentgh well into the green - and I could hear myself in the headset, so the mic was definitely getting through to Discord, it just wasn’t being sent to others in the group.
I could hear you all - I heard @chipwich telling Freak (for my benefit) that the SRS frequency was 243MHz (iirc).

As mentioned, I rebooted the PC a couple of times and did it all again, but nix damit. The weird thing being that earlier I was on miRage’s server and all was working fine.
I have a strong suspicion that Discord set a PTT of its own choosing when I was looking through the settings. I selected to use a PTT switch, but then cancelled it so that I could have a think about which controller I wanted to use for that. I now reckon it just set something as default - I’ll check later. Shame I didn’t think of that last night. Although Discord can be fairly simple when you know what you want and where it is, I think there’s far too much garbage in it for use as a simple gaming comms utility. It’s repeatedly pestering me about this function or that function that i just have zero interest in, but never know if they are required or not or if I should use them or if they make things easier - normally I just click the ‘X’ and say 'bye 'bye to any pop-ups!

One other point - sorry for the long post - is that when we were talking on Discord while flying earlier, i was using Index, but had switched to Quest 2 for the pre-mission stuff, with the intention of going to the pico 4 for the actual mission (so as to save the battery usage in the Pico - you can just swap headsets on the fly and stay in-game). That was why I’d wanted to use SRS for comms on the server - no hassle with switching input/output audio.

All might be a merry-go-round for me on occasion, but I don’t really mind, as I’d rather feel more secure and have a bit of a dance than use stuff I don’t trust and worry about possible consequences.

2 Likes

Yup - indeed, I found the culprit! Not only was PTT activated, but there was nothing set for it! According to the info, it wouldn’t have worked anyway, so saved me even more headaches in the end.

No idea why DCS was hanging on the splash screen, though - worked fine today.

**I do need to get the best way to start it, though, as it has done this before - I’ll see if i can find a thread where this was covered and I’ll ask there about things I’m unsure of :wink:

4 Likes

Voice activity was split between Discord and SRS channels due to the large number of players. ATC was done on SRS mission freq, we had our own channel on SRS with the Mirage flight, and Discord was used by the Strike Eagles and for a few general announcements?

At least 5 of us were on SRS and we would have happily taken you along without Discord. But you do need to join the DCS server for that! In fact, we kept checking the DCS server player list to see if you had come back yet.

Don’t let Discord stop you next time!

4 Likes

Tacview file from the server.

@schurem please forgive me for not scraping that MiG off of your six. I had a good solution on him twice, but good grief, had not armed weapons! That is also why I didn’t drop on my first pass. Thankfully, someone (you?) called it and I knew to make a second pass. I probably need a fence check more than anyone. The other Mudhens did a great job killing the other 3 MiGs and almost got the 4th.

2 Likes

Honestly I’d personally prefer to use SRS for all comms once we start flying and leave discord for admin stuff (like people announcing they have to leave etc.). The reason is I can control the volume in the jet so I know whether a transmission is from the package channel or my flight and change the volumes and channels depending upon what’s happening in the mission at the time.

But I know not everyone is as familiar with SRS as I am. I think what we ended up doing worked well - Discord essentially became the strike channel, the briefed SRS strike channel (243MHz) became the ATC frequency and Freak and I used Preset 1 in our jets (240MHz if memory serves) as our private flight channel.

5 Likes

Thanks for posting the tacview!

Thanks Freak - I know you were trying to help as I could hear you on Discord and I appreciate it.

In future I’ll stick to SRS - as long as we’re all singing from the same sheet and know what’s happening overall, that’s the main thing. I do have Discord installed on my old tablet, and I’ll see if I can use that just for monitoring.

2 Likes

The Discord/Chat/Comms issue pops up on every multiplayer game I play.

I find it best to use in-game chat or SRS when playing and save discord for pre-flight briefings and after-killed (“heavenly”?) chatting. Even Sea of Thieves on XBOX is best with chat. Using Discord we are unable to scream epithets at other pirates. To conclude: Discord sucks! But it is necessary for communicating outside a particular game.

5 Likes

How good/bad are dcs in built comms? And I’m gettkng SRS sorted for next sortie. Fo sho’!

1 Like

I read that in-sim comms are very unreliable. I looked into it before flying with @Freak and everything I found was not exactly complimentary about it, even from ED. Apparently they will try and do something about it, but who knows if and when.

1 Like

The good thing about SRS is you just set frequencies and volumes using the controls in the cockpit.

I have no idea whether that works with the built-in comms yet…

1 Like

Yes, SRS is so simple, even I can set it up. I need to take a gander at the manual, but does anyone know offhand if there is any way to use it outside of DCS? I’m guessing not. Regardless, I’m happy switching to SRS once the briefing is completed.

5 Likes

SRS works really really well, and the radio effects it adds to voices are awesome, adds another element of realism. That said, there’s a burden on the mission editor to make sure every aircraft has proper comms channel presets. It’s been every bit as reliable as discord for me, and +1 on having the volume knobs in the cockpit. Plus the ability to communicate on 2-3 channels at once is great.

2 Likes