The axis input for Unreal Engine 4 consumes plenty more than the action input, oddly; in fact, it consumes so much that the axis can only be attributed to one input at a time. What to do?
Thankfully enough, most of the axes were separated from Gamepad and Keyboard inputs, but I did have to create an extra function. In there, I also placed Blueprint implementable events to trigger the change in tutorial text. Success!
But wait, there's more; seems as if the text material was fairly wonky, as it was displaying more translucency than was appropriate. In order to make it visible, I searched around for the proper translucency settings, removed them, and placed in some glowing text.
It's still a bit translucent, but a lot more visible.
No comments:
Post a Comment