Відео

Happy to help! :) This was my favourite Tutorial to make though :) Have fun and expect more great Tutorials!

You are just one of those toxic trolls that knows no better than this... use your Delays as much as you want :) make sure to have 100 of them :D

I believe it cost more, because you have to create the Blueprint Interface. This is just a Text tag.

@@bilalrasheed9725 You are welcome! I hope this Tutorial helped you.

Nope. Casting is for lazy people who are trying to find a reason to keep using it. Casting ruins the game performance, it's as simple as that.

@chankulovski but how would you do that task then?

@@SellusionStar Blueprint Interface, Event Dispatchers for example. With Casting is quick and easy, you've never thought WHY is that easy this type of Blueprint code? It's easy and quick, for the price of your game's performance. And that's ONE Casting, imagine having hundreds of them ... no no no...

@@chankulovski interesting idea. Also I like your tagging approach. But at the same time using interfaces or dispatchers for managing inheriting classes and using their specific functions feels really cumbersome. It's interesting though. By any chance, do you have a video about the measured performance impact of casting vs. interface/dispatchers?

@SellusionStar Thank you :) The thing is, to use Interface and Dispatchers is a bit more work, slightly more advanced, but the game will run better and chances to crash during gameplay are minimum, whereas when using Casting, chances are high your game to crash. People ignore this on purpose, because using Interface and Duspatchers requires more work (hence optimization). Watch this video and you will see how Casting is increasing the load of the game. As a side note, when I was shipping games with Casting, 4/10 times they crashed. Here's the Casting video: ua-cam.com/video/iVhEL-sWaC8/v-deo.htmlsi=WaXsbZ4v1XBvSJqx

@@swrcPATCH That's your opinion, there are others who wants to learn the proper way, and they will. However, Do Once is a great node, it's fine and safe to be used.

@@chankulovski I am not saying you are wrong. I just said the example so people can understand why the delay-node is bad, is a terrible example and not proving your point. The "proper" way would have a more understandable example in my opinion. All your example does is showing "why to use timers instead" but not avoiding "delay", you know what I am trying to say? Your video could be "use timers" but this example doesn't show why to avoid delay, it just shows why to use timers, do you get what I am trying to explain? Oh and good to know that do once is fine. I have not checked its implementation so I just wondered if it has some issues too.

@@Jueceovo Hey thanks a lot! I'm really happy the Tutorial helped you 😊

Thank you very much, I appreciate it! You will learn a lot from these Tutorials :)

Thanks Dan! I've also covered why we should never use Canvas Panel and what we should use instead. Hope you enjoy the Course, let me know if you need anything (the DMs are not coming through on Discord, I've tried to reply to your message).

Thank you very much!

I've researched what's missing the most from this topic, and I've made the Course for Beginners and Advanced users, it's definitely worth having it! Let me know if you need anything regarding this, I will be more than happy to assist you! Thanks again. Vlad

Obrigado Brasil! ❤

That's EXACTLY THAT ! You can have Input/Output and it will serve you as a normal Function, but with this method you can use that Function anywhere you want. But be careful, if you have the Character as an Input/Output, this will be the same as Casting, because that Character will load into the memory, so don't add Character in as an Input/Output. Also try to avoid Actor as an Input/Output.

@@chankulovski bro apreciate your time, i was watching your udemy and just discover that get all actors of class is bad i think im losed again i mean what if you placed like 100 turrets on the map? you need to get all of them right i mean what else can be done ? it is possible that the answer is if want to set something for all just make the main actor turrret a interface that has an event for setting something and then when called this event will be called also on all actor turrets placed ? and also if i want to modify only 1 of them i can use even dispatcher but the get all actors of class i dont understand if my answer its not the answer itself

@@TheSuperGameHD Hey man, you are welcome! Get All Actors Of Class is used if you want to manipulate multiple Actors of the same type. This is extremely bad for your game, because this node will search through ALL ACTORS IN YOUR GAME, and that can be very very expensive for your game performance. You can use Interface and Event Dispatchers yes, but definitely DON'T use Get All Actors Of Class.

