Greetings! We have exciting news to share for those of you who want to hack, mod, or design accessories for the Steam Controller and Puck.
Today we're making the CAD files for the external shell (surface topology) of Steam Controller and Puck available for download under a Creative Commons license. This includes an STP model of each, an STL model of each, and an engineering drawing with critical features/keep outs for each. You can find the files here. We can't wait to see what you all...
Not even remotely related, also if they made a standalone driver it wouldnt matter because for the most part xinput doesnt support the unique hardware and if they made a standalone steaminput driver nobody else would put in any effort to support it. Its like how Valve lets anyone publish software for SteamOS by supporting flatpaks yet not a single other store acturally does. They would need to emulate xinput or directly support it meaning the touchpads and back buttons wouldnt be supported along with gyro or touchsense (at that point just get a standard controller).
Firstly, xinput support would still be useful. Reduced functionality >> no functionality. Secondly, it a standalone druver would only need to remove the steam itself and keep what makes the controller work. It would not require any extra work from any game dev. Stop making excuses for rich corporations providing half-baked support. It’s kinda pathetic.
If it was xinput you would be correct it would not require any additional dev work as they already support xinput, however functionality would be so severely reduced that honestly I cannot think of a single reason to use it like that (unless you really like the ergonomics I guess). If they went out of their way to make a standalone steaminput driver though that would require additional dev work for game devs that nobody else would do. You say why make excuses for rich corporations but why are you making excuses for xbox basically limiting xinput to their own controllers. Objectively xinput sucks, its clear that they never intended it to be a universal standard and until a truly open source API can replace it then yeah you’re going to have weird solutions like requiring steam open.
What other API are they supposed to support that has wide support and supports all features while not being tied to a specific ecosystem? Because as I said if they made a standalone steaminput driver that would require explicit support from developers (outside steam nobody else really interprets controller input the same way, typically they just allow the devs to do whatever). Its more complex than games just automatically accept any controller with any input method, they either need a stable API to call upon (which outside of steam is basically just xinput) or have a translation layer. Lets be honest nobody is going out of their way to support a standalone steaminput except maybe gog.
Not even remotely related, also if they made a standalone driver it wouldnt matter because for the most part xinput doesnt support the unique hardware and if they made a standalone steaminput driver nobody else would put in any effort to support it. Its like how Valve lets anyone publish software for SteamOS by supporting flatpaks yet not a single other store acturally does. They would need to emulate xinput or directly support it meaning the touchpads and back buttons wouldnt be supported along with gyro or touchsense (at that point just get a standard controller).
Firstly, xinput support would still be useful. Reduced functionality >> no functionality. Secondly, it a standalone druver would only need to remove the steam itself and keep what makes the controller work. It would not require any extra work from any game dev. Stop making excuses for rich corporations providing half-baked support. It’s kinda pathetic.
If it was xinput you would be correct it would not require any additional dev work as they already support xinput, however functionality would be so severely reduced that honestly I cannot think of a single reason to use it like that (unless you really like the ergonomics I guess). If they went out of their way to make a standalone steaminput driver though that would require additional dev work for game devs that nobody else would do. You say why make excuses for rich corporations but why are you making excuses for xbox basically limiting xinput to their own controllers. Objectively xinput sucks, its clear that they never intended it to be a universal standard and until a truly open source API can replace it then yeah you’re going to have weird solutions like requiring steam open.
I specifically said “standalone driver”. That does not equate to xinput support. You still have not understood what I said.
What other API are they supposed to support that has wide support and supports all features while not being tied to a specific ecosystem? Because as I said if they made a standalone steaminput driver that would require explicit support from developers (outside steam nobody else really interprets controller input the same way, typically they just allow the devs to do whatever). Its more complex than games just automatically accept any controller with any input method, they either need a stable API to call upon (which outside of steam is basically just xinput) or have a translation layer. Lets be honest nobody is going out of their way to support a standalone steaminput except maybe gog.
You think you really understand how controllers/drivers work. Unfortunately, you do not.