Відео

Haha you're welcome! I'm glad its providing some clarity on the plugin, it's definitely far more complex than it should be. Setting up Common Ui is a huge battle constantly but once everything is set up it becomes really useful and easy to create Ui's. We just need Epic to step it up on cleaning it up more.

Hey! You would do exactly as you said! Under the ButtonBase, create an animation for that widget, then under ButtonBase use the built in event "On Hovered" -> then play the animation.. This way whenever this button is added to other widgets, the hover event will always trigger the animation.

Really appreciate the support 💪 glad you love the videos, feel free to comment if you ever have questions or come join the discord. Good luck on your dev log too!

And by the way, the same error appears in my friend's completely empty project

Which version of UE are you using? I took some time to try and play around to replicate this but I haven't been able to. Have you set the all the project settings shown in the beginning of the video? Specifically the viewport and inputdata?

It's a fair assumption, the setup for Enhanced Input Actions is such a huge upgrade from their previous setup with data tables to be honest but it definitely has ways to go to make it easier because right now there is too many things that you could slightly mess up on and it ruins everything. The main thing i like about this is that once it is setup you don't really have to worry much about it as everything else just starts to click into place easily.

Oh interesting! The custom c++ class was causing your Common Ui to provide errors? Or was it simply the c++ wasn't compiling and causing the blueprint deriving from it to break?

Glad you liked it! Always happy to help

I would make sure that you don't have overlapping IMC buttons, if the IMC_Default has buttons overlapping with the UI IMC then it would cause the buttons to not work, if they are overlapping you can set the UI priority higher than the IMC_Default to get it to work or remove the IMC_Default when using Ui and readd it after :)

@@MrButiier I have seperate mappings for both ui and player controls, and even thr action assets are seperate

Thanks man 💪 more to come that focuses specifically on the common action widget.

@@MrButiier what I found is that if you have Lyra like stack UI_Layout (Common Activatable Widget) |___HUD_Stack (Common Activatable Widget) |___Game_Stack (Common Activatable Widget) |___Menu_Stack (Common Activatable Widget) |___Modal_Stack (Common Activatable Widget) and then on BeginPlay you create UI_Layout, add it to the ViewPort and push MainMenu Widget to the Menu_Stack, then the Enhanced Input Actions won't pick up but if you create MainMenu Widget and add it to the ViewPort on BeginPlay it works as intended

I recorded 3 videos at this point of time so you’ll see yourself mentioned 3 times 💪 afterwards I will have a page in my video to showcase my supporters but in the meantime you can enjoy the special treatment :)

Appreciate the feedback :) I try numerous types of styles to see what people find useful so I appreciate it 💪

@@MrButiier creating everything from scratch each time wont scale much. What I think you could consider is pushing the final version to GitHub. This way you can continue focusing on the main aspects and details and have a full reference for those who needs the entire set. Thanks for the great content One think I'm interested in tho is how do you listen on the "Clicked" events? Do you use the Input Action itself in the Blueprint or simply attached to the Button OnClicked event?

@@maxsaylor9333 It definitely something I have considered and may try in future videos to see how well that turns out! For the click events, you can use the Button OnClicked event, those event will work as they normally would.

@@MrButiier thanks for the response, that what I was scared about. I have a listener attached to the Button that holds the Input Action and it's not reacting. It reacts when I explicitly hit the Button with a mouse click but fully ignores the assigned Input Action. Probably missed something, will continue digging But thanks again for the great content, nowadays it's hard to find something in depth, especially in the painful UI topic. I wish UI is simpler and just works, but unfortunately, there is always some dancing around involved

@@maxsaylor9333 Hm is the meta data set to “is generic action” or are there any other IMC’s with the same button? If there are overlapping buttons in multiple IMCs that can prevent it from being called. And of course, happy to help man, I know Ui is quite painful and there’s not nearly enough tutorials out there helping people with it. I agree that I wish UE5 made it easier but with more functionality causes more complexity.

Haha right on time!

Ah! Thank you for the feedback :) the main important thing here for icons showing is that the meta data and input actions are showing and that active IMC has the same buttons set. If button icons/texts are not showing then it means your IMC is not set properly. It's very easy to mess up.

It does work but there's still a lot they can do to make it easier and some bugs that make the editor a bit awkward in widget blueprints.

Thank you 🙏

Hi Lucky! Sorry that I did not specify which version I was using, I always use the latest version for my updates so I am using 5.4 in this video. If you're utilizing 5.2, it should be roughly the same set up based on the documentation but for your input action blueprints you need to set "Consume Input" on however since its experimental it may be prone to more bugs on an older version. dev.epicgames.com/documentation/en-us/unreal-engine/using-commonui-with-enhnaced-input-in-unreal-engine?application_version=5.2

@@MrButiier Hey! I kind of got it to work. It was an Issue with both my Player Controller and the "Set Input Mode to Game and UI" node, which seems to be broken with Common UI. However, I am still only able, to get Generic Acccept and Back to work. I have other Input Bindings, but they are not getting called. Also... I don't know, if this is just 5.2, but... Most UI for Gamepad have Accept on the face bottom button. Since the UI for our game will be complex, this will sometimes not be the case. In the generic input mapping context, I put accept to the face left button. But the face down button did ALSO trigger the button. After reading into the code A LOT!!! I was able to find the HandleKeyDownEvent method in the FCommonAnalogCursor. Overriding that method (C++ only) I was able to break that (hardcoded...) behavior... Does this still happen in 5.4? If you map generic accept to any button on a gamepad, will the face button down STILL trigger a button as well?

