Project Reality Forums

PRLauncher.WPF.ViewModel.OptionsWindowViewModel.LoadPRMumbleKeybinds()

Usually this happens when you rebind a keybind to something that is a USB peripheral other than a standard windows keyboard or mouse. IN your case with a crash during a windows update, it's possible a driver, for your keyboard/mouse/joystick/whatever has been corrupted and windows fell back to a sxs copy of an earlier version of the driver, which might have just enough different code as to cause PRMumble to not properly interact with the driver.

SO where did you have the keybinds that are not working? extra mouse buttons?

Open PRMumble manually, (<bf2 install dir>/mods/pr/bin/PRMumble/PRMumble.exe), and reset your keybinds to default (Configure -> Settings -> Shortcuts -> Restore Defaults).

I thought of that too but it didn't work. I've verified it in the launcher options, in the mumble app itself, and in the game options... all keybindings are set to default.

But yeah, no local, squad or commander radio. I don't know the term for the "push to talk" thing that's bound to the "B" key by default. What is that called? That's working. But not many people use it.

I also noticed the game's blank screen when it first launches is much longer than before... maybe because it's trying to start PR mumble in the background and failing. But I'm not understanding what I'm seeing on other posts about mumble issues, talking about mumble being launched in the background, because even when it was working, that was never the case, so I'm assuming that's the way it worked in previous versions and not 1.1, which is the one I started with (I'm new).

I tried swapping out my new user profile for the old one, and now at least I'm getting the "mumble disconnected" icon in-game. But unlike originally, I can actually open up the mumble app and my mumble settings from the launcher. So now I think I have a better problem to solve.

I have of course changed my windows update settings... no wonder my game was lagging out so bad before the crash... it was installing updates without asking!

Well I managed to get mumble working by starting up and then quitting the mumble app... so it's all good! Now if I can just get good enough that I can actually co-operate with my squad... I keep getting booted for being an accidental lone wolf. And I still have to figure out how to move over to my new profile, because, yeah, Trekkie sucks as a name in PR.

Alright, lets try completely removing all user settings for PRMumble. Open up regedit (just type it into your start menu), and navigate to:

HKEY_CURRENT_USER\Software\Project Reality\PR Mumble

Delete the PR Mumble folder completely.

Now open up Windows Explorer, and delete the following folder as well:

%appdata%\Project Reality\Project Reality Mumble
(%appdata% is a shortcut to C:\Users\username\AppData\Roaming, should be able to just copy/paste it into your address bar)

Now open then close PRMumble. Should be good to go now.

Well after getting the options pane working, and with the standalone prmumble app able to start without crashing, I was able to reset all my mumble prefs to defaults the easy way, and any connection issues disappear when I alt+tab out of the game, start mumble, close it, and get back into the game.

So, about the windows updates. I let windows go ahead and apply the updates again, and that didn't cause any problems. Now in the interim, the game also updated itself to v1.1.1 from v1.1. So I got a game update two days after a Windows update, lots of troubleshooting going on in between, so anybody else with similar troubles: I can't say which combination of the things I've tried will work for you. I just know what really broke through was backtracking to an earlier system restore point. So... maybe that's one way to solve windows permissions problems... or maybe it is just about the files themselves, in my profiles folder.

So many details but I'm just happy to have the game working. Love PR.

It's strange because I never edited my keybindings. I guess that just happens to be the file that went bad.

Bug you probably already know about: I'm noticing when I try to keybind stuff in the options from the launcher, the pointer behavior is funny. The first time I click on a key to re-bind it, it works ok. The second time and so on, it acts like I double-clicked and binds the key to my mouse button zero. The options thing in mumble works fine.

Note to other noobs: So if anybody else is having trouble binding their keys for that reason, try doing it from the prmumble app itself. The settings do migrate back.

PR w/ mumble is so worth the troubleshooting.

Good to hear you got yourself up and running.

We're aware of that bug with the mouse, AncientMan is the the coder, he's got it on his to-do list.

Enjoy the game, if you see me online join my squad any time,

cheers,