@@rishikeshjaiswal3979 Hey thanks! It's not you, definitely! It took me long time to master them as well, luckily I had amazing teachers in Sweden (Futuregames Gamedev school), and they've explained to me properly. I will make more in depth series only for Interfaces, because they are perfect for Optimization. I can assure you, with creating simple things and learning them slowly, you will gradually increase the complexity and you will get better and better.

@@chankulovski Yes Vlatko! Having access to good teaching is crucial. Even I am a Teaching Assistant for game development course at Purdue University.

@@DailyPaily I'm publishing new Tutorials often, and I will speed up the process even more, so expect a lot of valuable and rare Tutorials soon! :)

@@DailyPaily My apologies, but I didn't understand this?

@@chankulovski 12:53 Branch ---> Clear and Invalidate, you will save the 'is valid' node.

@@DailyPaily The Timer was there just to demonstrate how "IsValid" node works. There's another approach for this, but I have to make a whole new Tutorial because it's not that simple :) Thanks for your input, that was a nice catch!

@@chankulovski Cool !

Yes, definitely !

Thank you!

@@tuwumuch I explain in great detail why Casting is bad and you should never use it, check that Tutorial on my Channel. Casting is made for prototyping and quick test an idea. Only lazy people are using Casting because they don't want to optimize their code and spend few more extra minutes to do so.

@@chankulovski thanks for the reply but theoretically, if something will always be loaded in isnt it just simple to just cast? Currently I always cast if its directed towards the character or the gamestate/etc, but interface or tags for everything else.

@tuwumuch Those theories are invented by people who wants to use Casting, due to lazyness. To prove this, simply hover over the Casting node and read what it says.

@@chankulovski yes i saw your video it'll always be loaded. Character is always loaded though no?

@tuwumuch Yes

What do you mean exactly? You can spawn either with Timers from the Event Begin Play node (not with TICK!), or you can spawn them when you overlap a Trigger Box. If you spawn them with Timers, make sure to Clear And Invalidate Timer when you don't need to spawn them anymore.

Ok if you believe that

@@sutadoralive I'm really glad to read this, THANK YOU!

Third Person is my favourite to work on :) So definitely I will make Tutorials for this in the future. Probably for free on UA-cam. Thanks for your interest, keep an eye on the Channel, more Tutorials are coming soon.

@@chankulovski Nice, looking forward to it! Your spellcasting and magic system look amazing as well,if you have the time pls make tutorial for them too

@digitalwf852 Thank you :) ! That's the plan, to make Tutorial series for these Spellcasting in the near future!

@@newwonderer You can perform without Casting, there is a way around it.

Actor can perform with interfaces you just have set up you want interface to do you can set and get run event add remove pretty much anything with interface

@@MikeReed-r8r That's right!

Hey there, thanks for your comment! Try watching this Tutorial, hopefully it's what you are looking for: ua-cam.com/video/DmpRbWwJCzY/v-deo.html&ab_channel=Chankulovski If not, try to check my other Tutorials. Casting node is bad for your final game, and it's made for quick prototype and testing, there is almost always a way around it! :)

@@chankulovski Awesome I will do that... thanks a million for your quick reply!

@@cmulder007 Always! :) Let me know if this was what you were looking for, if not, I will try to explain in a comment, or make a Tutorial for it. Thanks again

That is also a great video... however in that example you are able to avoid casting because you know the object that you are going to be calling the function on is the player character (you check this with ==) and then you call GetPlayerCharacter ...... however in a more generic system where you want to check against ANY object that implements the interface, like for instance I_CanBeClicked.... and if the object does implement it you want to then call the ClickMe function defined on that interface, you still need a reference to the object as that interface.... hope that makes sense... I know there is a node to check if an object implements an interface but that just returns a boolean, I cannot find a way of calling the function on an abstracted object reference without a cast... however I guess a cast to will only increase the size of the blueprint by the size of the interface though so maybe not so much of an issue?

