What about no. Make it an optional plugin just like the Raw Input plugin. I don’t need this in basic projects and when I need to make a complex input system I will require something different anyway. I don’t need a bunch of extra binary files in which users are going to awkwardly try to program their logic. I need text based data assets. JSON or INI which just WORKS. Thank you. Don’t drag us down into your buggy experimental releases.
can’t still use legacy input in 5.2?
Can still use it but since it’s deprecated it might be removed at any moment.
In future versions, but not the current one it is in, right?
That is what deprecated means.
once you’ve begun a project do you keep updating the version?
epic isn’t going to do everything that you want. They do what they need for fortnite or whatever they are working on.
this seems like finding excuses for failure, instead of finding every possible way to win, to me. Sometimes when faced with a problem we don’t know how to get around, we invent issues that we do understand and point blame at them as a way to start justifying retreat.
If finishing game is the goal there is basically two choices:
- use what is there however you can
- invest time to fix the tools to your own liking or write new ones (unless you are a AAA developer, I doubt this is pragmatic)
anything else just seems like fruitless whining to me.
Call it fruitless whining I call it a shitshow on EPIC’s part for constantly breaking existing stuff and enforcing experimental bug infested plugins replacing core functionality that did work. Very professional.