Playercontroller not working

Posting this in Packaging & Deployment since i’m not sure where else to put it (using UE4?), let’s start.

Hi,

I started out with a blank c++ project (either on 4.1 or a 4.2 preview from github), using mainly blueprints. Until a few (3 maybe) days ago nothing was wrong everything was working, even when packaged.

Since then i’ve changed a few things, in c++,blueprints and i added a menu using UMG.

Now when in editor, when i use selected viewport or new editor window to test, everything still works, but when using standalone game or the packaged version it seemed like the playercontroller wasn’t receiving any input.

The pawn was working with input, so i tried triggering events in the playercontroller from the pawn, yet this didn’t change anything. Both new editor window and standalone game use the correct playercontroller class, so that’s not the problem. I disconnected everything in the playercontroller’s blueprint and only had BeginPlay linked to print string (“Hello”), this did work in new editor window, and not standalone game.

Does anyone know why this happens and/or how to fix this?
Should you need more information, feel free to ask.

Thanks,
Thommie

Forgot to mention, i started on 4.1 or 4.2 preview, but currently i’m working with default 4.2 with -umg.

Did some more experimenting today, created a new playercontroller in blueprint, extending the previous one and this one does work. I’m lost.

So apparently using my umg hud was the problem, i moved everything in the playercontroller referencing my hud (extending userwidget) to another class and suddenly it worked again, seems i have to wait for a new release to get the menu to work.

Hello,

Thank you for your report. We were not able to investigate this on the engine version you reported, but there have been many version changes to UE4 since this question was first posted. With a new version of the Engine comes new fixes and it is possible that this issue has changed or may no longer occur. Due to timetable of when this issue was first posted, we are marking this post as resolved for tracking purposes. If you are still experiencing the issue you reported in the current engine version, then please respond to this message with additional information and we will investigate as soon as possible. If you are experiencing a similar, but different issue at this time, could you please submit a new report for it.

Thanks!