CASTING DEMYSTIFIED - CAST TO WIDGET COMPONENT - UNREAL ENGINE - UE4 - UE5

preview_player
Показать описание

Рекомендации по теме
Комментарии
Автор

looping through all actors then casting will consum a lot of player pc resources, which hurt the frames and performance in general
use interfaces which only send the information you need instead of casting the entire blueprint or widget.
there is couple of useful tutorials on interfaces and how to use them,
they are confusing in the beginning but once you understand how they work your game performance will be super smooth in any pc even low budget once .

DoctorMGL
Автор

Idk why but blueprint communication is important but most tutorials spend 5 minutes on BP communication... It's literally impossible to do much w/out it tho so thank u for dedicated video.

Wild-Coma
Автор

Blueprint communication is stupid. I learned C# before this blueprint crap. But it makes no sense that if I have a widget with properties within it, I can't pull those properties within a blueprint. All these tutorials have me making 50 different widgets all linking together when I should be able to simple call the variable with all the noodles. Casting for instance. If I cast to a specific Item, there's should be no worries of ambiguous references, as the variable I pull is from a specific instance of a specific item, but instead it apparently wants me make a separate object reference to something I still cant figure out.

chrishayes