Hi everybody! I hope the previous episodes have piqued your interest and that you're motivated to learn more tricks for rendering a 3D scene in 2D shaders. As you may have noticed, so far we've been able to change the camera's position, but not the direction it's facing, meaning it was fixed straight ahead, which has been somewhat limiting. In this video, we'll solve this problem, so that by the end, we'll be able to aim the camera anywhere or even set it up as an orbiting camera. So, let’s do it.

How is it? I'm eager to hear any and all feedback.

If any of you are on macOS, I could use your help testing out the add-macos branch. What's currently there is just me guessing at what might work.

Hi everybody! And welcome back to our miniseries dedicated to rendering 3D scenes in shaders using the ray marching method. In the third episode, we will bring the previously static scene to life – adding combinations of objects, rotations along different axes and pivots, multiple lighting sources, and morphing using the so-called smooth minimum.

I have instances of this area2d object that spawns and is added to a group dynamically. when they collide I want them to say their name and the group they are in. right now they report their name but not their group and I can't figure out why, when they instantiate they report the group they are in so it looks like they're in their group but when they collide the group is missing.

var type_groups = [ "pluto", "moon", "mercury", "mars", "venus", "earth", "neptune", "uranus", "saturn", "jupiter", "sun" ]

func set_type(t): type = t

 undefined

        # Adjust for paths or hierarchy
    var shape = get_node_or_null("CollisionShape2D")
    if shape:
        shape.scale = Vector2(type_sizes[t] * 5.5, type_sizes[t] * 5.5)
        
    var detect = get_node_or_null("Area2D/CollisionDetection")
    if detect:
        detect.scale = Vector2(type_sizes[t] * 5.7, type_sizes[t] * 5.7)
        detect.add_to_group(type_groups[t])
        print("added to group: ", type_groups[t])
        
    var sprite = get_node_or_null("Sprite2D")
    if sprite:
        sprite
  

Hello!

So I installed an addon and saw that it made a license, readme and so on on the main folder. At the moment I didn't had those files there since I'm still very early on the game but shouldn't this files be inside the addon folder instead of the whole project?

The addon is as simple as check for the TODO on the comments but I want to do this properly. Where should I move this files of the addon? Or my License would substitute the one there if it's stronger?

Thanks!

Hi everyone! Do you remember the digital clock shader I created here some time ago? It was one of the first 2D shaders I used in a 3D project, and the result looked very usable. I think a shader simulating a classic analog clock could have a similar application, and that's exactly what we'll be creating today.

The demo for Robot Anomaly is out! Try it out and leave a review!

Hi everyone! In this video, I would like to demonstrate a shader that reacts to mouse clicks and movements. It is a variation of a shader displaying the Mandelbrot set, which I created here about a year ago. This time, however, we will enhance it by adding the Julia set at a point chosen by the user, and we will add more control elements, all of which will be controlled by the mouse.

Hello. I'm at a point in my learning where I see potential to make a big mess and want some advice before that happens. Particularly, how to organize game systems like inventory, damage calculation, level variables (eg. locked doors -> remain unlocked even after the level scene is reloaded).

For Inventory (consumable items, weapons etc), what I've done so far that seems to work is create a global script called PlayerInventory, within it is a list of every item as a boolean variable to indicate if the player has it or not. So now when the player travels through different level scenes, their inventory is persistent and any upgrades remain. Seems to work so far.

But how would you go about doing this for a locked door in a level scene? One way is to tie it to a key, in the player inventory - if "key" == true, "locked" = false. Ok, fine. What about a wooden crate that has been destroyed by the player? How would you keep track of the crate's destroyed state without it being tied to a "key

Hi everyone! In this video, I won't be showcasing any shader. Instead, I'll show you a trick for easily generating 2D sprites from 3D models in Godot Engine 4.4 or higher.

so I have the RB2D collision layer just for collisions, and I have a area2d collision layer for detecting contact between cloned nodes, but it doesnt detect the two earth nodes touching unless I set the area2D collision mask to layer 1 and I'm not sure why.

I just came across this great GDscript reference page and thought it might be handy for other beginners here. Cheers!

Hello everybody!

I have recently started to make small game jam project with friends using Godot. I previously had some experiences with it, but only on solo dev project. I really like it. I recommended it, and we used it on several project with git the following way: we split our project in a lot of small scene to avoid conflict, and everybody works on their branch. We communicate to be sure nobody is working on the same scene.

Now we face problems that could mean the end of our godot usage as a team: After some commit (I'll say the first one after a fetch), the uid of some random scene changes and will cause merge conflicts. It seems that there is no logic to it, and it leads to a lot of time lost, sometimes file corruption. The faulty commits are then extremely hard to track. Today we worked with godot 4.4 and it was even more painful. We lost a lot of our project.

I really want to continue to work with Godot, but I should say that my teammates were talking about learning other e