The issue is mainly support. If it gets out there and a bunch of people start using it, we have to spend an inordinate amount of time supporting it. Unity/Wwise/FMOD are used by something like 90% of our developers, so that's where we'd like to spend our time.
We also tend to break it -- a lot. 😃 The C/C++ SDK is setup so that we can experiment and move quickly with new designs, and once we release to the development community at large we'll have to worry more about backwards compat at the native level (vs. the integration level) which only helps a few developers but slows down our team.
The issue is mainly support. If it gets out there and a bunch of people start using it, we have to spend an inordinate amount of time supporting it. Unity/Wwise/FMOD are used by something like 90% of our developers, so that's where we'd like to spend our time.
We also tend to break it -- a lot. 😃 The C/C++ SDK is setup so that we can experiment and move quickly with new designs, and once we release to the development community at large we'll have to worry more about backwards compat at the native level (vs. the integration level) which only helps a few developers but slows down our team.
Okay, I'm cool with that.
You have an idea about when it will be "mature enough" so that supporting it will not be problematic for your team? 🙂
(If you have no idea when, or if you're can't tell, I can take that as an awnser. I'm just curious ^^")
CV1+Touch; Running on GTX980 - 4770K - 32GB DDR3
Developer at LIV
No idea -- imagine when we can't think of any major new features that it will be considered stable, but we're constantly working towards improving it right now.