@@cmulder007 The node is called "Does Implement Interface" with a Boolean Return, but you have a Target to assign in that node, so you can still do things with it. You can always Call an Interface and avoid the Casting :)

@@MichaelBullo Thank you very much, I really appreciate it.

@@chankulovski Best of luck with the channel

@@MichaelBullo Thank you! Doing my best to push as much knowledge as possible, especially for beginners.

@@chankulovski Excellent. You are getting close to 1000 subscribers.

If you don't like it, DON'T WATCH IT! It's that simple. There are people who want to learn proper programming, so, relax...

I know what I'm teaching, that's why I'm teaching. Nothing is misleading. Everyone who says Casting is good or great, is either lazy or not knowing how much damage it causes to your game. But don't say misleading just because you love using Casting and don't want to hear about it.

@@muratkara9482 Thank you!

Well, for a small mini game, or something not that serious it's fine, yes. But this will become into a bad habit very quickly, so later when you want to create a bigger and better game, then you will have to learn Timers, so it's just not worth doing things twice. Better to learn at the beginning, so you don't have to bother about Delays.

Thank you very much for your kinds words! More Beginner Tutorials are coming soon :)

Thank you very much for your kind words, it means a lot! And I'm very happy that you love the way I teach :) I'm working on my next Tutorials, so I will write your suggestions and will definitely consider doing a Tutorial for it, will see :) Thanks again!

Exactly right! Especially if you are having multiple Event Ticks in different Blueprints, that's a total disaster of a performance!

@@chankulovski For real lol, I saw all the comments complaining so I had to leave a supportive one since anyone having performance problem's would honestly benefit a lot from this

@@ademonnamedburt1232 Yeah, of course they will complain. It's easy to call one node and do 10 other things for them, it's easy and convenient, but at what price? :) You know what they say "You cannot help a person who doesn't want to be helped". Thanks a lot for your supportive comment, it means a lot! P.s. another Tutorial is coming in the next few minutes :)

@@DevGods If so, then why does Timer exists? :)))

@@chankulovski Timer predates the delay node. Imagine having to create a timer and bind a delegate to it finishing every time you wanted to do something on a delay. Hence the delay node was made which wraps that logic up all nice and compact in a graph.

@@DevGods Nope. Delay node is made to quickly test and prototype an idea, and then should be replaced with Timer for Optimization. People adopted Delay as their Go To node because they are lazy, it's that simple. But I'm done proving this over and over again, everyone can believe what makes them feel good and they can do what they want with their code.

@@chankulovski Yea. Pretty much at the end of the day they both have a purpose. Delay is done async while timer is on the game thread. If you don't want to have to prove bold statements don't make them for clicks and views fam. This is the engagement you wanted when you posted this click bait title.

@@DevGods Find ONE of my videos where I'm saying "Please like and subscribe", or any word that says "Subscribe", and I will delete my Channel completely. All I care is to share Programming best practices and Optimization. Instead of being grateful for the hard work we are putting here, you are being jealous and toxic... have a great life.

You can use "Set Timer By Function Name". You have to create a Function and use it instead of Custom Events. This way, your code will be much cleaner and readable. But if you prefer to use Custom Events and Timers, you can create the Timers with Custom Events on the side, and then simply call the Custom Events' name to run the timer.

@@ryanoconnor7957 I've explained 1000 times why Delay nodes are bad, I've made a whole Tutorial about it, and people STILL don't listen... I'm done explaining :) anyone can use anything they want in their game. Their game will be laggy, not mine.

Delay node is not synced with the Delta Seconds Framerate of the players, and this will cause inconsistencies and unfair gameplay in Multiplayer. But I'm really tired of trying to explain something and people don't want to accept. If you believe Delays are great, use them a lot :)

@@chankulovski for multiplayer yep its not good but i saw ur way u can use switch to pass flow no need to make another timer with custom event and one clear timer variable. instead using this use switch to pass node flow. there is node called switch u can put delay in 2 flow in 1 flow it will pass. i think u take me in wrong way i just say their is other ways too.

