Agreed that SIAPI needs to become it's own thing. It'll never become a new standard as long as it's tied to Steam.

If a game launches with SIAPI then it will typically be the default config so it will have automatically been loaded. So for most situations it isn't something to worry about. However, for instance, Rocket League added SIAPI support just a little bit ago so everyone who played before the update still had their Legacy Config loaded. They would need to manually import the SIAPI config. But anyone who buys it from now on will have the SIAPI config loaded by default.

@@criticalinput In my case I always like to make my own configs so I usually start from scratch. I did that to a game that (I believe) supported SIAPI and then never saw the unique inputs.

I want to hold off on RL because it's still in beta and I also touched on its current shortcomings in an earlier video. But as soon as they fix it up and release it properly I'll be making it immediately. It has strong potential to be the gold standard for SIAPI implementation.

@@criticalinput Thank you, I'll keep an eye on your channel.

I was wondering when someone was going to mention that.

@@criticalinput Btw You talking about code? ;)

Haha, why not? It's sort of like a giveaway but for viewers with keen eyes. :)

@@criticalinput Whoops. should i delete the above comment?

Nope. Just leave it. I'd be surprised if it wasn't claimed by now anyways.

I can take a look at this tonight. The SIAPI bindings should work just fine, though it might not display the correct glyphs in game. I'll get back to you with my findings.

@@criticalinput They have updated. For instance, left 4 dead 2 never used to support the radial menue with a ps4 controller (via the steam API). Now however it works fine. I'm talking about over 1yr ago.

Dang dude, I totally forgot to check in on this. I just put a note on my computer to do this tonight. I've never run into any issues with Steam Input giving devices exclusive options but I've never tried a SIAPI game with anything other than an SC either. Mainly because SIAPI is broken in every game that has it.

@@criticalinput makes sense, probably takes a lot of programming.

Just checked and everything worked just fine. The 180 Turn worked and radial and touch menus worked. Interestingly, I think I like the DS4 gyro more than the SC gyro. I checked every binding though and didn't run into any that didn't work. Which makes sense because Steam Input doesn't care what the controller is. Try it again and see if you are still having issues. Going back to your original comment, the reason that Steam Input throws up an error message about the config is just because the devs didn't create a DS4 config and you are importing a SC one. It does this anytime you do this; SIAPI or Legacy, and for Community configs, Dev configs, or even templates. It just lets you know that your device might have different Input Sources and that it'll try its best to put each binding in a similar place but that there is a chance that not every binding will make the transition.For SC -> DS4 it isn't really an issue, only the grips will get left behind. But if you were to do SC or DS4 -> Xbox then you'll lose touchbar and gyro and grip bindings -- which is quite a bigger issue.