Seriously. I did pick up a sufficiently difficult task, however; it seems that the tutorial text needs to display different actions based on the input being used.
After moving through unsavory amounts of array looping and testing the wrong actions, I find out that "Any Key" literally refers to Gamepad buttons as well. Now I can set the buttons to ignore and the buttons to use for switching between Gamepad and keyboard use.
How do the actors see this? The actors at the beginning of the scene (only once) get a list of action mappings that they will be attached to. As a result, they will also have a list of the different (keyboard/gamepad) keys attached to those actions. This results in a much smaller array to move through each time different input is registered, and produces text that changes with input:
It'll still need a bit of polish and may require images instead of buttons, but it's a start!
As for the big programming project, I think I will tackle DirectX terrain generation. The platform is always a tricky one to work around, so I'll be plenty busy working from the ground up on creating a proper application first.
No comments:
Post a Comment