It seems that in 4.21 the mouse input for the y-axis doesn’t work anymore. I did set it up in the input section
and in my character blueprint I set up a simple graph for the LookUp functionality
in 4.20 it all worked perfectly. The weird thing is if I show the mouse cursor, the y-axis seems to work. Does anyone have a suggestion?
What if you create a standard fps or tps project, does it work there?
Make sure you aren’t using the same input or axis value anywhere else, i.e. Level BP which can override. If that’s the case you can disable “Consume Input” in that input or axis’ Details in wherever else you are using it.
could also be your characters setup. for example the inherit pitch and use control rotation options. i would use a print string instead of the add controller pitch to confirm if the axis event if firing. once you ensure that the event if firing you will know if the issue lies elsewhere.
Thank you for your comments!
@Tuerer: It works in the TPS example project
@Jacky: I don’t know exactly what you mean by “Consume Input” but I checked my Blueprints and the Character Blueprint seems to be the only one which uses the InputAxis-Event(s) … and each of the events is only used once.
@ThompsonN13: I disabled/enabled the “Inherit pitch” and “use control rotation” options for my camera boom without any effect. I tucked a print string behind the event and it always seems to fire with an output of 0.0 … even if I don’t move the mouse at all.
It is weird that the yaw works but the pitch doesn’t. :-/
If it works in another project, that it’s certainly not a 4.21 build or hardware issue; something in your project must be interfering with Y movement.
Also i agree with Tuerer. If you used even the axis value like the one in the screenshot in a higher priority BP it is going to prevent you from using it in your player character.
Thx… yeah the mouse Y stuff doesn’t get called anywhere in my blueprints. Maybe I have to check my C++ classes again.
You’re right, it is no inherent problem with the 4.21 build. It is just that the 4.21 apparently did something new in the source code (maybe something with the input) that interferes with my code and/or vice versa. I checked my project with 4.20 again and it all works there.
I think I have to study the 4.21 release notes. Thank you guys.
Ok found the solution.
I have a function that reads the mouse sensitivity from a config file and sets it via console command
Apparently the console command changed in 4.21 so that you don’t enter one value for the sensitivity anymore but a x- and a y-value
In my case the y-value must have been set to 0.0 because it wasn’t specified … now it works. Thanks again for your help.
