Symptom: Xbox One controller connects initially to the wireless adapter, but after turning off or disconnecting they will not reconnect. Requires a reboot to allow controller(s) to reconnect.
1. Close Steam until the controller is connected, then restart Steam (if desired.) This was my and the majority of the people with the issue’s solution – See Gabriel Barsali’s post on the 4th page of Xbox One Wireless controller keeps disconnecting.
2. If you have the newer (Xbox One S and later with Bluetooth) controllers, try removing the Bluetooth Xbox Controller adapter from the Bluetooth & other devices window in Settings/Devices. If you disable Bluetooth (or remove the Bluetooth dongle) before removing the Bluetooth Xbox Controller Adapter it will appear “grayed out” in the Bluetooth & other devices window; you can’t delete it without Bluetooth on. (Of course.) This was not my issue, but is a potential solution listed by others.
3. Some feel uninstalling GeForce Experience is required. I have GeForce Experience running and this did not cause a conflict for me. It was definitely a conflict with Steam and the new Steam capability to manage non-Steam controllers.
As a 40+ year Buffalo Bills’ fan, I’m not unfamiliar with having the season be effectively over by December. I’m also numb to losing playoff chances to the Steelers late in the season (damn you Willie Parker.) But this…this was both different and unfortunately too much the same.
It’s one thing to lose because your favorite team is just worse, but trying. It’s another entirely to see that team clearly playing in a fog, like they just can’t or won’t try to win. That’s how it looked on Sunday. The only time I enjoyed myself was listening to the obscenely loud “BONNNNGGG” as Carpenter’s extra point caromed off the left goal post in a perfect example of the Bills’ 2016 season. It was a perverse enjoyable moment, because I gave up on this game about 90 seconds later than the Bills team already had, and I just had to laugh. Or poke my eyes out, and I still had to go to work the next day. And actually perform.
I usually mark my posts with the category/categories they fall under. Normally for these posts that means NFL and Buffalo Bills. It definitely was a Bills game, but I’m not sure both teams on Sunday deserved to be labeled as NFL.
Suffice to say I’m not uploading this video, unless someone absolutely begs me to. And they’re not a Steelers’ fan.
“They were custom made with Cleveland’s skyline on them. … I believe in my team. I believe in my city. And it’s cool. [They’re] cool shoes and I believe. I believe in my team. I believe in what we have, the glory is God’s. We’re just trying to do our thing.”
Update 2: 18 June 2017. Added quotation marks around the command in the batch file to allow for any spaces.
Update 1: 20 NOV 2016: Added a tweak to the batch file before you make it an executable to add some compatibility with Steam and nVidia streaming.
Background: I use the Steam Link to remotely play games on my family room TV. It’s basically a glorified remote desktop/streaming device.
Wouldn’t it be great if it could play Plex remotely so I could watch movies, TV, etc? In order to do this, you have to launch the application you want to view from within Steam. Easy enough for a “traditional” x86 app (i.e. one that is the type “something.exe”) but more difficult to launch a Windows Store application. As anyone who has tried knows, they are not only hidden, but don’t launch with an executable file.
Attempt 1: I tried launching using the shortcut to the Plex app – which sort of worked.
If you want to get a shortcut to any application, Windows Store or traditional, the best way I’ve found is to open the hidden “Applications” folder and create/drag a shortcut. You can open this hidden folder by going to “Run” (shortcut: Windows key + R) and type shell:AppsFolder then hit OK (or press enter.)
I created a shortcut to the Plex app, moved it to my D: drive, and used that shortcut in Steam as a non-Steam app to launch the Plex App. Problem was, although it would launch, it would always have an error box behind it.
Attempt 2 – Et voila!: A bit more complicated, but works very well. Basically you create a batch file that runs the shortcut, and turn the batch file into an executable file.
When you add a system to RocketLauncher you have to choose the default emulator – but what if RocketLauncher doesn’t list the emulator you want to use? Note: this is not how to add a new emulator/system if the emulator was not previously added. That has been covered on the RocketLauncher page here.
As you can see above, my System names (left column) don’t all correspond with “traditional” RocketLauncher names. In this case it’s because they were imported from LaunchBox. You can see that rather than being called “MAME”, the name (circled in green in the left side of the screenshot) is “Arcade”. While that is because it was imported from LaunchBox, it’s a more descriptive name for the non-initiated. Not that someone would be messing with RocketLauncher if they didn’t know what MAME was, but anyway.
sega_101.bin (md5 hash is: 85ec9ca47d8f6807718151cbcca8b964)
mpr-17933.bin (md5 hash is: 3240872c70984b6cbfda1586cab68dbe)
Place them in the appropriate folder under RetroArch
Typically this is the RetroArch/system folder
You can place them where ever if you use per-core configs (I use RetroArch/system/mednafen_saturn_bios)
If you just use one config file (i.e. everything is saved to RetroArch.cfg) then place all BIOS files for all emulators in the same folder (again, typically RetroArch/system folder.)
You will have to set the BIOS location in RetroArch
Open RetroArch and enter the Directory location
It is in the second column – “Settings”; the one with the gears for the icon
Near the bottom of that column is the Directory section
The first directory option under the Directory section is System/BIOS Dir
Set the directory to wherever you saved the two BIOS files in step 2.
Save the RetroArch config.
If you are using per-core configs MAKE SURE YOU’VE LOADED THE Mednafen Saturn config file first! Don’t overwrite the default RetroArch config file with a new default BIOS directory location – unless you’re going to put ALL emulator BIOSes in that directory (see 2.C. above.)
Using a zipped/compressed ROM in emulator through LaunchBox.
Allows you to save hard drive space, but does take a little longer to launch each game (about 20 seconds per 500MB depending on CPU and hard drive speed.)
You must have the setting checked to “Extract ROM archives before running” in the emulator setting inside Launchbox.
Example: Tools, Manage emulators, Demul (or whichever emulator) then Edit. Bottom right corner is a checkbox for “Extract ROM archives before running”. In this image it is NOT checked, but you’ll need to check it and click the OK button for it to work.
The audio is a little choppy in the game start…this is due to the slower laptop I was editing on and not indicative of the game play.