A short post about a small bug that was occurring when testing this feature.
Hi all, I hope you are all well!
Whilst creating the interaction widget for this project I ran into an error that meant the interaction feature didn't work as fully intended so I thought I'd share this with you so you can see that sometimes problems can occur when you least expect them.
For the sake of keeping this post short, I'm going to skip the creation process of the actual interaction function and skip to the debug, when everything was put together I enbaled the input when the game started which can be seen below and that worked well until I stopped running the game and I got an error back also pictured below:
So to apprehend this I moved the enable input feature to exclusively when the user enters the specific box collision connected to this blueprint which solved the issue since it only runs in exclusive instances rather than throughout the whole game!
Hopefully, this was somewhat insightful for those of you interested, and I hope you all enjoy the rest of your day!
Brandon
Comments