I think it's likely a permissions issue, but I haven't really bothered with trying to figure it out. However, it does mean my overlay doesn't always work, even if I start Mumble first. But since I had Mumble start as administrator, I haven't had this problem. Since I tend to get WoW crashes in the middle of raids, it was quite annoying. I would have to quit Mumble and relaunch. Mumble would look like it was working after that, in that I could hear people, but they couldn't hear me. I did have problems if WoW would crash on me. I have to say, I love the automatic equalization! I like the overlay for WoW, though I don't need it. On Mumble, they rarely, if ever, hear the "damned birds" so they jumped to it as soon as they tried it. One of their tanks has birds, and they are VERY loud when he would talk on Vent. Most of one of our 10s raid groups adores it completely because of the background noise canceling. I think it may be a case of "It's different, I don't like it" or something. The second person hasn't given me any solid reasons why she dislikes it, but she does. I've not pushed the issue, but he's really being bitchy about not ever trying again. I haven't been able to talk to him about it because he refuses to try again or tell me anything about what happened. The 2 people who don't like it - the first one said that installing Mumble messed up his sound so badly that he had to revert to a restore of his OS, or maybe just reinstall all his audio drivers. We were using TypeFrag for Ventrilo hosting. We still have the old Vent server up and running, but with fewer seats. A solution is disabling the Mumble overlay (in Mumble, click on Configure → Settings, open the Overlay section, deselect Enable Overlay and click OK).My guild just moved from Vent to Mumble. If you're using Mumble and OpenRadar at the same time, you might notice that the OpenRadar screen flickers. FGCom-mumble: In addition to using plain mumble, you can also try the FGCom-mumble plugin, which provides realistic radio operation.To mute yourself, click the Mute button in the main toolbar.Note The new channel is temporary and will be deleted when the last person in it exits the channel. Input a name and (optionally) a description, then click OK. if you're acting as a controller), right click on the FlightGear channel and choose Add. To enter an existing channel, right click on it and choose Join Channel.When you are connected, Mumble will show a hierarchical list of channels on the right side of the main window. Select FlightGear ATC from the server list and click Connect.If it is in that folder, you'll need admin rights. On next startup of the launcher it will redownload the exes (if you don't swap them again) If your game's not in Program Files the below code will suffice. at the bottom of the window and input the following parameters, then click OK:įlightGear ATC (or another descriptive name of your choice) First start the launcher, when it's done, run the batch file and click play. If this is the first time you connect to the FlightGear Mumble server, click on Add New. Nevertheless, it's still the joystick button and typing semicolon on the keyboard has no effect. For example, one of my joystick buttons appears as semicolon. Note It may show up as nonsense but that is just a cosmetic issue. Open the settings dialog, go to the shortcuts tab and assign any button you like to the Push-to-Talk function. GlobalShortcutX: /dev/input/event7: Saitek Cyborg Evo Force You should see your input device listed, such as: If you are using a terminal, watch the output messages. Note: input-events is part of the input-utils package. Debianers might want to use # /sbin/usermod. Note: # usermod YOUR_LOGIN_HERE -aG input should do the trick, where YOUR_LOGIN_HERE should be obviously replaced with obvious. Tip input-events is a useful tool for troubleshooting. Consult your OS documentation for details. You might need to add yourself to the appropriate group (for example input) or configure your device manager to grant access. Make sure you have permission to access the input devices (typically called /dev/input/event*). Note: This is correct: add the section as stated above ignore the fact, that there is already a section.
0 Comments
Leave a Reply. |