Takes a little bit to familiarize with the asset, but once you get going with the online docs it still doesn't make sense immediately. But then it does and now, I don't need to use anything else.

Easily one of the best controller frameworks here, very usable - easy to program. Used it in the game Manic Archers! Worth the price.

I bought this 9 years ago and never used it in a shipping game because it always had issues. It still does. I recently thought I would use it for the names of buttons on controllers. It works well when you bind them but after saving and loading them back in, the good names go away. I have had a few problems and am not getting any response to any emails. What is odd is that he is adding support for new things when the core old things that most people use it for don't work. There is obviously a lot of work put into it and it can be used to learn some things but I am still not going to use it in a shipping game. Addendum: He finally did contact me on a forum post and said he had no good answer. That is an answer so I added a star. The library is still lacking in examples and documentation but any support is likely worth the price. Further addendum: I did everything I could to get this to work. I got some things to work but I can't get everything to work. So I am pulling it out (extremely reluctantly). I have to go back to my old code and make that work. I got no help after getting one message that what I wanted to do won't work. BTW, the "Getting Started" code has all sorts of stuff that won't compile so I highly recommend not getting started.

The documentation is lacking, more examples of different scenarios should be covered. It's mainly used by devs with a keyboard, not a controller. Videos should be updated. It's somehow hard to figure out how we should use it.

I've used this asset now in the second project and it it worked like a charm. For transparency – I only use it to poll controller button states on Standalone and Apple builds in a standardized matter, and to get Apple controller glyph names for buttons. While this is only a small subset of it's functionality, everything works as expected and the code is very well structured! Twice, I reached out to the developer b/c I needed support for a new feature/ platform and was helped in a timely manner. Big ups for supporting this for many years now!

I bought it as an alternative to its most popular concurrent. Here are some negative points: - Poor gamepad detection, when you connect a gamepad it often takes several secs to detect it - You can't query the "active gamepad" in Start() or even in the InControl.InputManager.OnDeviceAttached(), meaning it's still telling you there is no controller connected - Support for only one center button Positive : Seems to be lightweight and fast

This is a really good asset and I do recommend you use this instead of Unity's default solutions. However, the documentation really needs updated! A lot of the videos aren't public and cannot be watched and there were a few things that just seemed a bit confusing at first. The examples, however, are very helpful and help fill in the gaps I feel are in the documentation. There are a few features a would love to see added, like a get any input feature or a way to save a single action instead of the entire action set, but all in all it is a great solution! TLDR: Great asset, poor documentation, I would still recommend it!

Does what it says. If you feel the need is worth time, effort, and expense. See the "Getting Started" video on YT to get an idea of what is involved.

Incredibly useful and makes handling player input almost no effort at all. As someone who prefers having as much stuff in code as possible (and as little of it in prefabs/settings/GUI) this EXACTLY what I was looking for. The included examples also really help show how to pattern-match to precisely how InControl wants to be used. Great work!

The support team did not respond to the reported issue found in this package. I think the package is dead. 🕸