Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Are you sure files got updated on the server? Maybe some caching system still holds old file?
I downloaded it twice, once using `wget` just to be sure, and firmware files have the same checksums as ones downloaded on 20.06:
the swapping shortcuts work properly and ble connection works great
thanks mate
hi, i've been following the thread and i've just tried the new file, but unfortunately when i try to run ValveFirmwareUpdateApp_new.exe it reports the following files as missing:
-MSVCP140D.dll
-ucrtbased.dll
-VCRUNTIME140D.dll
i tried to just launch ble.bat, but now my pc just keeps asking me to try to connect again. tried to connect in both the bluetooth modes (steam key+Y and steam key+B). am i missing something?
There are two files in this that might not be intended - ValveFirmwareUpdateApp.bat (references a firmware image three levels above the folder and which isn't included in the zip) and ValveFirmwareUpdateApp_new.exe which isn't used by any of the batch files
First tried "ble.bat" and ran the update successfully. No wireless.
Then tried to revert with "prod.bat", which reported a successful update. Still no wireless.
Also tried connecting through USB, copying the firmware straight to the memory. No wireless.
An observation, if it might help smart people figuring this out:
"firmware.bin" on the memory gets set to the date 2009-02-06 09:10, even after having copied over "vcf_wired_controller_d0g.bin" with 2023-06-28 01:51. (same if I manually rename "vcf_wired_controller_d0g.bin" to "firmware.bin".
Damn, I thought my controller was rigged, since I bought it on Ebay a few days ago from a different owner. Glad I'm not the only one with that problem, I hope valve will keep supporting the steam controller, I really like it. You can connect your controller again by opening the old big picture. If you need further details hit me up.
How did you manage to get old big picture to work? I added -oldbigpicture to the Steam-shortcut(in windows 10). It doesn't seem to revert back to the old one. :(
Found how to enable it, got my controller back! Will experiment more now that there's a fix to restore it.
For people who are in the same situation: add "-vgui" to your Steam-shortcut and then in Steam, you press Alt+Enter to start the old big picture.
Austin thank you so much for this!
I don't have windows and tried forward the controller over USB to a QEMU emulated Windows instance. It got recognized, then I ran ble.bat, it ran successfully but didn't make any change on the controller. Should it print an error if it doesn't detect the device or can't complete the fw transfer?
In any case, do you have any idea how to do the same thing on unix (linux?)