Enhanced Input System: when are input actions set to be executed

[WSwinks]

@ClockworkOcean

It’s up to you what input actions you include in a class. IA_Shoot may not be there at all when you start, if you want to include it, you can.

What do you exactly mean with including it? In the VR template the input actions IA_Shoot_Left and IA_Shoot_Right are defined in Blueprint. Do I need to include them in C++ or does the UHT links this as long as I define the input actions as UPROPERTIES?

@ClockworkOcean

It makes sense that nothing works without a mapping context, because the mapping is a translation from your input to the events. Say I want to use X as IA_Shoot_Left and ‘Spacebar’ as IA_Shoot_right, the system doesn’t know this until I add the mapping context, and it makes no sense to respond while the mapping is missing.

Why is it then that the showdebug enhancedinput command highlights the input actions when I press the buttons assigned to these input actions in the input mapping context when this input mapping context is not yet added? This confuses me.

@ClockworkOcean

As for passing parameters, there are a lot of parameters returned with the event itself, but if you want to pass specific parameters yourself, its probably easier to incorporate the IA… events in the player controller, and use that to call different events ( using an interface for example ) in the corresponding class.

Can you elaborate on this part? I don’t understand it completely.