kashif101 Posted April 8, 2016 Share Posted April 8, 2016 Hello. I have a very peculiar issue with my XBox One controller in Fallout New Vegas. I only want to play with the K+M, however, on the first launch, the game ran with the controller enabled. I disabled it from the options menu, and the mouse cursor appeared, however I can't move it around. The keyboard doesn't work either. I have to Alt-Tab and kill the process. Now when I launch the game, the mouse cursor is in the middle of the screen and I can't move it or do anything in the menu. If I open the .ini and change bdisable360controller to 0, the game launches with the controller active, and the only way I can play is with the controller. Unplugging the controller is a temporary fix, yet extremely inconvenient. I like to keep my controller connected 24/7. For some reason I cannot disable it properly in game. Any ideas? Thank you. Kind regards. Windows 10XBox One Controlleri5 4670kMSI GTX 770 Lightning16GB DDR3 RAM Link to comment Share on other sites More sharing options...
dubiousintent Posted April 9, 2016 Share Posted April 9, 2016 See my reply in this thread for some general suggestions. To which I would add that you need to disable the controller in both the "Fallout.INI" and "FalloutPrefs.INI" in your "C:\Users\<YourAccountName>\Documents\My Games\FalloutNV" folder as well as the "Fallout_default.INI" file in your game folder to be absolutely sure it's changed everywhere. Disconnect the controller first, make the edits, then start the game again before re-connecting the controller. You don't mention this, but I assume you installed using the Steam default location of "C:\Program Files"? If so, that can contribute to the problem as any changes beyond the initial installation actually are made to a "shadow file" associated with your account. These are not always recognized. The only true solution is to move your Steam game out of that folder tree. See the "Installing Games on Windows Vista+" article in my signature, which has a link to the official Steam procedure. -Dubious- Link to comment Share on other sites More sharing options...
kashif101 Posted April 10, 2016 Author Share Posted April 10, 2016 Hello Dubious Thank you for your reply. I should have mentioned in my original post that I have indeed changed the setting in all 3 .ini files, FalloutPrefs.ini being the only one that had the line of code when I first looked. Also, apologies for not mentioning it but no, all of my games are installed on my E: and F: drives, none in my Steam installation folder (which is C:). Unfortunately, I tried what you suggested with no success. After attempting your fix, I noticed that when I start the game with the controller disconnected, then reconnect it, it doesn't interfere and I can play with the M+K. However I have to disconnect it every time I launch. When I launch the game with the controller connected and the .ini files set to disable the controller, my mouse just sits in the middle of the screen and doesn't respond. Pulling the controller out lets it respond. I deleted the .ini files and let the game rebuild them (and verified where it failed to), and the issue persisted. So I assume it's not something I can fix by playing with the .ini, so I kept my old ones since they had many tweaks. Lastly, it's worth noting, these .ini's were built in Windows 7 and I had this controller and game in the same state. No problems. My documents folder is also on my E so when I formatted and installed Windows 10, my documents wasn't affected. So the ini files were all made on Windows 7. Thank you again for your reply. Kind regards. Link to comment Share on other sites More sharing options...
dubiousintent Posted April 11, 2016 Share Posted April 11, 2016 (edited) Thanks for the additional detail. Unfortunately I'm afraid the only other suggestions I have is to look into an updated or alternate driver for your controller that is more compatible with Win10, or possibly a "KVM switch" that will let you more conveniently disconnect the controller. It is not uncommon for hardware that works fine under one version of Windows to not under an updated version of the OS, due to changes in the base OS code (not the driver, which "translates" to the OS). This is actually fairly common with USB devices. I have a voice recorder that refuses to be recognized under Win7, but is just fine on the same hardware running in an XP Virtual Machine. Same driver is the "latest" in both cases. Go figure. Hmm. Running FNV in a Win7 Virtual Machine is another possibility I hadn't considered. -Dubious- Edited April 11, 2016 by dubiousintent Link to comment Share on other sites More sharing options...
Recommended Posts