Push/Pull block in First Person Mode

[SmallShank]

Followed an extremely helpful tutorial on how to interact push/pull a Cube on keyboard F input (in my case I have this as E).

Here is the link: https://youtu.be/v3JXpF4wl_o

Everything was followed correctly with no blueprint errors at all. I interact with the Cube on pressing the keyboard E, however, I can only move the Cube forward and not to the left, right, or backwards.

I’m wondering if the reason this isn’t functioning correctly, is because the tutorial uses a full skeletal mesh in 3rd person, and I have followed this tutorial and used it in my first person mode, which only has the arms and not a full body.

Could it be something to do with the Physics Constraint on the Cube?

This is a new mechanic I have discovered today, and I have experimented with expanding the scale and angle of the constraint to try and get it to come into contact with the arms to see if that resolved the issue.

Is anyone able to help or point me in the right direction as to why this isn’t working?

Thank you

[Everynone]

@SmallShank

I can only move the Cube forward and not to the left, right, or backwards.

Perhaps you could post the part of the script responsible for this behaviour?

[SmallShank]

Code for the macro created with the Cube

Code within the blueprint for the Cube itself

Small extension at the end added on, followed as part of the step by step tutorial for this interaction

[Everynone]

We can’t see you call the macro anywhere above. It would be either called on Tick or after an Input Event - more likely.

[SmallShank]

I apologise, completely missed that step, was quite a bit higher up in the blueprint event graph!

Not sure if this needs another component added?

Below is the other section relating to the Cube:

[Everynone]

How are those variables set?

When you debug this part, does the execution flow the way you expect?

---

Push/Pull block in First Person Mode

Most importantly, how would like it to work? We can grab the box only from one side and shift it only in its local axis?

[SmallShank]

The Action Value X and Action Value Y were promoted to a variable to get those references.

In doing so, it created the SET, which I deleted as it would have interfered with the Movement Input flow. Maybe that was the error, I shouldn’t have deleted that section, see below:

Will debug test the code flow now

[Everynone]

@SmallShank

Maybe that was the error, I shouldn’t have deleted that section, see below:

It’s not even connected, and it should not interfere with anything once connected. As in, this is fine:

---

If you find the chance, do tell:

@Everynone

Most importantly, how would like it to work? We can grab the box only from one side and shift it only in its local axis?

I sense the whole thing can be dramatically simplified and made more efficient. Many red flags in that tut.

[SmallShank]

That is the first time I have seen the code in debug mode, really good to see what is working and what isn’t.

What you say makes perfect sense, it wasn’t even grabbing the X and Y. Let me amend the blueprint based on your feedback

[SmallShank]

It works! Everything in the blueprint was set based on the tutorial I had found and followed based on the tutorial video mentioned above.

Thank you for helping me, the problem was I hadn’t correctly grabbed the X and Y axis data. Really appreciate you taking the time to help me with my issue