Questions I have

[Aaron]

The eAction_Test commands are just for debugging, for firing off functions so that you don't have to replay the whole level to trigger certain events. They are only linked to keyboard numbers 0-9.

[Rapture]

Do you know what the function is called for grabbing the Keyboard/Mouse input?

[Aaron]

Afraid not, just a lowly artist . Perhaps a scripter can pop their heads in!

[Patrik]

Do you know what the function is called for grabbing the Keyboard/Mouse input?

You should be able to get by with using the OnAction callback that's called in levels, modules, player states and probably other things as well. You can also use the cInput_* functions for directly checking an eAction from anywhere in the code.

Code: (Select All)

cInput_BecameTriggered(eAction_Jump)

You can set up your own eActions in InputHandler.hps and InputHandler_Types.hps if you need something not already defined.

That's the recommended way of doing things and the only way we do it in all of SOMA, but I think you can also do cInput_GetKeyboard()/cInput_GetMouse() to get direct access if you really want to. Something like:

Code: (Select All)

cInput_GetKeyboard().KeyIsDown(eKey_Space)

Haven't tried it myself though and will quickly get complicated if you want to rebind keys or allow gamepad use.

[Rapture]

To get the Debug 1-9 to work.


Is their something special you need to do, to get them to work? I am in DebugMode, but pressing 1 doesn't seem to do anything.

Code: (Select All)

    void OnAction(int alAction, bool abPressed)
    {
      if (!abPressed) return;
    
      if (alAction == eAction_Test1)
     {
      Entity_SetActive("construct_theta_1", false);
      cLux_AddDebugMessage("Hi");    
     }
    }