I made a widget blueprint for a custom cursor (an image). I create it on Begin Play and toggle its visibility when RMB is pressed/released. The problem is, it flashes for a frame in the top left corner then disappears. I’ve tried Add to Viewport, setting visibility, and using Render Translation, but I’m still getting this flicker/flash issue.
(In the beginning very hard to capture cause it only shows for a frame but in game it flashes everytime)
i’d recommend to add it to viewport on begin play, and setting visibility to hidden/collapsed immediately after.
then only changing the visibility instead of adding/removing.
Hey again nande, I ended up getting that cameralock system I wanted working and found a way to ignore the mouse inputs. Thanks again
This is the last thing I have to add onto that system and it was going smoothly until this. So I tried what you suggested, I removed the remove from parent node so im not just adding it and removing it and I switch to the set visibility hidden right after adding it to viewport on event beginplay and Setting it visible-Hidden when pressing-releasing rmb, I also got the image cursor variable and connected it to the visibility nodes
But its still not working, now it just doesnt show up at all, Maybe I did something wrong im not sure. Got any idea why it might not be working?
i highly recommend not to “share” connections across multiple execution paths (the white lines). makes the code hard to maintain and could have weird side-effects. specially with “pure “ nodes.
notice you have connected the setvisibility on the input event to the result of CreateWidget.
connect it instead to the variable you set right after that node.
i would suggest not to drag a line from the same “set” node, but instead drop a new node for that variable
also i can’t really read the text since it’s too small. but the connections seems pretty ok.
great work anyway, good progress.
I changed the order of the visibility nodes and put them on the bottom IA. Along with your other suggestions and touch ups and as a result it started working how I wanted. I will say though I use multiple IA exe pins because it doesnt work otherwise so i usually have to use both canceled and completed. I didnt know it was a bad idea to use multiple but hey if it works it works XD, Thanks again you a real one 
hey i’m really happy to hear it helped. great work!
sorry i didnt meant those.
though if you use on trigger and ongoing that might be bogus. but what i meant was this
crossing execution lanes
which is not bad per se. but i try to avoid it when possible as it makes maintaining the code harder.
specially with pure nodes which gets executed every time you connect them.
and the result of the createwidget i truly do not know what happens on the IA whether it has a value or not.
i also think that your code could be made into some functions, at least the one for the IA at the top, it’s really looks like it’s duplicating most of the code.
but these are minor issues, crossing execution lanes would be the one prone to issues though.
Ah I see what your saying ill keep that in mind, I have no actual experience with game dev ive just watched like 3 tutorials from smart poly so im sure my blueprint connects are not very optimal but i plan to make improvements on it once im more experienced.
