I am currently working in release build of 4.5. I have gravity gun like system in 4.2 and have ported game over to 4.5. As I was testing to see if everything works set actor location seems to false not matter how rock is set.
Is your Actor being moved by this node at all? It looks like you have your Print String set to only print when Moved is set to True. So when you call New Location, is Actor’s location actually being set? According to your screenshot, it is.
If it isn’t being moved, try refreshing nodes. Select all nodes in your graph and right-click, then select Refresh Nodes. Upgrading your project from much older versions can sometimes cause problems because editor handles BPs differently, and sometimes a simple refresh can clean things up.
I have tried your solution and nothing has changed, it dose not move a unit. I am sure bottle neck is with set actor location. Is it possible that I have it setup wrong in some way?
I set up a project to test this, and Set Actor Location is working for me. I also created same project in 4.2 and then converted it to 4.5, and still did not encounter any problem with Set Actor Location. way you have your BP set up should move your mesh when function is called and then print string you created below.
Based on screenshot you provided, I can see that print string is being called, which should only happen when actor is successfully moved. How are you calling function, and what vector value are you feeding it? Can you show me an image of where you’re setting vector value for New Position and where you’re calling function? Thanks!
Okay, it seems like that should work, if Forward value is what you’re feeding your New Location function in pickUpable Blueprint. I’d like you to try replicating what I have exactly to see if it works in your project, if you don’t mind. I have a very simple setup, which you can see in these images:
We haven’t heard back from you in a while, so I am marking this post as resolved for tracking purposes. If you get a chance to try suggested Blueprint setup above and still have experience issue with Set Actor Location, please let me know and we’ll continue investigation. Thanks!
Hi guys, not sure if this is appropriate place to put this but I have built a very basic test for set actor location as I was experiencing similar issues. In 4.8 there seems to be a bug with it as it works as intended in 4.7 for me. I made a basic blueprint object with physics simulated and a keypress for testing setactorlocation.
Having same issue here, return value is reporting true that object has teleported but nothing is happening. This has been tried with ‘teleport’ and ‘SetActorLoction’ nodes. This bug is persistent to 4.9.
I’m not having any trouble with this on my end in 4.9.0. Are you able to reproduce this in a new project? If so, please create a test project for me and upload it someplace like Google Drive or Dropbox, then get me a download link so I can take a look at your setup. Thanks!
I had same issue as this. In case anyone is having same problem, Set Actor Location does not work if physics is enabled. I’m not sure if it is a bug or not.
I ran into a similar problem and managed to solve it. I’ll post solution here in case somebody encounters it again. In Transform component of details tab, there is a “Mobility” option. Set it to “Movable” and problem should be resolved.