@@chankulovski if delay doesn't use the manually modified player time delta, then that sounds like a bug in delay they should fix.

@@madpuppet666 They should not fix anything. Epic Games gave us tools to work and to experiment, they won't do the hard work for us, they won't give us the magic button everything to be ready for us.

@@chankulovski if user can alter timedelta, then the time used in Delay should work with that. if it doesn't its a bug, or it should be an option on the delay node to work with real time, or modified time. Otherwise the Delay node is useless.

Yes, just don't overdo it :) don't make it 100 or something.

Just check the "Looping" Boolean, and when you don't need the timer, just Clear And Invalidate as shown in the video.

@@TheSuperGameHD Hey man, I'm happy you like the Tutorials. For the things to work as you were asking, you should use Blueprint Interface. I'm not sure if this will help, but you can try it and let me know if it helped: ua-cam.com/video/DmpRbWwJCzY/v-deo.htmlsi=QcS72Bcj6aK8QX9Z The things you were asking are a bit complex, so I have to make a whole Tutorial for it, probably I will do in the near future. Thanks again.

​@@chankulovski Thats right bro , interfaces broooo, i will change now the rest of all casting sht , in sure my big project will run on windows xp with 4 gb ram or less xD

Now i understand that when i play gta v my 3080 grafics card the fans are always running and when playing the big game star Citizen the fans run only sometimes maybe in 1 hour of playing only 1 minute the fans are spinning thats amazing, and for the casting thing im hate it so much after watching your videos , but i was thinking if i want to test just something fast that will never be published i can just cast for testing so i think from hating it its more.like for testing , but when i think in the past vro casting was normal in my mind and now its just sht

@@RaulRadulescu You can use to quickly test something, but make sure that won't turn into a habit :) I'm using Optimized Blueprints even for testing, because if I like that what I'm testing, I will just leave it that way, I don't have to change the code 100 times :)

@chankulovski somehow bro i m envious that you showing this professional information for every nub for free like me

GREAT POINT! :) You can do that, that's even a better option. But if you have more Blueprints and more complex code, it will become "spaghetti" messy very quickly. Having the "Clear And Invalidate" ready in a Custom Event will give you more clear and tidy nodes, so you can call that Custom Event as many times as you want, while keeping the nodes tidy and the code optimized.

Yes you can, but that's not the point. This is what Delay nodes are doing to your PC: CPU overhead: Delay nodes introduce unnecessary calculations and updates, which can strain your CPU, especially in complex or resource-intensive projects. Frame rate drops: Excessive delay nodes can lead to stuttering or frame rate drops, negatively impacting the overall user experience. Open this Article and scroll all the way down to learn more: www.doppelganger1989.com/blog

Here's the thing... You can use Delays, you can learn how things work after few seconds, test an idea, prototype etc, that's totally fine. The problem is, this will easily become a habit and it's going to be VERY HARD to change in the future (as you can see many of the people who comment don't want to accept that Delays are bad and they are keeep using it, and their game suffer :)) Overall, if you are doing a very small Project, using Delays should be fine, but if you intend to become better and smarter programmer in the future, you should learn Timers and use them all the time (I never use Delays in my games, not even for testing or anything, I don't wanna see that node). So it's up to you :) Meanwhile, take a look at this Tutorial, maybe it will be handy for your Jumping mechanics: ua-cam.com/video/xeJUwXJUvZo/v-deo.html&ab_channel=Chankulovski

@@chankulovski Hey man, thanks for the extensive reply, really appreciate it! I see, so delays are really that bad huh? I'll try to translate everything into timers instead as you suggest, I'll also try to get more viewpoints on this topic from forums and such. In the meantime, I got your udemy course, looks very promising, has a lot of functionalities that are very interesting to me.

@@masterlkm You are welcome buddy, doing my best! Go to this page and scroll all the way down, I wrote an article with a breakdown points, which part of the performance is affected: www.doppelganger1989.com/blog In the meantime, extend your research as you said, always check multiple sources and opinions, and decide what do you believe and go for it. Thanks for buying the Course, feel free to message me any time if you need anything.

Yes, you can make things work with Delay, but the code won't be optimized, especially with more complex games or Multiplayer games.

@@chankulovski If you use a sequence node, then put the delay in sequence 1 and the code in sequence 2, i am pretty sure you get the same result, meaning the second code is executed in the same tick as the delay node.

@@FreeD00M I'm trying to tell you: Delay node is NOT OPTIMIZED NODE, and it's not performing the same as Custom Event with Timer. Watch the Tutorials, and if you still believe Delay node is better, it's your choice.

@@chankulovski I did watch it. I just suggested that a sequence node can be used for parrallization with the event timer or a delay node, thats all.

What do you mean to have two of those spheres, next to each other, to overlap, or? If you want to make an On/Off switch, you can make a Boolean Variable, so when you Interact with the Sphere you will check if that Boolean is True or False, then continue the code from there, depending on what you want to achieve next.

​@@chankulovski Hi, thanks so much for replying but just figured it out. Both buttons are working now. :) Combined some information from your other video "How to use Tags instead of Casting node | Unreal Engine 5 Tutorial" with some here and managed to get it to work. Just want to thank you so much for the great work. Made my life a hell lot easier :)

@@chankulovski Oh and not really for on/off switch but more an ignition switch and start switch. :)

@@N3DArtworks That's why you are going to be a successful developer! If you cannot find the solution - you've asked a question, then you've done your homework (researched even further from other Tutorials). I'm super happy to see people like you, gives me motive to continue creating unique content even more! Keep an eye on the Channel, more Tutorials are coming! :)

@@chankulovski Thanks man. You have no idea how much I appreciate the kind words. Honestly! I'll definitely keep on watching tutorials from you. Explain very well to the point I actually figured things out. Awesome content man! :)

Have you watched the video till the end, or just 10 seconds of it? That is causing the execution of the code to perform badly. Delay nodes are NOT synced with the user's computer Framerate, so it's not giving the same experience to every Player, because every computer has different Framerate. Timers are more complex solution and more optimized, that's why nobody bothers to optimize their code, due to lazyness. Also, even though I didn't mention something in the video, you should continue your research further. Let me help you with that, please check the link below. www.doppelganger1989.com/blog Scroll all the way down to read more.

To avoid waiting, use Sequence.

@@GMTechArt You can, but it's bad for your game. Doesn't mean if we can do things, that they are right things to be done.

Exactly right! That's because Delay nodes are not synced with the user's machine Framerate, so the Delay node will cause inconsistency and it will behave differently and unfair most of the times, especially in Multiplayer games! Timelines are also great, yes. Thanks for clarifying and sharing your experience :)

Canvas Panels are increasing the numbers of Draw Calls, and using another UI element is a better option IF the developer/designer wants to optimize their game, it's that simple. I am, and will continue teaching about why we should NEVER use some tools while making a game, because some tools impacts the performance. If you believe I'm offering a bad advice, don't watch the Channel, very simple thing.

Здравствуйте, я рассказал об этом команде движка Unreal и отправил им ваше видео, они очень пожалели и не поняли почему допустили эту ошибку, поэтому поблагодарили вас и сказали, что перенесут задержку на юнит и удалите его из движка Unreal в следующих версиях. Мы страдаем от этой ситуации. Мы разработали игру из-за задержек. В игре есть тысячи задержек. Мы работаем уже 5 лет. Спасибо.

@@AstrovoidInvasion Very funny 🤭 Also, I'm confused why you are commenting in Turkish and Russian languages :) but anyway :)

@@chankulovski We thought we were Russian

@@andrzejmikolajczyk9561 You are welcome! I'm super happy you find this useful :) more great Tutorials are coming!

Never. Don't use Delay nodes. Delay and Timer nodes are having the sam functionality. The only difference is in the optimization, Delays are not optimized, Timers are optimized. Also, it takes a few minutes of extra work to create Timers, but the code is optimized with them, but creating Delay takes just a few seconds, but the code is NOT optimized. Please always optimize your code, you will thank me later :)