Why isn't my blueprint Actor responding to OnClicked?

Development Programming & Scripting Blueprint
, , ,
1

Ok, so this is probably something really minor, but I’ve spent a few hours on it now and can’t seem to figure out what I’m missing!

Steps:

  1. Create new C++ puzzle template (my prototype is based on this)
  2. Create new blueprint Actor
  3. Add Sphere shape as component, set it to visible in game
  4. Add OnClicked event in the Actor’s Event Graph, just wired to print string
  5. Add blueprint actor to scene
  6. Play and click Actor’s sphere component

I’ve messed around with this a lot, and it seems to me this super simple setup should call OnClicked, but I’m not seeing any of the input events called for any component in a blueprint Actor, regardless of if I spawn it in blueprint, set it to enabled, or set input enabled from player controller.

Really stumped… what am I missing guys?

Thanks

2

Did you select a player for “auto receive input” in the “Default” section of the blueprint ? In a single player set it to “player 0”

3

Nope, had already set that. Looks like it’s an issue with component type, see my answer

4

So I was thinking, obviously onClicked works with the static mesh cube in the puzzle example, so what if I added a static mesh component to my blueprint? And wallah, it worked!

Still seems pretty strange to me that a sphere shape (the bounding sphere that I would expect to be designed for collision, including clicks) doesn’t work. And it didn’t work for me with a skeletal mesh either, although I suspect this requires further bounds configuration like you do for a player controller (this was just a skeletal mesh in a blueprint Actor).

For now I’ve made a low-poly sphere static mesh and added it as a sub-component to my skeletal mesh, with its visibility off. With this setup, clicks inside the invisible sphere mesh fire both sphere → onClicked and actor → onClicked, so problem solved.

Anyone know why the other component types don’t work as I expected? I’m running 4.3.1

5

As answered by Ben Halliday(in my question) simple go to your skeletal mesh, right click it in the content browser then click create physics asset, then it will work without need to add a hidden static mesh , tell me if it works!

6

It does have a physics asset already setup…

7

I had this issue (onClicked and similar events wouldn’t fire on one specific actor blueprint when other actor blueprints with different meshes worked fine). Here’s the solution that worked for me:

24997-ufo.jpg
24997-ufo.jpg1920×1080 188 KB

Note that you must open the static mesh asset to view this setting. So, double click the static mesh in the content browser to open its details. Selecting an instance of this mesh in the level will show you the details for that instance, which does not include this setting.

8

For those who tried everything mentioned but OnClicked still doesn’t work:

Make sure you don’t have hidden widget on the HUD. It will purge OnClicked event. Make blocking widget SelfHitTestInvisible.

if (PlayerInput)
{
	bResult = PlayerInput->InputKey(Key, EventType, AmountDepressed, bGamepad);
	if (bEnableClickEvents && (ClickEventKeys.Contains(Key) || ClickEventKeys.Contains(EKeys::AnyKey)))
	{
		FVector2D MousePosition;
		UGameViewportClient* ViewportClient = CastChecked<ULocalPlayer>(Player)->ViewportClient;
		if (ViewportClient && ViewportClient->GetMousePosition(MousePosition))
		{
			UPrimitiveComponent* ClickedPrimitive = NULL;
			if (bEnableMouseOverEvents)
			{
				ClickedPrimitive = CurrentClickablePrimitive.Get();
			}
			else
			{
				FHitResult HitResult;
				const bool bHit = GetHitResultAtScreenPosition(MousePosition, CurrentClickTraceChannel, true, HitResult);
				if (bHit)
				{
					ClickedPrimitive = HitResult.Component.Get();
				}
			}
//2F:THIS IS WHY YOUR CLICK EVENTS ARE BUGGED
			if( GetHUD() )
			{
				if (GetHUD()->UpdateAndDispatchHitBoxClickEvents(MousePosition, EventType))
				{
					ClickedPrimitive = NULL;
				}
			}
  //2F:-------------------------
			if (ClickedPrimitive)
			{
				switch(EventType)
				{
				case IE_Pressed:
				case IE_DoubleClick:
					ClickedPrimitive->DispatchOnClicked(Key);
					break;

				case IE_Released:
					ClickedPrimitive->DispatchOnReleased(Key);
					break;

				case IE_Axis:
				case IE_Repeat:
					break;
				}
			}

			bResult = true;
		}
	}
}