@@Luckyluk1996 hm if you're focusing a button with a gamepad then yes the accept button should also trigger the button and is intended to work that way, however if you're not focusing the button but both trigger the button then I'd say thats odd behavior and not something that occurs in 5.4 I'm downloading 5.2 right now and I'll try to see if I can get it to work however I have low hopes as CommonUi even in 5.3 had many issues.

@@Luckyluk1996 I downloaded 5.2 and didn't run into any issues as far button clicking goes, it looks to be visually built about the same as 5.4. To prevent a button from being hovered or able to manually click, make sure the button is not focusable. this should allow you to only activate based on the input action.

Appreciate the support 🤩 feel free to comment if you have questions or want a specific video made.

Haha thanks man :), I'm changing my thumbnails overtime to see what works best so I'll take note this, appreciate it.

Hm I couldn’t find any issues on my side trying to recreate it but if you could provide screenshots on the discord (I believe you joined the discord) I can see if I can help.

I watched a video that gave me and overview of how things work and did my own manual research so huge credits to this video: ua-cam.com/video/76SWLfeyO0o/v-deo.html I spent a long time checking each node available for the List View widgets and testing out what each one does to decide what to include into the video and cover it. The unreal engine common ui documentation was not very useful but I did open it a few times hoping it'd help lol

It could however it may be better to implement something a bit more simple for things like tiles/objects unless you're looking to do calculations based on armor etc. Stationary or environment objects typically would just need a health value.

Hey! It's in the description of the video called "Xelu's FREE Controller Prompts"

@@MrButiier Thanks

It would depend on how much control you would want within your game's resolution, due to the way UI shrinks and enlarges based on resolution. This just allows you full control over specifying resolutions you will allow in the game. You could still use "Get Supported Fullscreen Resolutions" then simply filter to make sure the X/Y of the resolution is not larger or smaller than what you would want to support in your game, this option does provide a variety of different resolutions for the player however as a dev, you would want to make sure you test as many variety resolutions as you can when doing it this way to make sure the Ui in the game does not get messed up. This way would still be perfectly acceptable and does provide the user more options! It just requires a bit more thorough debugging.

@@MrButiier nice explanation thank you sir

Thanks for the input and sharing for everyone else in the future 👏 I like to set the sliders 0-100 so that in the future i can display text from 0-100 instead of 0.0-1.0 as a personal preference.

Also when it comes to deactivating and reactivating you need to recall the information based on what I have set up in the video. So just construct does not recall the information, I found some issues with that during the time of filming and that solved it. At this time I could remake this into something better structured but this still helps showcase functionalities and how to do it :)

I appreciate the honest feedback and for you to take the time to critique the video I’d like to clarify I do not script or edit much or anything at all intentionally, as this is the style I enjoy the most and keeps me making videos. I prefer to communicate and showcase as I do, mistakes occur and I want my viewers to see this as well. I enjoy learning and sharing unreal with everyone and will keep this as enjoyable as I can to continue my UA-cam. The style may not be for everyone and that’s quite alright.

I’m installing UE5.0 to take a look right now and will respond either later today or tomorrow 🫡

Correct! You only need to implement the interface in the blueprint that is require to receive the messages.

Love to hear it! Happy to help all devs 💪

This is on the radar to do as well 😉

Hello! I do not provide Animations nor provide the assumption that I will provide any or teach how to create animations. The blend space in this video is from the free Epic pack and is only used as an example: marketplace-website-node-launcher-prod.ol.epicgames.com/ue/marketplace/en-US/product/animation-starter-pack. This video is to strictly show how to set up the technical portions of couching that other tutorials have left out. At this time, I would recommend to learn "Motion Matching" instead if you're using UE5.4 demonstrated in Epics sample here: marketplace-website-node-launcher-prod.ol.epicgames.com/ue/marketplace/en-US/product/game-animation-sample

PS: I am using enhanced input.

Ah I know exactly the issue, I'm currently looking into what would be a great blueprint solution and will follow up on this comment once I have one. Only responding since its been 4 days and don't want you to feel forgotten :)

@@MrButiier Thanks a million for even considering looking into it!

For future reference if anyone struggles with this issue; use the following console commands when/where needed: CommonUI.AlwaysShowCursor true/false AND CommonInput.EnableGamepadPlatformCursor true

​@@smarton1600 Thanks for following up here and sharing the solution until one in blueprints directly is available.

Hi Kora! 1. I would still highly recommend using Common UI in a project with keyboard/mouse only, the ability to add styles in widgets is extremely useful. Just under the settings of Common UI -> Platform Input -> Select whichever platform you're trying to support -> turn off "Supports Gamepad. 2. This one is a bit tricky, I haven't released a video of a solution to 100% cover ideal mouse/keyboard functionality but it is a solution right now that still does 95% of the job. I go over here here: ua-cam.com/video/aDoNLyUVy2o/v-deo.html

The issue I found with this was the keyboard didn’t work well with it either; I’m completely open to a better route, I couldn’t find a full working solution in blueprints anywhere but wanted to share this until I find one.

I found a solution but it's a bit tough to explain in text. I could send you a screenshot if you're interested. It's largely based on your approach though, so thanks for that!

@@CGSky I'd love to see it! I'd love to know for my own sake too haha. Glad I was able to help steer you in some direction, Common UI has been rather difficult to deal with while handling keyboard functionality.

@@CGSky Any update on this?