I've been working at this on-and-off for a while. A Vine system that can accomplish real-world vines, different growth patterns, annual patterns, annual re-growth and expansion, etc.

The system is not intended to have a full year go by in 30 seconds like here (this is sped up 5x), but it can, as long as there aren't too many at once.

The system is intended to be for games that either want static vines, i.e. just bake it and use it, or vines that are realistic per the time of year, but change very slowly. So when the leaves fall off, they don't do it all at once but over a few weeks perhaps, dependent only on how many real world seconds "weeks" takes.

Vines are set up via a "Recipe" (Scriptable Object) system, which determines how they grow. A lot of GPU for the leaves and what not.

Vines can be trimmed at runtime, fruit can be picked (are game objects, separate prefabs, so you can code them as you'd like), etc.

I am exploring Animation Jobs as it is a requirement for a job opening. There's not much resources related to this out there. It's very interesting that I could manipulate animations with Burst compiled code.

take a look of what is coming in Quicktile !! running at 120 fps

Enemies are super simple right now - just testing some early behaviours out. I also added a slip/dodge mechanic where the player can slip out of the way of attacks. That move was inspired by the dodge in the last of us part 2, (which I love), I wanted it to feel like your slipping just past the blade instead of a big roll.

Its all still procedural with no animation clips... What enemy behaviours would you expect for combat scenarios like this?

It flies.

Continued experimenting with the clouds I shared here recently. Now squeezing a cloud makes it rain and grows a little tree on my desk. A hand gesture summons the sun, and water rises back into new clouds.

There are 5 different fairies with different skills and rarities.

Farm & Feast - We are a two-person team building a peaceful farming and restaurant management game in Unity. My town felt empty, so I added pedestrians and traffic. Here's the process:

• Took one of my customer characters and his walk animation
  
• Baked the animation into a texture (VAT) so the GPU can play it without bones
  
• Tested a single pedestrian on a plane
  
• Scaled it up: 10, 50, then 150 people
  
• Moved them into the actual game
  
• Added cars that keep their distance from each other
  

• Made the cars stop and queue when someone stands in the road

  Happy to answer any questions!

INKURSION is a narrative platformer in Unity 6 HDRP where you play a newly sentient octopus escaping a simulated universe. HDRP isn't exactly known for running on handhelds, so making it portable and Deck-friendly while keeping the look was one of our biggest challenges. Here's what actually moved the needle:
The octopus itself
Eight fully physics-driven legs is a lot of rigidbodies and joints aswell as procedural walking scripts for step reach. We tuned joint counts per tentacle, simplified collider shapes, adjusted solver iterations, and made sure segments sleep when they're not doing anything. The goal was keeping the floppy, reactive feel without the physics step eating the frame.
Mirrors
We use HDRP planar reflection probes for mirrors so the player can look at their octopus character, and rendering them every frame was brutal. Now each mirror only renders in realtime when it's actually on screen and the player is within a set radius. Even then, it doesn't capture every frame: it takes a snapshot at an interval, which is still smooth enough that your eye doesn't notice. This was one of our single biggest FPS wins.
Meshes and shaders
We cleaned up and LOD'd environment meshes, cut down shader variants, and simplified our heaviest shaders so the lighting still reads the same but costs far less on weaker GPUs.
Batching
Lots of foliage and repeated props, so batching was huge. Cutting draw calls freed up more CPU headroom than almost anything else.
Upscaling
On NVIDIA hardware we use DLSS, which lets low-end RTX cards render at a lower internal resolution and still look sharp. [On Deck we use FSR, since DLSS is NVIDIA-only.]
The result is a stable 60fps on low-end hardware with the bioluminescent look you see in the clip intact.
Happy to go into detail on any of it, especially the ragdoll and mirror setup. What's been your biggest win optimising HDRP?

Demo: https://store.steampowered.com/app/4767470/INKURSION/

Nothing really tricky, just didn't want to show the character's reflection straight up. Thought it would be eerie to have a creepy wavy ghost blanket where the player is for both a third person and first-person view.

I haven't posted anything in a while, but I've recently released my RPG Items package (a C# framework to handle items and inventories in Unity) for free on GitHub, and I'm continuing to release YouTube videos explaining in full and in-depth the implementation and usage of said package: RPG Items Playlist

So I just started using PrimeTween and what is the best way to code with it

• Code in the same component?
• Code in another component and call the methods from the "controller" component?
• Actions in controller component and in another component subscribe to them and play the animations

To me it seems like PrimeTween with it's methods already does a lot to avoid repetition of code with the sequences so it seems weird to me to separate it in another component so I would like to know how other people code

Left is the texture; right is the model.
Out of curiosity, I wanted to give a chance to an AI-generated model, downloaded for free, from a store. Despite the huge number of vertices, I kept trying giving a chance. After applying a decimate modifier, I considered the mesh "acceptable", +4k faces just to imagine a possible pipeline. Then I went to check the texture and "God no". The inhumane aberration of such a texture lead me here, sharing with you this time-wasting micro-experiment. Neural-generated meshes are very, very bad.
Happy continuation of the day,
Remember, kids, it is not worth

Feel free to comment and share your opinion :D

Hey guys, these are the VFX for my game. It's the first version, and I'd like to know what you like and don't like. What would you improve?

Thank you to the 2,000+ friends who downloaded and played the game. During this trial play session, we collected a large number of opinions and suggestions.

For example, regarding the position of the shipping box, some friends suggested it could be moved; some said the floor height could be increased to build a loft; there were also suggestions for modifying the operation keys to accommodate different operating habits, and for adjusting resource consumption, etc.

What moved us even more was that we saw some friends playing the game for over 200 minutes. This gave us great encouragement. Once again, we would like to thank all of you for your support of "Shelter Prepare".

Next, we will sort out and improve the problems and suggestions we have discovered, and prepare our official demo.

Also, the alignment adsorption was not obvious before. This time, we have further enhanced the alignment adsorption ability, and the cans and beverages are now easier to stack!

I'm solo-developing a power-grid game in Unity 6 (URP), low-poly style. If you overload a cable it burns out. The old version was one puff of smoke in the middle of the cable, and then the cable just disappeared. Nobody noticed it, so I redid it.

Stand-in cable: the real cable gets removed by gameplay right away, so I copy its rope points first and rebuild it as a bunch of short prisms (up to 120). They go from orange hot to ember to black char using MaterialPropertyBlocks, then shrink and sag until they're gone.

Burn front: every piece catches fire based on how far along the cable it is from where it failed. The far end always burns within 0.9 s. Smoke, flames, sparks and lights all use that same timing, so it's all one component.

The smoke took me three tries. I use opaque, flat-shaded low-poly puffs for smoke in my game.

1. First it was too small and too spread out, and looked like gravel. More puffs, 12 per metre.

2. Then the puffs spawned at full size and looked like boulders lying on the pavement. Now they start small and grow as they rise, and drift with the wind.

3. It still looked a bit like stone because of the sunlit facets. I gave each puff a bit of emission (about 45% of its colour) to soften the shading, and that's what finally made it read as smoke.

Fire and light: small unlit flames with HDR colours so bloom picks them up, plus up to 4 flickering point lights that move along with the fire. At night it lights up the ground and the bottom of the smoke, which honestly looks better than the flames.

How I tested it: I have a little test scene in Play Mode that overloads a cable on purpose and takes screenshots during the burn, during the day and at night. I mostly fixed the smoke by looking at those screenshots, because while it's moving you don't really see that it looks like rocks.

Can I do something more to make it better? Any ideas?

If you're curious about the game: steampage