The scale value pin on the add movement input node does not seem to be accepting anything except a 1 or -1 value so I am unable to adjust the players movement speed, ie change to walk, crouch or run speeds. This is working fine for me in 4.7.6. Is this a bug in the 4.8 preview build at the moment?
Hi ,
Thank you for reporting this issue. I’m currently reproducing it, but it seems like it is occurring in all of the previous builds. I’ve tried 4.8 Preview 4, 4.7.6, 4.6, and 4.5.
To outline what exactly I’m doing to test this, I’m simply making a new project based off the First Person Template and changing the scale for the MoveForward event there. I can’t enter any values or calculations that can get it to go faster than 1.0.
I’m also looking into if this is how the function is suppose to work, but in the meantime can you make sure that this worked in previous versions?
I apologize if I am missing something but I am applying the same logic in 4.7.6 but it still does not work for me. The following screenshot shows what I have in my ThirdPersonCharacter blueprint:
I’ve made the default value of Scale 50.0. I’ve also tried directly plugging Scale into the Scale Value pin of Add Movement Input. This didn’t change anything except the fact that I was constantly running. My speed stayed the same as if it were 1.0.
Hi ,
I currently have this working properly in 4.7.6. My project is based off of the third person template but with a duplicated and adjusted character blueprint. What you see in the screenshot is exactly what is working in 4.7.6 but not 4.8.
Oh sorry, I forgot to clarify that I am slowing the speed by giving the variable a value such as .5 or .1.
If I do the exact same thing but with Scale set to 0.1 in 4.8, it works without an issue. I can only reproduce the problem when using a value higher than 1.0 or lower than -1.0.
Hi ,
Are you still having issues attempting to use a number between 0 and 1 for the Scale Value? I can confirm that it is not suppose to take anything above 1 or below -1 as that is how the function is designed, but it should be able to take 0.5 and make a difference in speed.
Hi ,
Its working fine for me in 4.7.6 but when I convert the project to 4.8 my scale changes are still getting ignored. Have you tried setting it up in a 4.7.6 project then converting it to 4.8? Maybe the issue is getting created there.
Unfortunately it still isn’t occurring, I made my blueprint the exact same as your original screenshot with the variable set to 0.5. Are you setting the scale value in another area, like your crouch function for example? If so, can you try also attaching a Print String to that same function and see if the scale value is ever actually being changed?
The scale value gets changed appropriately in both 4.7.6 and 4.8 as verified in the print string. It just seems like the scale value is ignored in the add movement input node in 4.8. Even if I set a value manually in the node in 4.8 the character still moves at max walk speed.
Can you try making a fresh project in 4.8 Preview 4 with the template for Third Person Character and reproducing it there? This would be a good way to narrow down if it is a problem with your project in particular or not.
Yup. Works when I create a new project with the new fancy mannequin but not when I try to modify the old mannequin in 4.8.
Yes, I manually copied the project to a new folder then right-clicked the uproject and selected the 4.8 preview version.
Interesting. Do you remember exactly what you did to convert your project? There are multiple ways, such as simply trying to open it in a different version or right clicking the .uproject. There are also different options for conversion as in converting in place or opening a copy.
This seems like an issue that is a rare case that is only occurring for your project and only when converting. I would suggest three different things that you can try.
First, try making more copies and converting in different ways. I tried all other ways I could think of, including yours, but couldn’t reproduce the issue. It is possible that something went wrong in the conversion process.
Second, if the project isn’t too large, try migrating the assets to a brand new project in 4.8 and see how that works for you.
Third, as this is a preview build of 4.8 and isn’t the final product, we don’t usually suggest development to be moved to this build from earlier builds until the final product has released. If none of the former works, I would suggest continuing development in 4.7 and attempting again once 4.8 is released which will be soon.
I apologize for not being able to directly solve your issue, but without being able to reproduce it I’m fairly limited in my capabilities.
I hope this helps,
Just wanted to post a quick follow up. Creating a new project in 4.8 and then migrating my stuff to that project did the trick. So it seems the issue in my case was doing a conversion in place. Thanks for the help!
This happens in a clean 4.8.1 TPP project as well, so not only for converted projects and it happens for all values except 0 and 1 (including 0.1, etc).
You have to play as 2 players or check “Dedicated server” though, this doesn’t happen in singleplayer. In 4.7.1 it used to work fine.
Hi ,
I made a fresh blueprint project based off the Third Person template in 4.8.1 and did the same repro steps as before without doing anything dedicated server or multiplayer related. When I set the ‘Axis Value’ to be multiplied by 0.1 before being input to the Scale Value, it goes one tenth of the normal speed as expected. Unfortunately I am not able to reproduce this by the explanation you’ve given. Does my method differ in any way to what you’ve done?
Hi ,
"without doing anything dedicated server or multiplayer related. " - you need to play as multiplayer to reproduce this bug, either 2 players or check “Dedicated server”
Ah, I misread your comment, I thought you meant that it worked only in multiplayer, I’ll give it a try.