I’m following this tutorial, but I can’t interact with the buttons like shown in the video, also I can’t see my mouse cursor while running the game.
The title seems a duplicate, but I’ve read these questions (one)(two), and followed the suggestion of setting Pivot to (0, 0) still with no luck.
If I set the Pivot to (0.5, 0.5), which is the default value, I can somehow (randomly) interact with the buttons, but I can’t see the cursor, all that I can do is blindly move my mouse around and suddenly the button becomes hovered.
Besides, my buttons are vertical, but my mouse has to move horizontally to hover through the buttons.
I ran into the problem of 3d Widgets just plain and simply not working, not being able to interact with them at all, where they worked ok in 4.8
My setup is that I have 2 computer blueprints, 1 migrated from 4.8, and another newly created blueprint, set up with the exactly same mesh, with a 3d widget component (not copied from 4.8 blueprint, just added to the blueprint with the exact same settings).
When the player clicks on the computer, it gives turns mouse cursor on and changes the interaction to UI and Game.
On the 4.8 blueprint, it works perfectly fine, but on the new 4.9 one, it doesn’t work.
I even copied the 4.9 widget over to the 4.8 blueprint, removing the 3d widget component from the 4.8 one first, and then it didn’t work.
But when I copied the 3d widget from the 4.8 blueprint to the 4.9 blueprint, it worked perfectly.
As for the settings possibly being wrong, I spent hours scratching my head to the point where I got a pen and paper, went through each individual setting and wrote them down, side by side and found they were all identical. I even got another person to triple check it for me just in case I was losing it
So my temporary solution I have is to make the 3d widget in 4.8, migrate it to the 4.9 project, and copy the 3d widget component from it for it to work.
Thank you for pointing out these issues. We are actually in the process of updating the tutorial you cited, but ran into the same issues as you. Our development team is aware of the issues and a fix for this is planned for 4.10.
