Here: https://youtu.be/UfN5WK7OzU8?t=17m58s
At least it was doing that in 2014. I remember seeing it on the dev days conference, but had to search for it
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
Steam DualShock 4 support is now live
- Thread starter Enter the Dragon Punch
- Start date
Here: https://youtu.be/UfN5WK7OzU8?t=17m58s
At least it was doing that in 2014. I remember seeing it on the dev days conference, but had to search for it
Ceallach
Smells like fresh rosebuds
Nah. Neo Geo CD dpad is the best.
The best thing about this whole configuration thing is that you can do exactly that if you want.
Just thought I'd clarify/correct something I stated earlier:
What I meant to say is that no games need to have the API integrated to in order for the Steam controller to work for it. Games can integrate the API into their game, which is part of what the presentation was about. Although I'm not sure which or if any games have integrated the API currently.
http://www.gamasutra.com/blogs/LarsDoucet/20161012/283057/Steam_Dev_Days_Steam_Controller.php
Here is the presentation
Here is the presentation
Doesn't native support mean they have integrated the API?
https://www.reddit.com/r/SteamController/wiki/official-support
Yes. 15 minutes is the minimum and two hours the maximum.
Ninja Kn1ght
Member
This is great news. DS4 has replaced the 360 controller as my go to on PC, and while DS4Windows worked well last time I tried it, it'll be very nice to see Steam supporting it officially.
Infinite_Daremo
Member
Does that include the dongle for the Steam controller?
No, that's not Bluetooth.
somesayyea
Member
this is fantastic news...great job valve
Yes, it is.
Infinite_Daremo
Member
The Steam Controller also works with bluetooth, but the dongle itself isn't one. We can't use it to connect other bluetooth devices, for instance.
Candescence
Member
Well, the big difference is that the PS4 pad has been given far, far more functionality and can work with games that don't even support controllers period.
Coreda
Member
Everything I'd read from users prior to picking up a DS4 mentioned the lightbar consumes battery life considerably.
Just doing a quick search returned a top result from a GAF'er who had done some testing which confirms this.
Okay, what is the dongle, then?
Oh, I see. That sounds great.
larsiusprime
Member
See my presentation. (I'm Lars, one of the guys who presented this on stage with Valve).
Full Controller support is a specific status that has eligibility requirements defined in the Steam documentation, I have a slide in the presentation that directly lists the requirements for "Full controller support" as of the last version of the documentation. I'm not sure if Valve is enforcing those standards yet or not, but that's what the docs say.
It's another wireless protocol that only works with the Steam Controller and it's supposed to have lower latency than bluetooth. I don't know what protocol it actually is, though.
AcceptableGhost
Member
I have sent you a PM.
Microsoft isn't going to take away any lessons; UWP is supposed to restrict user control.
chrominance
Member
NOTE: now that one of the people who actually gave the talk is in this thread, I don't know if this post will be super useful, but maybe it'll still help clarify things? Or if Lars says this is totally wrong, I can just take it down.
I read through most of the Gamasutra talk (which was pretty interesting even for someone who doesn't develop games!), and I'm not 100% sure if I got this right. Also, I am not a game developer, in case the previous comment didn't make it clear. But here's what I think is going on in that talk.
There's two separate things being discussed: one is the integration of the Steamworks controller API, which sounds very new. That's an abstraction layer that lets you define actions in your game (and certain properties like whether it's an analog or digital action, and how the analog action should work for things like touchpads), and then leave the actual mapping to controls completely up to Steam. Most of the talk discusses the benefits of using the API, and implies that you could completely remove the controller/keyboard mapping screens in your game and let Steam handle all that on its own (assuming you're only targeting Steam).
The Dualshock 4 stuff is separate. Steam Controller remapping support will be extended to the Dualshock 4, with all its native controls (gyro/touchpad) mappable in the same way Steam Controller inputs are. For games that don't directly implement the controller API, which is most/all games on Steam right now, the Steam client is presumably doing some translation between the hardware controller and the game, either emulating Xinput/Directinput controllers or keyboard/mouse input. That support is now being extended to the Dualshock 4. Either way, not only does a game not need to care if the connected controller is a Steam Controller or a Dualshock 4 (and change things accordingly), it actually can't know because of the API abstraction. The only place where this might be confusing is how do you implement button icons in your game, but perhaps I missed a detail in the talk (button icons do get brought up, but only in the context of the Steam Controller actions specifically). Worst case scenario, you could just include multiple sets and let the player self-identify. A couple of games already do this; Rebel Galaxy is one example.
The benefits of API implementation seem to be largely that you don't have to make a control binding interface anymore if you don't want to (and don't need to sell your game outside of Steam), and that even if you don't want to tie yourself to Steamworks, you can abstract some of the input functionality and then polyfill the abstraction layer for the GOG/DRM-free/Uplay/Origin/etc. release. It would be interesting if it also meant for users that the actual action names showed up in the Steam Controller setup interface, i.e. instead of assigning "Dpad Up" or "X Button" to controller inputs, you could map "Jump" or "Open Weapon Wheel" because you could send the actual names of the actions through the API to the Steam Controller interface. But that's a guess; I don't actually know if that bit has been implemented.
I read through most of the Gamasutra talk (which was pretty interesting even for someone who doesn't develop games!), and I'm not 100% sure if I got this right. Also, I am not a game developer, in case the previous comment didn't make it clear. But here's what I think is going on in that talk.
There's two separate things being discussed: one is the integration of the Steamworks controller API, which sounds very new. That's an abstraction layer that lets you define actions in your game (and certain properties like whether it's an analog or digital action, and how the analog action should work for things like touchpads), and then leave the actual mapping to controls completely up to Steam. Most of the talk discusses the benefits of using the API, and implies that you could completely remove the controller/keyboard mapping screens in your game and let Steam handle all that on its own (assuming you're only targeting Steam).
The Dualshock 4 stuff is separate. Steam Controller remapping support will be extended to the Dualshock 4, with all its native controls (gyro/touchpad) mappable in the same way Steam Controller inputs are. For games that don't directly implement the controller API, which is most/all games on Steam right now, the Steam client is presumably doing some translation between the hardware controller and the game, either emulating Xinput/Directinput controllers or keyboard/mouse input. That support is now being extended to the Dualshock 4. Either way, not only does a game not need to care if the connected controller is a Steam Controller or a Dualshock 4 (and change things accordingly), it actually can't know because of the API abstraction. The only place where this might be confusing is how do you implement button icons in your game, but perhaps I missed a detail in the talk (button icons do get brought up, but only in the context of the Steam Controller actions specifically). Worst case scenario, you could just include multiple sets and let the player self-identify. A couple of games already do this; Rebel Galaxy is one example.
The benefits of API implementation seem to be largely that you don't have to make a control binding interface anymore if you don't want to (and don't need to sell your game outside of Steam), and that even if you don't want to tie yourself to Steamworks, you can abstract some of the input functionality and then polyfill the abstraction layer for the GOG/DRM-free/Uplay/Origin/etc. release. It would be interesting if it also meant for users that the actual action names showed up in the Steam Controller setup interface, i.e. instead of assigning "Dpad Up" or "X Button" to controller inputs, you could map "Jump" or "Open Weapon Wheel" because you could send the actual names of the actions through the API to the Steam Controller interface. But that's a guess; I don't actually know if that bit has been implemented.
I know who are, even saw your reddit posts.
Full and partial controller support used to mean this:
As of Big Picture launch I think
It's very odd for them to redefine what full support means. Most games would lose it then.
Okay, thanks.
larsiusprime
Member
@Sini: thanks for that! Sorry if I'm muddying the waters.
The text in my talk is taken directly from the Steam Controller SDK documentation. They have a list of requirements for "Full controller support" which presumably in this case means STEAM controller.
So maybe steam is going to add a third status which is "Full STEAM Controller support" as a separate status?
I'll ask a Valve contact to clarify the situation, as the image you've got there seems to be referring to what you were discussing earlier.
The text in my talk is taken directly from the Steam Controller SDK documentation. They have a list of requirements for "Full controller support" which presumably in this case means STEAM controller.
So maybe steam is going to add a third status which is "Full STEAM Controller support" as a separate status?
I'll ask a Valve contact to clarify the situation, as the image you've got there seems to be referring to what you were discussing earlier.
Thanks, that's exactly what I wanted to know.
I actually just found support article about this, so you don't even have to trust that image.
https://support.steampowered.com/kb_article.php?ref=5006-ASLN-3202#controller
I would also guess they'll actually add a new level of controller support instead of redefining existing ones.
larsiusprime
Member
Here's the specific stuff from the SDK, I think this is okay to share as it's basically what I put in the talk:
---------
The Steam Controller API is designed to allow you to easily enable full Steam controller support in your game. We define full support as the follows:
To ensure users have a good experience from the couch, we also recommend the following:
----------
I associated the "Full Controller support" badge with these requirements, but now I'll have to double check with Valve about that. They didn't correct me so I just assumed that's what it was. I'll post an update as soon as I know for sure.
---------
The Steam Controller API is designed to allow you to easily enable full Steam controller support in your game. We define full support as the follows:
- Your game uses the Steam Controller glyphs when showing in-game input prompts.
- The Controller Configuration screen in Steam uses in-game actions that the player performs in your game, instead of keys or buttons.
- You've published an Official configuration for the controller.
- Your game doesn't restrict the user's ability to customize their controls. This means it allows any mix of mouse, keyboard, or gamepad input simultaneously.
- When your game wants keyboard input (e.g. when naming avatars), you call [the soft keyboard overlay] to automatically bring up the text entry UI.
- Your game has no launchers that require mouse or KB input - or even better, no launcher at all.
To ensure users have a good experience from the couch, we also recommend the following:
- Make your UI readable from several feet away. Our rule of thumb: when your game is running at 1920x1080, your fonts should be a minimum of 24px in size.
- Start your game in fullscreen by default when the user is running Steam Big Picture (the "SteamTenfoot" environment variable will be set)
- For bonus points, at first launch detect the user's screen resolution and set your resolution to match it.
----------
I associated the "Full Controller support" badge with these requirements, but now I'll have to double check with Valve about that. They didn't correct me so I just assumed that's what it was. I'll post an update as soon as I know for sure.
One thing I was thinking about today is, what about mouse/KB controls? Will I ever be able to bind those to actions using the Steam "controller" interface?
Because that would be rather important and make the API even more useful (because then you can really unify your input handling).
Because that would be rather important and make the API even more useful (because then you can really unify your input handling).
larsiusprime
Member
I did ask them about that specifically. And I can't tell you what their response was... but they do know that's something people want.
We'll have to wait and see!
Spiral Insanity
Banned
Isn't Sony involved in this? I can't imagine how they couldn't be.
Why would they be?
Nabs
Member
Thanks nabs.
So it seems to be a little more latency. Could be really nice for folks without the steam controller to set the gyro to mouse and be able to pop of headshots.
MrTroubleMaker
Gold Member
nice!
grandwizard
Member
This is amazing news. As a Steam Controller owner I've felt the software side of it is amazing but the hardware is not. I've always wanted to be able to use the config tool and overlay commands with other controllers and this opens the path for that. I personally use a non-standard controller for most gaming and if I could access the overlay commands like touch menus and radial menus it would be so awesome. The DS4 is also a great gamepad for doing this on, with it's touchpad and gyro. But I do hope they open it up to all gamepads.
The API doesn't have events, it's very simple and polling-based. The calls are very fast so you can poll more once than every frame if you want, but once per frame should still be plenty. It's pretty standard, that's how people use XInput too. Definitely not a "huge basic error"..
The API isn't new with this BTW, it got released last year. The new additions are going to be tweaks like being able to resolve Origin IDs into on-disk glyph paths.