Widget Interaction Component broken in 4.16?
Just upgraded to 4.16 and the widget interaction component in my VR project is no longer functional. It doesn't even show up in PIE when 'show debug' box is ticked.
An error message says "Error The cursor class '/Engine/VREditor/UI/VRRadialCrosshair.VRRadialCrosshair_C' was not found, check your custom cursor settings.". Although I'm not sure this is the issue, since it can be solved by using a custom widget in the Default Software Cursor in Project Settings under User Interface. Once that is done, the error message disappears but the widget interaction component is still not working.
I'll stick with 4.15 for now, but I was looking forward to the new release so it would be great to get this fixed as soon as possible.
I just updated to the latest build and it seems to be working fine now. Happy days!
answered Jun 01 '17 at 07:48 PM
Why is this marked green - i dont see any answer or solution?
My widget interactor seems to be hitting the widget but with an offset so my widget controls register only when I click up and the right of them !?
answered Jul 09 '17 at 03:58 AM
Encountered same issue when migrating my stuff onto new version. Widget Interaction just didn't work, and I couldn't figure out why, exactly. Answers above I guess do work, but it didn't work for me. Anyway, tinkering around, I found out that in version .16 Widget Interaction Component behaves much rigidly in terms of proper setting up of parameters. You MUST have unique Pointer Index for EVERY Widget Interaction Component active ingame. That means, you should be sure to set to active only those components, that you really need (for spawned actors), and give each an unique pointer index if there are more than one active. It stops working completely (no debug traces drawn) if it encounters two components with the same index. Disable all but one (or set proper index), and it works as intended, and draws debug lines too. At least, that's how I understood this problem. Worked for me. Sounds silly and kinda unprofessional, but I forgot, that when you spawn Motion Controllers, you spawn two Widget Interactions. In .15 it worked fine, and I didn't notice any overhead, so I forgot about it completely.
answered Jul 17 '17 at 03:33 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here