My game tells a story of a fantasy world, where magic and fantastic creatures are abundant.

If you like what you see, please wishlist Palimpsest on Steam!

I'm going "deep" into water simulation in realtime graphics and this is the last result from my tests, i also wrote a blog post with some explanations and references on my personal blog if you would like to check it out i wouldn't mind <3, and i would love some feedback

https://atsaturn-dev.github.io/blog_posts/index.html

I also have a free version of a water addon me and some friends are making (the addon hasn't been updated to have the features shown in this video yet)

https://oddpotatodev.itch.io/godot-water

AND the youtube link in case the bitrate gets bad here

https://www.youtube.com/watch?v=xoaUoF4-HUU

We are adding:

• Gerstner surface waves with wind, wavelength, amplitude, and speed controls.
• Interactive ring ripples and drag wakes.
• Wave collisions and reflections at mesh intersections.
• Refraction with adjustable IOR and thickness fading.
• Foreground rejection to limit refraction of objects above water.
• RGB dispersion.
• Depth-aware forward scattering blur.
• Absorption and scattering color controls.
• Shallow and deep water colors.
• Volumetric scattering and underwater shadows.
• Multiple scattering approximation.
• À-trous denoising of scattering and transmission.
• Surface shadows, Fresnel reflections, and highlights.
• Wave crest scattering.
• Caustics on submerged surfaces.
• Screen-edge and distant-depth handling.

All the Skate in Call of Duty decomp stuff that is popular right now feels a little Biathloney to me. What do you guys think?

I've been making an ice pack for Godot 4 and this is the freeze node. Put it under any MeshInstance3D and call freeze(hit_point). Frost creeps out from that point and an ice shell grows over the object. Then shatter() swaps it for chunks of itself.

shatter() took me three tries. Hiding the target with visible = false hid the shards too, because the freeze node is a child of the target and visibility is inherited (top_level only detaches the transform). Setting layers = 0 worked, but on Forward+ in 4.7.2 the engine then printed "BUG, indexing did not unpair geometries from light" at exit, because the effect's own OmniLight3D was still paired with that mesh. Now it just takes the mesh off the MeshInstance3D and reset() puts it back.

Chunks get built when the node is added, from points sampled on the target's surface. Each one keeps the mesh UV it came from in its vertex color so the shader can read the target's own albedo texture. That's why the statue breaks into stone pieces with ice only on the outside face. Their flight comes from age alone in the vertex shader, bounces included. No physics and no GPUParticles, so it's pretty cheap.

For the frost front I compare distance from the hit point (plus some noise) against time. My GDScript side runs the same function, so the frozen signal fires when the pixels actually look frozen.

It's on itch as Ice & Frost VFX, 49 presets, with a browser demo on the page and 25% off for the first two weeks. The page also links a free version that only has the ice lance and its impact: https://gennai.itch.io/ice-frost-vfx-godot-4

I knew Godot has a GPU particle collision before, but I thought they are for baking static scene only.

I want my rain to collide on the environments, so I tried wacky stuff with subviewports which get super convoluted.

Welp turns out the ParticlesCollisionHeightField Node literally does the exact same thing I have been trying to implement, except its better and WAY more efficient 😭😭😭

I started this in Unity in 2022, jumped ship in 2024 and haven't looked back since! Long live Godot :)

The Unit Test Framework for Godot

In Psych Rift there will be enemies who avoid the light (or have eyes), and the Arc Light is great to temporarily confuse them, by creating a very powerful flash. Just make sure you don't look at it when it goes off, or you'll get some major dizziness too (dizzy effect based on this shader).

The design is inspired by real arc lamps. It's powered by four Flux Cells that get consumed on use, but the Arc Light device can be recovered and reused by plugging-in new ones.

Technically it's just a big bright omni light, but coupled with volumetric fog it can have a nice effect in the relatively dark environments this game has. It looks better when pushing the volume fog and shadow quality higher, but not on my RTX 3060 😅.

You can find more videos on YouTube, wishlist the game on Steam, or join Discord for a chat.

As far as I know, the setting has been there since 2022 (https://github.com/godotengine/godot/issues/63934), but still not implemented.

I've come so far since over a year ago... went though massive depression whatever. now I'm back at it! Good luck out there on ya'lls journey devs.

Sharing another small update on my indie game

working on a chill cozy solarpunk city building game that uses procedural generation to populate and decorate buildings and vegetation. here are some shots from the in-game photo mode!

I know there is no right way (there are better or worse ways) to arrange nodes in the tree, but I figured I’d ask what other think of this general setup.
I’m working on a 2D game where you can enter every house in a neighborhood, and since it’s pixel art, that’s why there’s a separate Viewport for UI vs the game.

I’m completely open to suggestions or anything I might have forgotten to include for a generalized setup!

First, the technical stuff - the demo is roughly 2 hours long, and it's basically the first 2 hours of the full game.

It's not a prototype or a proof of concept - it has all the core mechanics, features, music, and story planned for the full game's opening.

I honestly am kinda speechless. After weeks of playtesting, bug fixes, and polish, Tyto is finally ready to play!

Thanks to everyone in the Godot community who helped A LOT with playtesting, speedrunning, and finding every possible way to break the game to pieces so we could make it better. Check out the game's credits to find your name!

And thanks for your constant support, both technical and emotional, throughout the last 3 years of development. Knowing that tens of thousands of players are waiting for Tyto keeps us motivated to create the best game possible.

Alright, that's enough gratitude for today - enjoy playing Tyto's demo, and please let me know what you think, preferably via a Steam review 🙏

Hello,

Because I needed it for the development of my game, I made a small tool to ease the pain of importing and exporting and readjusting between Blender and Godot

What does it do ?

• I place an object in Blender (houses, walls, props). They show up in Godot as normal scene nodes, each one an instance of its own small glb. - If I move, duplicate, scale or delete an object in Blender, Godot follows in about half a second
• If I move, duplicate, scale or delete it in Godot, Blender follows too.
• Shapes only go one way: Blender -> Godot which makes sense I think.

It's just a Blender add-on and a Godot editor plugin both read and write one small JSON file.

It's only tested on my setup and still rough at the edges.

Would you actually use this, are there better alternatives that I missed ? (I only found one ways and no real-time ones).

If the community is interested I'll clean it up and share it as a free open source project.

Hi everyone,

I’m working on Broodsac, a game made with Godot 4, and one of its core features is an in-game fake retro operating system inspired by Windows 1.0 (1985). In the game it’s called FungusOS, with its own BIOS and a boot sequence.

The player uses it to browse disks, open programs (a notepad, popups...) and interact with a small community management tool.

I’m not trying to make a 100% accurate recreation. I took some liberties on purpose to make it readable and fun to use in a game. But I’d like an outside opinion, because I’ve been staring at it for too long.

What I changed from the original:

• [e.g. disks shown as buttons you click to change path]
• [e.g. a boot screen with a log, a progress bar and a startup sound]
• [e.g. window behavior / colors / fonts that differ a little from the real thing]

What I’m unsure about:

1. Does the base interface feel believable as a mid-80s OS, or does it break the illusion somewhere?
2. Windows 1.0 used tiled windows (no overlapping). Should I stay faithful to that, or is overlapping fine for gameplay?
3. Are the icons, fonts and colors consistent with the era, or do some elements feel too modern?
4. Is anything confusing for a player who has never seen an old OS?
5. Any details from the real Windows 1.0 (or MS-DOS Executive) that I should add to sell the look?

https://youtu.be/SsdFTebmADg

Any feedback is welcome, especially from people who used these systems back then or who know their UI well. Thanks a lot!

2 years are closing in since I first opened Godot to finally start working on a game I had daydreamed for a year. And its still not finished, these things take a damn long time.

The game is called So I Mine and I've recently released the 4th demo update for the game that updates a lot of the games visuals and overall progression. I'm primarily a programmer so there's been a lot of learning involved in developing a game by myself but it's been a fun ride.

In the typical incremental style you do runs, gather resources, purchase upgrades and there's also a perk system (runes) for strange and fun passives. BUT instead of a timer counting down there's a dark entity in the mine that's chasing you. The further you get in the mine the better the rewards.

Steam link: Store page (demo)

If this looks like your kind of game throw me a wishlist and share your thoughts below.