UE5 | Modular Interaction System - Tutorial - Pt3 

It could be that the 'Range' value is set to 0. This isn't an issue as it should be fully black when 0 but during testing, it can be useful to set this to a higher number so you can see what's happening. I set the default to 45 so I can see a triangle shape. Hope this helps.

@@mpattym Thank you for your fast response. I tried setting the range to a higher number when previewing the node, the same as when you do in the video, however it remained black regardless of the value placed in the range default. All steps were followed exactly as shown in the video. I am currently using version 5.3.2 if that could be a factor?

@@novisient in that case it'll be hard to say what the issue is without seeing it. Feel free to jump on the discord to share a screenshot and I'll take a look when I have a few mins.

@@mpattym Will do, thank you!

Yes that's right. When you layer your blueprints, (as you would in C++) you want your heavy assets (skeletal mesh, sounds etc.) to be in child blueprints that only handle the visual side of things. In most cases, other blueprints shouldn't ever need to know about these but would if all the logic was in one blueprint. Making it so they only need a reference to the parent class means it doesn't need to know about the other stuff. There's nothing stopping you from creating a parent class that only contains vars and functions other actors can get or change and then create child BPs that adds the functionality and makes use of the variables. Another example of how I've used this technique is for handling the UI. I created a base UI manager that has a variable for what UI should currently be displayed. I then create a child of the UI manager that checks if this var has changed and updates the UI accordingly. Anything that needs to change the UI only ever references the parent and updates the var meaning it never knows about the various widgets and textures used.

@@mpattym damn thx for the complete answer that open more question and objectif for me but im sure i will aquire it with more experience and practice with ur content and other creator. Im thinking about what variable and function should go between the hierarchy of parent class and child that u make in ur logic and what is used by what.

Another question then lol, u use the function stored in the BPI_Interact called Set Outline State and u setup it in the AC_Interaction with the function UpdateInteractState, so its mainly what make it work for the bp_npc but u also need all the variable of AC_Interaction_Base to check the outline state right ? i didnt follow the part 4 vid of ur tutorial if u do something else in it. I think i understand wtf

@@efsfsesegsgesg8775 if you create a variable in a child BP, you can right click and move to the parent if you later find it needs to be in the main class.

@@mpattym nice ok i feel like i should try to discover the basic of c++ to be more comfortable

Setting the texture group to UI disabled mipmaps by default.

The UI side is handled inside one of the child components. Make sure You've added the correct one to the character. Additionally, make sure you've added the relevant actor component to the player controller. I hope this helps.

@@mpattym I fixed! Thanks. the problem was in the input configuration