Hey, TheFXGuy! Thanks for the support!
We found an alternative way to deal with this problem. The bug persists but we used the inverse way. It’s not perfect, but it works. We converted the 3d assets to the screen, because the problem is occurring at the mouse to world location conversion. The mouse location at screen is working perfectly, but when converted to the world location gives the offset.
Still, I will report this as a bug and keep this topic if someone, or our team, finds a solution to post here :).