Enhanced Input problems in 5.5

Development Programming & Scripting
,
1

There seems to have been some breaking changes between 5.4 and 5.5 that impact the Enhanced Input system. In trying to isolate why most of my input logic is not working in 5.5 but worked fine in 5.4, I have worked up a minimal sample that exhibits all of the same behaviors, and here are my findings:

First, if you have Enhanced Input Action events on UI class, create a child class from that, and spawn the child UI into the world, the events will not fire; though they will fire just fine if you spawn the parent.

Second, if you add an enhanced input event to the child class (even one that is unused and not part of any mapping context) then the enhanced input events will fire on the parent, even if you spawn the child. (The unused event does need to be hooked up to some code, like a print statement, even if it will never run)

Third if I remove the UI from the viewport, and then add it back in (the same instance), then all enhanced input events for the UI stop firing, even with the “unrelated event trick” above.

What changed in 5.5 that could have caused this? These seem like bugs rather than intentional behavior.

6 Likes
2

I’m experiencing this too in 5.5.1. Has anyone found any clue to what is going on?

3

I think I had the same issue.

In my case, I had an Enhanced Input Event placed in a User Widget and when I compiled and saved that widget I had a log message telling : ‘bAutomaticallyRegisterInputOnConstruction’ must be true in order to use Enhanced Input in the widget…

When I removed the Enhanced Input Event from that User Widget, the error disappeared.
So, to fix the problem, I had to put that Enhanced Input Event in my PlayerController to have it working by calling a Custom Event on the User Widget from the Player Controller Input Event.

4

My theory is that its not properly registering the widget with the enhanced input system if its only input events are inherited. This is why adding a dummy input event in the child fixes the problem.

I reported this as a bug (or bugs) over a month ago; but it hasn’t shown up on https://issues.unrealengine.com yet.

5

Same issues an Enhanced Input Event placed in a User Widget

6

Bumping, enhanced input is almost unusable with widgets in UE 5.5.

7

As a temporary workaround until Epic fixes Enhanced Input in UE 5.5, I am attaching hacky code that makes Enhanced Input work. Implement this class in C++ and then, inherit from HACK_UserWidget rather than UserWidget when creating Blueprint widgets which are supposed to receive Enhanced Input Action events.

#pragma once

#include "CoreMinimal.h"
#include "Blueprint/UserWidget.h"

#include "HACK_UserWidget.generated.h"

UCLASS(Abstract, meta = (DisableNativeTick), MinimalAPI)
class UHACK_UserWidget : public UUserWidget
{
	GENERATED_BODY()
public:
	virtual void NativeOnInitialized() override;
};


#include "HACK_UserWidget.h"

#include "Engine/InputDelegateBinding.h"
#include "Extensions/UserWidgetExtension.h"
#include "Blueprint/WidgetBlueprintGeneratedClass.h"
#include "Extensions/WidgetBlueprintGeneratedClassExtension.h"

void UHACK_UserWidget::NativeOnInitialized()
{
	if (APlayerController* Controller = GetOwningPlayer())
	{
		UInputDelegateBinding::BindInputDelegates(GetClass(), Controller->InputComponent, this);
	}

	if (UWidgetBlueprintGeneratedClass* BPClass = Cast<UWidgetBlueprintGeneratedClass>(GetClass()))
	{
		BPClass->ForEachExtension(
			[this] (UWidgetBlueprintGeneratedClassExtension* Extension)
			{
				Extension->Initialize(this);
			}
		);
	}

	for (UUserWidgetExtension* Extension : GetExtensions(UUserWidgetExtension::StaticClass()))
	{
		Extension->Initialize();
	}

	OnInitialized();
}
8

so currently i don’t think there’s a way to activate the Automatically register input on construction.
The issue is that unreal 5.5 doesn’t allow you to use the enhanced input with Child Widgets, this is, if the widget is inside another widget without being “create widget”
so my current solution is to go to the “parent Widget” and Call the functions inside the child
like this:

image
image606×690 100 KB

that fixed my issue, but it’s very annoying.

9

@vyzor You do not need to do this. Unreal will work “as normal” as long as the child has at least one input method, even a dummy one. I use this:

InputHack
InputHack677×318 28 KB

As long as you have an Input Action (it doesn’t have to be mapped to anything) if you put this event in the child, it allows the parent events to register even on the child.

1 Like
11

man it starting to make me crazy does someone has any solution? for my part when i open it all the enhanced actions work fine but when i close it and open it again they dont work anymore. i have been searching for a good 2 week on this matter…

12

What do you mean by close it and open it?

If you mean that you Remove the UI from the screen (close), and then re-add the same instance of that UI to the screen (open), the only solutions I know of right now are to either hide the UI (not remove), or recreate the UI each time (rather than create once, and re-add the same instance).

13

This did it for me! Thanks.

15

I was having the same issue and I was able to solve it in C++ by overriding NativeOnInitialized and setting bAutomaticallyRegisterInputOnConstruction to true. It seems like it’s supposed be set to true during compilation if the blueprint requires input handling but something must have broken in that flow.

void USomeChildOfUUserWidget::NativeOnInitialized()
{
	// HACK: This is supposed to be set at compilation time but it is not working as of UE 5.5
	bAutomaticallyRegisterInputOnConstruction = true;
	Super::NativeOnInitialized();
}
16

Please Fix This - the Enhanced input is broken in ue 5.5.due to this issue. The hack is just put an event input action in the widget to receive further input… but it will become a mess.
Furthermore the workaround is not working always. Example
If I have an input management just in a widget “Master Layout” and I Push a widget that does some actions based on specific inputs, it is not triggering. The only way could be put in each widget the capturing of input actions, but this will broker the concept behind the things.

It works perfectly from 5.0 to 5.4 - please check this issue that is really urgent.

17

The best way to get a resolution is to report the issue, not on the forums but via their official bug report path.

https://www.unrealengine.com/en-US/support/report-a-bug

I have already reported both of these when I created the original post; but checking https://issues.unrealengine.com it doesn’t seem like my reports made it into an actual issue entry.

18

I have also opened it. I was hoping that it was fixed in 5.5.4 hotfix, but the issue is still there :frowning: - I hope it will be fixed in the next version\hotfix

19

For future reference, the bug report is here, please vote on it.