Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

I'm unable to get my playercontroller to respond to movement inputs anymore (It used to work perfectly fine until today)

Basically, I'm very new to the Unreal Engine and I'm working on something involving it for my school personal project.  I managed to get my player character and game-mode to work perfectly fine since the start of the project, however today it suddenly stopped working for me - it was working this morning but stopped working after I built my level more. The mouse inputs still work and I can move my camera around freely, however my movement keys have suddenly gone non responsive and I am unable to resolve it.  Any help is appreciated alt text

alt text

alt text

Product Version: UE 4.21
2018-12-09-4.png (696.9 kB)
2018-12-09-5.png (2.4 MB)
2018-12-09-6.png (183.9 kB)
more ▼

asked Dec 09 '18 at 12:16 PM in Blueprint Scripting

avatar image

3 1 1

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

If you didn't change any logic and only added more meshes to the level, then maybe one of the newly added meshes blocks your character with its collider? Here is what you can try to narrow down the issue:

Add PrintString nodes that print something to your movement input events and see if it prints anything after trying to move. If it prints it, then it means that the events are fired properly, but something in the scene prevents your character from moving.

... If that's the case, go through your newly added actors and disable collision on them, then try again. You can even go to a 100% problem-killer mode: Make a copy of your level and keep removing actors until your character will move again. This way you can find the thing that 'corrupted' your scene and fix its collision or remove it.

more ▼

answered Dec 09 '18 at 01:58 PM

avatar image

2k 154 153 206

avatar image KyrenDuNord Dec 11 '18 at 11:37 AM

Ahh thank you Slavq so much for your reply. I've finally figured out that the problem was a rouge static mesh I added with a bizarrely large collision size. Even though I had checked the player collision view, I couldn't see it whatsoever as it was extremely large and I was always within it. I tested deleting parts of my scene in large scale batches, and found out I was able to move. I was eventually able to narrow it down and fix the problem by modifying its collision. I'm extremely grateful for your help. Thanks again!

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question