Player Name Tags Above Head - Multiplayer - Unreal Engine 5 Tutorial [UE5] 

thank you :)

Add a delay brother ... If your logic is ok this can solve it. You can try to get a variable in your pawn and update the overhead widget on every tick with that string. If you need a delay everything will work if widgets updates on tick, if not. there is a logic error.

Thank you ♥️

Hey thanks, what features for a menu screen do you search for that aren't shown already in other tutorials? :)

They usually make a menu screen where you can start the game but it's never dynamic. Like where should the character start exactly? Or when you're at the main menu. The background is just a picture not a dynamic scene.

@@tamerdrop Yes that's a good idea for a tutorial. Like a main menu where you can open different pages (settings, credits, ...) and invite friends to a party and then start playing from a map that you can choose in the main menu?

Exactly! :) @NiceShadow

@@tamerdrop Nice, I could imagine doing some tutorials about that

Thanks, I'll try my best for future videos 😀

yes I try to improve it in the future

Attach the widget component to a spring arm. Turn of the spring arm Do Collision Test and set Inherit Ptich, Yaw, Roll to false. The target arm length you can set to 0 or to whatever you want.

@NiceShadow Thanks for the answer, but I already fixed it by creating a new actor just for the widget and updating its position to match the players position on tick. Which approach do you think is better?

@@Nin10doLetsPlay ok, the spring arm approach is better I think

@NiceShadow I just tried the Spring Arm approach and it didn't work. Do I have to attach it to the ball?

I figured it all out. I had to add stuff to the on tick, but not much. If anyone has questions reach out.

@@javascripted_ I would be interested in knowing how you did it and what you added if you care to share :)

Thank you! If you click on the widget component you can set Space to Screen instead of World. Then you also don't need to make the widget component face the camera on tick anymore. But if it is set to Screen it also renders through walls.

@@NiceShadow and is there also a way to keep the widget above the player's head when the character gets respawned? because it doesn't attach to the player again after the respawn. the destroy actor function destroys the player together with the widget, but the respawn only respawns the player and the mesh but not the overhead widget

@@Headcrap So the widget is away after respawn?

@@NiceShadow yeah it is, it stays when the third person actor turned into a ragdoll before respawn, and even after respawning it's at the ragdoll's location instead of the freshly respawned player. If using destroy actor, the widget gets destroyed together with the ragdolized character and doesn't show up anymore after the respawn.

@@Headcrap Then you could also try to add a new widget component in your blueprint after respawning

It exists locally for every player. You can set a timer (Looped) on event begin play in the character. Then you can get the actor location of this character (self) and the actor location of get player pawn where you can get the distance between these two locations. Depending if the distance is bigger as a certain value you set the visibility of the name tag widget. The widget component itself has nothing to do with replication, it's just there because you added it by default to the character. Only the name value within the widget is replicated but this has nothing do regarding adjusting the visibility of the widget component.

@@NiceShadow is it too expensive? if i just set Collision ,it just can be enabled only for character whatever you want anyway and then when the other character is overlap with it then pop up the widget

@@leejames-f4z It's ok to do it so. But I would suggest that you constantly (for example with a timer that you set on event begin play) get the actor location (self) and do a distance node from that to get player pawn -> get actorlocation. And if the distance is bigger than a specific value it hides otherwise pops up.

if I remove the branch of check is locally controlled in set up local, it seems to be working, and using my steam name as well, otherwise it shows my pc name. is this a correct way?

It is better to store the data in the player state

@@iamagenius2646 How is that possible? When I store 'Player name' in Player State and switch Map Level it doesn't work

Thanks, I considered that already when creating this system. The repnotify function should trigger for new joining players so I don't know why it's not working... Maybe you missed a step

@@NiceShadow Thank you very much for responding, what happens to me is very strange, in the same onrep I put the name in the widget and in a text render and in the text render it works fine for everyone at all times... something strange about my character again thanks for the tutorial, greetings

yes it would but it would also render through walls

You can do that too. But screen space widgets render through walls and have always the same scale. For example if there are 2 characters nect to each other but 200m away from you, the name tags would overlap. To prevent that the nametag could be only made visible in a near distance. So both ways have pros and cons 😄

Maybe the node you grabbed was text box and not editable text box?

Is locally controlled means that you execute logic on the actor that can receive input on this machine aka this is not a simulated actor

Maybe try in your game instance to set the name variable based on your api result. So instead to set the name of the editable text box in the main menu

can you send me any tutorial for that am beginner Sory @@NiceShadow

@@adam4eissa I'm not doing individual tutorials

whyyyyyyyyyyyyyyyyyyyyyyyyyyyyy create one & upload it for everyone we need to learn @@NiceShadow

@@adam4eissa my time is limited and I've to set priorities

steam friends list? or what exactly?

a list of players connected to the server

@@nand-studios I'll create a tutorial about that

THANKS 🙏