[Solved] Sudden Unity Bug. Pointer to World position has offset. Accidently changed cinemachine settings?

My game was working just fine. I started it up, added a few things, ran it and saw there was an error regarding where the characters arm/gun is pointing to.

I reverted a commit because I couldn’t figure out why, since this worked before. However, in the revert too, this bug/glitch is present, and it shouldn’t be. Last time I left off, I was sure there wasnt any such bug.

So I even created a debug circle image and positioned it to where the pointer is to demonstrate what is going on. As seen in the video below, there is an offset, the pointer screen to world position is the red debug circle, but the pointer is half screen below it.

https://youtu.be/gmLAHI7TQMY ← this is the link demonstrating what I mean.

I believe this may be a cinemachine bug, because after adding my character’s transform as look at, this bug occurs, otherwise by just setting follow, the chatacter is at the same offset under the screen. There are no offsets given to the virtual cam to do this however.

Thank you for helping to attempt me at fixing this.


Update: So I have the virtual machine as a child of a child of the main cam. and I moved it, but could not reset the position. This is causing the issue, and I’ll come back to fix this issue. x|

========================================

Solution: In cinemachine virtual cam, I set body to framing transposer, and aim to do nothing (Forgetting this part, but I the initial error was caused by camera offset for a different body, so set camera offset to 0 if you have the same problem).

I accidently changed these and moved the camera around. I learned a few things, and a few tricks. the offset of the cinecam was the cause of my issues. Also, offsetting the cam like this would mean screen to world is going to mess up if I try this in the future, so it probably isn’t something I’m going to use.

Solution: In cinemachine virtual cam, I corrected the fault by setting body to framing transposer, and aim to do nothing (Forgetting this part, but I the initial error was caused by camera offset for a different body, so set camera offset to 0 if you have the same problem).