Hi Guys,
Im having issue with my project. after a few secs to minutes, i suddenly cannot walk around or move the camera.
in my observation it happens:
Hey there @geronne! When you begin Play In Editor (PIE) you will have to click inside the window so that it can begin receiving your input context. Are you unable to do so if you don’t press it before 30 or so seconds has elapsed?
Hi @SupportiveEntity thank you for responding. it is also happening in the windows Build ive packaged.
Interesting! Does this apply to all projects now or just your specific project? If it’s isolated to your project, it has something to do with either your character controller or the character BP itself. We’d definitely need more information on your character controller and your pawn itself.
yup, i tried to create a new project and doesnt happen there. it is isolated. im still no sure why this happen. maybe do you have some idea that i can check?
The first thing that came to mind would be something occurring with the BP logic. So I’d start with placing some breakpoints or print statements on your inputs on your character BP and pull up the player controller and verify any inputs are being received.
Another possibility if you use a physics based pawn that physics based pawns can go to sleep after 30 seconds or so but physics movement should always wake it.
got it. Thank you so much @SupportiveEntity. btw last question, is there anyway to check data changes? for example when the control suddenly disabled? its not my src code, so im having hard time to check it
The answer changes depending on which component is having the issue. Start with the high level checks like verifying if the Player Controller is still sending inputs, verify the character is receiving them, then verify they are being sent. Another trick would be to import the components of a sample project to this project, and run a sample level, with the sample gamemode, and sample character + controller and verify if it’s project wide Player Controller wide.
Once you can tell where the break is, you can start honing in on what could be causing it and where to look. Otherwise the possibilities are so broad that it would be like taking a comb to a haystack.
Thank you so much @SupportiveEntity. i will definitely try that.
also, just to add information, this is the logs that show when i cant control anymore. this shows first then i cant control anymore. maybe this mayhelp
Good catch! That’s related to this node:
I’d use the code search function on the aforementioned blueprints to check for this node first.
fixed my issue. Thank you so much for the help @SupportiveEntity
