![]() On Windows some/most settings are stored in the registry, but others are stored in a database file mumble.sqlite in %LOCALAPPDATA%\mumble\mumble.sqlite. The server specific shortcuts are stored in the database mumble.sqlite. (That requires some more thought about the UI, specifically adding shortcuts, at which point I stopped). I briefly started trying to list them separately to make it clear there are both of them, and that the second kind of are only displayed for the current connected to server. However, it will only show those server-specific shortcuts ( with a channel as the target) for the server you are currently connected to. When you go into the configuration and list your shortcut, it will always display global (=those not specific to a server) shortcuts. I don't know why.Īs I briefly mentioned, server-specific shortcuts are handled separately (which was very surprising to me as well). But no, it just doesn't work on Linux as it seems it should. Because of your report of success with a similar approach, this time I was very diligent and paid tedious attention to every detail, thinking that all of my prior attempts must have missed something. ![]() Incidentally, I have tried this approach before (several times) during the last couple of years, because it sure seems like it ought to work. I don't know why (those shortcuts were not even visible through the "Configure->Settings->Shortcuts" menus). None of the new shortcuts worked on the target computer afterward. I went to one of the development computers in my lab that already had all of the shortcuts working correctly with both of those servers, and I copied the entire "" section from that computer and pasted it over the corresponding "" section of a different computer that didn't have such a complete configuration yet. ![]() Right now I am using two murmur servers in support of the "Linux Air Combat" community (one for development, and one for public use). Nevertheless, your guidance to copy/paste the shortcuts section out of that file seemed interesting. For each Linux user, separate copies of "nf" are stored in a hidden folder named ".conf/Mumble". In Linux, all of the shortcuts are stored in a file named "nf". As I see it, "portable mode" as you describe it makes no sense in a Linux context, since Linux configuration is already much simpler than the "registry" concept used in Windows. I tried it as you described, but Linux is different. You could then copy&paste the shortcuts section of the ini. Not sure how regular storage is on Linux. On Windows this will make Mumble not use the registry but the ini. You can place a mumble.ini next to the mumble executable, which will make Mumble use it to store its settings (portable mode). This helps with the sim's frame rate, and the Mumble information is presented on the aircraft's cockpit panel as if it were an aircraft radio.) With those 26 shortcuts, I am able to transmit all Mumble-related activities to all players in a mission, eliminating the need for the Mumble "overlay" and/or Mumble's "pop-ups". Without those 26 shortcuts, Linux Air Combat cannot synchronize with Mumble-related player activities like switching channels, etc. However, most of them are not using Mumble very effectively because they are intimidated by the task of configuring 26 Mumble shortcuts. My new sim is named "Linux Air Combat" and people are beginning to download and test it among other online players. (Background: I have written an open-source flight simulator for Linux and it includes a very powerful interface with Mumble that relies upon creation of 26 Mumble shortcuts. Of course, a corresponding "import" facility would also be needed. I would like to see an enhancement that would allow me to "export" the elaborate set of Mumble "shortcuts" that I have been using so I can distribute that exported file to others for their use.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |