Видео

Thank you so much for this kind comment! I'm very glad you liked the video :)

Glad it was helpful, thanks for the nice and interesting comment! You're absolutely right that there are already a lot of tutorials on that topic - to be honest, my goal at the moment is to create a little gallery of typical Godot game dev tricks so that people can get all this info while staying on my channel, if they want ;) But I really like your idea of talking about spatial audio - I'll definitely add it to my to-do list! Cheers :)

@@minapecheux Perfect 🤩

Heya! It depends a bit on the complexity of your project, and on your personal preferences :) When I'm working on something simple, I like putting the sounds inside the scene because it makes it easier to "cut them out" if I want to test another piece of the gameplay. But if you already know you're going to have multiple scenes that reuse the same sounds, and/or if you want to have your audio sources play during scene changes (eg to keep the background music during scene switches), then it might be better to group everything in an audio manager Autoload scene. Hope it helps :) Cheers!

@@minapecheux I think it does! I’m making a pretty basic arcade high score style game, and I made an audio manager, but I honestly find it a little confusing and may not be necessary for this project, haha.

Glad you liked it! Good luck on learning the 2D tools, and thanks for the comment :)

You're very welcome, glad you liked it! :)

Thank you, glad you liked it! 😃

Thank you so much for the nice comment! I'm really happy you like my content :)

Heya! Sorry, not exactly sure what you mean :) Are you wondering about how to make the shader move in a more "frame by frame" way? or how to give it a more pixelated look...?

@@minapecheux no, more how to snap the movement to a grid, so when I press a direction button it moves 1 entire cell, not 1 pixel

@@jotaeagles Heya! If you want your user inputs to create a 2D top-view grid movement, you should probably have some variable in your code that defines the size of a grid cell, and then when you press the user input (eg right arrow key) you add/remove this value instead of 1 to the node's coordinates. (I was confused cause I'm not exactly how it relates to this video, sorry ^^) I hope it helps, cheers! :)

Thanks, glad you liked it :) Well I definitely have some 3D ideas too in my near-future-todo... and actually, your comment motivated me to bump those up a bit, so hopefully I should publishing some of those short 3D Godot tutorials next week :D Thanks for the support and suggestions, Cheers!

Thanks, I'm glad you liked the tutorial! :) Basically, what we want to do here is a euclidean division with remainder, dividing our total time by 60. So first, we get the number of minutes [m] by dividing the time by 60 and flooring it to nearest integer below (with the int() method). Then, we subtract this number of minutes from the total minutes (and keep in mind it's been rounded to the nearest integer, so it's not exactly equal to the initial value) to get back the remaining seconds. Hope that helps, feel free to tell me if something's still unclear! Cheers :)

I'd say about 2h blocking the overall idea, and then 1 additional hour tweaking the anims + improving the materials and lighting, give or take :) (But I also had already modeled most of the items for this scene beforehand in other projects!) Cheers :)

Heya! Thanks for the feedback :) Though, at least from what I understood and tested, the "Floating" mode is mostly a way to "simplify collision grouping" in Godot - meaning it will consider everything like walls, and not distinguish between floor, walls and ceilings anymore... but the logic does work even if you don't turn this on ;) But noted nonetheless, thanks! Cheers :)

@@minapecheux the grounded mode also gives access to the function `is_on_floor()`, `is_on_wall()` and `is_on_ceiling`. I like these short form videos targeting a single feature btw. But the new RUclips UI makes it a pain to navigate playlists!

@@AlainPilon Thanks, I'm really glad you like this new format :) And yup, I totally agree - the UI is a bit weird on that front... :/ hopefully it will get better one day!

@@AlainPilon Hey man! I'm trying to put together a beat em up style game, i got the player moving but since the 3d is an illusion the is not really a "ground" or I don't know how to set it up. Problem is, now I am at the "jump" animation, and I don't know to get it done. Can you suggest a tutorial? I didn't find anything, maybe it's too specific :)

Glad you like it, thanks for the nice feedback! The code I show here indeed expects that you sent 1 piece of data max - but note that this data can be as complex as you want, so typically you could create a class or a tuple that holds your various properties. And of course, if you prefer, you could also define equivalent functions in the EventManager class that expect the exact list of properties your game uses (here I tried to keep it generic but you can adapt specifically to your own use case)! Hope it helps, Cheers :)

@@minapecheux Thank you for your answer :) I found that out and at the end I used the Version with a Extra Class. Tuple members are accessed by position (Item1, Item2, etc.), which can be less readable and harder to understand compared to named properties in a custom class. Since I just started Unity and C# I thought its better with the Extra Class so I dont lose Track of what is what :D

It doesn't really have a name... except perhaps for the title of this video :)

Heya! I think the Avoidance will only "'auto-work" as long as the agents are using the NavMesh (and you've properly configured the avoidance option of the navmesh and the agents based on your models :) ) - when they start to cross the jump links, they'll use a simple translate code that kinda ignores the others... To solve this, I would probably create a sort of queue at the entry/exit points of the jump link, so that they can only be one agent crossing it at a time. Hope it helps :) Cheers!

The idea is to use one or more procedural noises (with Blender's built-in Noise Texture nodes in the shader) to create somewhat realistic relief/biomes/colour zones, and also optionally pass this noise through extra effects like bumps/displacement. I then layer that with some other objects for the clouds + atmosphere. If you're curious, I made a ~10 min tutorial of the whole process :) ruclips.net/video/6EHodZYUzYI/видео.html Hope it helps, cheers!

Heya! Hmm perhaps you should check that you properly setup the structure of your behaviour tree (ie the hierarchy of nodes)? Have you properly put the task nodes as children of your Sequence/Selector parent node? Hope it helps, cheers! :)

Hey, Thank you. I checked and found issue. It is possibile make Selector as random choice? If not what different algorithm can I replace behaviour tree?

@@bogumiwyrwa216 Heya! If you want to make your inner flow nodes random, eg the Selector or the Sequence, you "just" need to shuffle the order in which its child nodes are processed. (Meaning that in the Evaluate function of your Selector class, before you do the for or foreach loop, you randomise the order of the children to iterate on) The point to keep in mind however is that, depending on the type of random you want, you might to store the randomised order for a while... Since behaviour trees are run continuously every frame, if you rerandomise every frame you might get a pretty frantic behaviour. For example, you could store the current randomised list of children until this node is not executed (ie the tree goes another route and doesn't execute this branch). Hope it helps, cheers!

Heya! Absolutely right :) Here I preferred to make things very explicit and show that the different nodes need to point to the same resource, which is why I extracted it to an actual project resource file - but you're totally right that if you're building your UI as you setup this system, it's quicker to just duplicate your first button reference. Thanks for pointing it out! Cheers.

Heya! I'm currently working on some game projects on the side, but they're not yet ready to be shown to the public sadly ^^ I'm focusing this channel on game dev tutorials :)

Heya! Hmm, the "mapping" of C# to GDScript should pretty one-to-one, using snake_case instead of PascalCase... if you want, you can send me more info about where you're stuck via email (at mina.pecheux@gmail.com) and I'll try to see if I can help :) Cheers!

No need for that anymore, after many attempts I managed to figure out what the problem was haha

@@Nikczemnik-km2lv Glad you found a solution! Cheers :)

Hello! And thanks a lot for your feedback :) Although I do understand your comment, I used to do that before and had remarks going the other way... but most importantly, this new technique allows me to create those tutorials way faster and get a better work-life balance, so I think I'm gonna stick with this system for now ^^ Hope it makes sense, cheers!

Nobody owes you anything, if you don't know how to learn, you'd better change your profession. What do you want, to have your bed made and fed too? Average

@@yusarimahubara Heya! While I understand your sentiment, please be kind with the rest of the community in the comments :) Everyone learns in their own way and at their own pace, and I'm always interested in hearing out suggestions from everyone (though I ultimately decide what I feel is more appropriate for me ^^)! Thanks for understanding, cheers :)

@@yusarimahubara oof It seems i hurt someone's feelings😁 Calm down

@@taravata8637 I am calm. You are the one who should be worried about your present and future. A mediocre man who weighs 200 kilos and is not able to learn how to use a computer. There are no jobs waiting for you other than appearing in some netflix documentary as a burger king victim.

Glad it helped! I think you'll need to change the ForceMode used in the _Fire() method - you can check out the table shown around 10:10 for more info on the different ForceMode values :) Hope it helps, cheers!

Thanks, glad you liked it! :) Yup, you're totally right: depending on the size of your tree, it can be nice to use the root. Here, I relied on the direct hierarchy to be as modular as possible, but this is definitely a pretty specific example case... Hope it clears things out, cheers :)

when I scaled, it got too big (almost kilometers), that the object was not visible in perspective mode - solved

Thanks, glad you liked it! That's a nice idea, I'll definitely add it to my to-do - and hopefully I'll get some time to work on it soon-ish ^^ Thank you for the suggestion, cheers!