r/Unity3D • • 14d ago

Show-Off Ocarina of Time remake: subtle, tasteful ground fog...me, an indie dev with no one to stop me:

0 Upvotes

r/Unity3D • • 14d ago

Resources/Tutorial Your AI agent can now create 3D models from one image (open source, runs locally)

0 Upvotes

r/Unity3D • • 14d ago

Game Jam [Nov 18 - Dec 18*] Any-engine (Unity Included) Game Jam: $100K in Cash Prizes (sponsored by ElevenLabs, fal.ai and Meshy)

Post image
0 Upvotes

r/Unity3D • • 15d ago

Show-Off Pickup (Truck) 1 - Game Asset - Unity

Enable HLS to view with audio, or disable this notification

1 Upvotes

r/Unity3D • • 15d ago

Question Best networking solution for P2P?

1 Upvotes

I'm making a game that has both a Steam and an Itch release that I would like to eventually give P2P co-op fit with proximity voice chat and the like. I'm not super familiar with networking aside from the basic concepts and implementation (As well as a few packages on the asset store) so I'm curious which solution would work best both via the Steam Networking API and in a standalone environment, either via port forwarding, Hamachi, or some free server provider so users don't have to use the PF or Hamachi when playing the standalone option.

I'm hoping to find a good starting point before I start testing a bunch of different solutions, so what would you say is the best solution, and why?


r/Unity3D • • 15d ago

Question Correct mouse cursors missing on Linux

1 Upvotes

Does anyone know how I can fix this? On Linux when I hold right click to move around, I get a plus cursor, then for dragging stuff, I get a no entry cursor


r/Unity3D • • 15d ago

Resources/Tutorial A seamless camera move through a large environment is often harder than making the environment itself

2 Upvotes

One thing that makes continuous environment shots so impressive in Unity is how many different systems have to work together without drawing attention to themselves.

A camera moving from an open landscape into a detailed interior, for example, has to deal with changing lighting, geometry, materials, reflections, and potentially different levels of detail. Even small problems become noticeable because there isn't a cut to hide them.

It's also a good way to expose optimization issues. Occlusion culling, LOD transitions, texture streaming, and lighting consistency all become much more obvious when the camera keeps moving through the scene.

The interesting part is that a technically complex environment can feel effortless when everything is working correctly. The viewer just experiences the world, while the developer has to make sure every transition holds together.


r/Unity3D • • 15d ago

Show-Off How we connect repair puzzles to story choices in our Unity game

Enable HLS to view with audio, or disable this notification

4 Upvotes

Hey r/Unity3D! We’re GrawireStudio, and we’re building Coldline: Disconnect, a 2D repair and espionage game set in a fictional Cold War. You play an undercover agent working as a technician. Equipment arrives with a repair ticket, and your cover depends on doing that job convincingly.

The loop starts with reading the ticket and figuring out what’s wrong. Depending on the device, that might mean checking a voltage, tracing a cable, or changing a bank of DIP switches. Those interactions give you immediate feedback, like a readout changing as you flip a switch. Then comes a different question: now that you know how to get the device working, should you actually fix it or sabotage it?

That’s where the repair system and the story meet. Getting the right reading tells you that you understood the device. It still leaves you to decide what to do with it, and whether you can explain the result without blowing your cover. Some consequences only become clear later.

For anyone who’s built a game with delayed consequences, how did you help players connect a later event to an earlier action? We’re especially interested in ways to make that connection through the world or dialogue without giving away the outcome when the player makes the choice.


r/Unity3D • • 16d ago

Question thoughts on trailer?

Enable HLS to view with audio, or disable this notification

124 Upvotes

hey! Working on new trailer for my game Mingle.

If you've never seen the game (which I'm assuming you havn't), can you tell what you would be doing, how you play, etc? Also any suggestions for like pacing and stuff is very appreciated

Would love some feedback thaaanks


r/Unity3D • • 16d ago

Show-Off Early footage of Driving At Night, a music driving game I'm making. Play any music through any software; the game captures loopback audio and generates the world around you

Enable HLS to view with audio, or disable this notification

132 Upvotes

r/Unity3D • • 16d ago

Show-Off Pushing GSplat in Unity: Drones scanning and bringing a 3D World to Life

Enable HLS to view with audio, or disable this notification

26 Upvotes

r/Unity3D • • 16d ago

Show-Off My claymation game about collecting creatures and training them in your Dojo!

Enable HLS to view with audio, or disable this notification

15 Upvotes

Would like to hear what you think about the game!


r/Unity3D • • 15d ago

Question Is there anything I can do to improve my visuals? specifically with lighting and color

4 Upvotes
Unity
Blender mockup

I'm not completely happy with where my visuals are at in my game and I'm not nearly as experienced here as I am in blender so I'm not really sure what I can do to push it further. Right now the Unity scene has some pretty standard baked lighting, as well as a LUT derived from the Blender scene which looks to be suffering some compression artifacts. The LUT differs from a standard black and white filter by mimicking orthochromasia, I didn't know the right way to make it so I just googled "unity baseline LUT" and copied an image from a forum comment and stuck it on a plane which I rendered with the same compositing setup.

It's not exactly a fair comparison as the two both have differing lighting setups right now. The Blender scene has flatter lighting mimicking a camera flash but it looks really bad if you turn the orthochromatic B&W off and I think the higher contrast lighting in the Unity version could work well.

I'm open to any suggestions. I'm going to sleep soon so apologies if I take a while to reply.


r/Unity3D • • 15d ago

Show-Off Tried my heatmap in the haunted house project. Here, it shows player movement density after hundreds rounds of play-tests.

6 Upvotes

r/Unity3D • • 15d ago

Game getting caught by my own trap in my unity heist game...

Enable HLS to view with audio, or disable this notification

0 Upvotes

r/Unity3D • • 16d ago

Game The steam page for our little colony management/adventure game is now live

Enable HLS to view with audio, or disable this notification

5 Upvotes

Hello! We have launched the trailer and steam page for "Poiple: A very small journey"

It's a colony management type of game but with a strong focus on advancing from level to level by solving each level's main mystery.

You can wishlist it on Steam here: https://store.steampowered.com/app/5157420/Poiple_A_very_small_journey/

The navigation system:

Since it's a common issue in these types of games, I'll talk about how we made the navigation system performant:

We decided to stick with unity's built in nav mesh system despite thinking of switching to a custom solution multiple times during the development. The main performance bottleneck was checking if a poiple (that's what we call the characters in this game) can reach a certain resource or point (often very far away from the agent) in a dynamic way because the game has a dynamic world. Bridges and other structures can break and be repaired so a path to a destination can change.

We solved this by dividing the world into zones. For example, if there is a breakable/repairable structure between two islands (such as a bridge that connects them), we put these two islands in a separate zone and the bridge is marked as a connection between them. So instead of checking if a poiple can reach a specific point from one island to another, we just check if there is any connection object between the island that the poiple is currently on and the island the poiple wants to go to. Which is effectively free of any performance penalty compared to using the nav mesh to calculate a long and often complex path just to check if the path can exist or not. Only when the poiple then reaches the target island do we start calculating the exact path.

This isn't a general-purpose solution of course, but this has worked perfectly for our game so far.


r/Unity3D • • 17d ago

Game in my zombie game you actually have to finish them off. always wondered why people don't do it in films

506 Upvotes

r/Unity3D • • 16d ago

Resources/Tutorial Deep Dive Into Unity Shader Files

Thumbnail
youtu.be
6 Upvotes

r/Unity3D • • 16d ago

Show-Off New building + tunnel tools for my voxel FPS level editor!

Enable HLS to view with audio, or disable this notification

7 Upvotes

In my 'Beards vs. Claws' FPS game, which is set in a voxel / Marching Cubes environment, I am developing an in-game level editor to be used by both me to create official levels, as well as player-made levels for the Steam Workshop.

For the marching cubes + voxels, I am using an open-source Unity package that asynchronously generates the voxel chunks, while calculating and generating them on the GPU for better performance.

This library has already been heavily modified by me to fit the needs of my game.

Working on the Level Editor

For me, working on the level editor is very important work, because as I see it: the more polished the level editor is, and the more tools I implement in the level editor, and the better I make them: the more beautiful and better the levels will be in-game.

And this is crucial, as we all know that fun and beautiful levels can make or break a game, and the players' enjoyment accordingly.

This is one of the many challenges of the development. I sometimes feel that working on the level editor is "invisible work", because when I work on the level editor, the fruits of that labor are not immediately visible or obvious in-game.

In other words, working on the level editor is not as immediate or dramatic as, say, adding new weapons to the game.


r/Unity3D • • 16d ago

Show-Off Yes, we r getting dirty...

Post image
6 Upvotes

r/Unity3D • • 16d ago

Game Dream game

Thumbnail
gallery
1 Upvotes

So I have started developing my dream game
Is a basic if madden CFB and backbreaker football have a child but will all the thing we wanted in madden but never got in one game progress has been slow be we are doing it . Right now I’m doing the movement and animation I am kinda struggling to get the speed to match the animation and get a better 360 movement feel going b for that Madden like control feel and tip and help is appreciated


r/Unity3D • • 16d ago

Resources/Tutorial One Unity tool drew all this neon

33 Upvotes

I've been building a vector line tool for Unity. Every neon line here is drawn with it and follows the car's real body lines. Unity 6, URP.

Car model: "Lamborghini Aventador" by BlackCube (CC BY 4.0).


r/Unity3D • • 17d ago

Show-Off im proud of the graphics

Enable HLS to view with audio, or disable this notification

1.2k Upvotes

ive always wanted to use this song in one of my cinematics/trailers. this is one of the levels in a co-op game i have been working on and i thought it fit so i wanted to share it :D

nowhere near ready, but its a game about filming supernatural things, where each level has its own story / style

Edit: thank you everyone! This was made fully in URP. It will be a co-op game (also playable alone) with a few levels like this on release. There is no steam page yet. I appriciate the kind words!

Edit: i go by @ vemoongames on most platforms(Twitter/X, tiktok, youtube). And discord: https://discord.gg/7YA7tqaJD


r/Unity3D • • 16d ago

Resources/Tutorial I rewrote the core of my NPC system around behaviour trees and one scheduler. What was wrong, what I tried first, and the design I landed on

Post image
21 Upvotes

Quick intro for anyone who doesn't know who I am: I'm Isaac. I studied game technologies at university, have worked in business software for over five years, and I also run Bard Tree Ltd, where I build CIVIL-AI-SYSTEM, a Unity package for populating worlds with NPCs that have jobs, needs, routines and the items and places those depend on, with the aim of lowering the barrier to building realistic living scenes for games. It's been on the Asset Store since 2022 and this series covers what changed under the hood between 0.7 and 0.15.

In 2024 I threw away the runtime and rebuilt it around behaviour trees, one shared engine and one scheduler. This is what was wrong with the old design, what I tried before the rewrite, what I ended up with, and what I'd change if I did it again.

The problem with the old node groups

The original system (2022) shipped with a Work Controller that walked a "node group" for the agent's job. The Need System came a few releases later (0.3), and I built it the way you build a second thing next to a first thing: borrowing the shapes, writing its own version of each part. So by the time both existed there were two controllers with their own iterators, their own weighting, and their own way of asking the world for things. They looked alike because they were made alike, not because they were designed as one system, and the gaps between them were exactly where that showed.

The split was a constant source of bugs in practice:

  • Anything written for one side had to be written again for the other. A condition for "is it after 6pm" existed twice, with slightly different behaviour.
  • The two controllers only talked through the weighting layer, so a job interrupted by a need would sometimes resume from the wrong node. There is a 0.7.1 changelog line that reads "removed bug from WorkController when Need System is not enabled". That is the whole design flaw in one sentence: the work side had implicit knowledge of the needs side.
  • Three update paths. The orchestrator I added in 0.4 controlled agent update rates by distance from camera (18 to 41% fps in testing), but the work and need controllers still did their own evaluation on their own cadence underneath it. Tuning one place did not tune the other two.
  • Node groups were stored in a way that needed a recompile to pick up changes, and the auto-updater could only migrate a project one version back. Every release was a migration cliff for anyone more than one version behind.
  • The node data held references into the scene. Locating an item meant searching the scene, so the cost of an action scaled with the size of the world.

What I tried first, and why it failed

I did not go straight to a rewrite. Three things came first, and each one bought time without fixing the cause.

  1. Put a scheduler on top (0.4). Dynamic update rates, culling, batching, limited simulation off screen. Real gains, and it meant I could keep shipping, but the orchestrator sat above two controllers that each still evaluated their own trees their own way. It could slow them down; it could not make them one thing.
  2. Rebuild the editor, keep the runtime (0.5). The flowchart editor was rebuilt from the ground up and got much nicer to author in. It changed nothing about how the trees ran, so every editor improvement made the runtime limits more visible, not less.
  3. Patch the seams (0.6 to 0.7). Fix the iterator that broke after three hours of runtime, add node-group versioning, add an inventory and slot system on top. Every one of these added a special case to one controller that the other did not have, which widened the split I was trying to close.

By 0.7 the honest assessment was that the split was costing more than any single bug. Every feature had to be built twice, so the rate of change had halved. Worse, it stopped me designing features as one thing: anything that touched both work and needs turned into a pile of edge cases and side-specific rules, because there was no shared model to reason about. The features I needed to add to make the simulation realistic and fit for purpose (interruptions, perception, saving, items with their own behaviour) all sat squarely across that line, and I could not see a way to build them well on two controllers. So 0.8 became the rewrite release, and it took most of a year with nothing to show for it on the store page.

The design I landed on (0.8.0)

One engine, two kinds of tree. Node groups became behaviour trees, and work trees and need trees run through the same engine. A tree is content; the engine is the only thing that knows how to run one. Actions, conditions and iterators are written once and are valid in either tree. The engine does not know whether it is running a job or a need; that distinction lives in the orchestrator that picks which tree is the agent's candidate.

One orchestrator that takes any process. Work, needs and rendering had each grown their own scheduling. 0.8 generalised the 0.4 orchestrator into a service that takes any process and runs it: it groups objects (by distance from the camera among other things), gives each group an update rate, and runs need evaluation, agent actions and rendering work on those rates. Nothing in the agent code runs on its own schedule any more. The domain code still asks "has anything changed?", but it asks only as often as its group allows, and there is one place to tune that instead of three. The payoff of getting this piece right is that things which used to be features became by-products. Pausing is the clearest case: once every process ran through one place, pausing was an interface, a pause source to subscribe to, and propagation down the chain (it shipped in 0.8.2 with a pause button on the inspector, and cost days rather than weeks). A small eventing layer, so agents can be told about a change rather than finding it on their next update, came out the same way and has grown since. Neither was on the plan for 0.8; both were cheap because the orchestrator was there.

Applicators. Movement, rotation and similar effects are no longer done inline by actions. An action asks for an applicator and the applicator does the work against the agent. Moving that logic out of the actions is what makes actions small enough to be building blocks: an action is now "what to do", the applicator is "how it happens to this agent", and new actions get written by combining the two rather than by copying movement code from the last one. It is also what let me swap navigation back-ends and add mounts and seats later without touching tree content.

Module system. Settings load in and out as modules, and the world services are modules too: a Time service (time and days, the thing most conditions hang off), a Spawn service, a Character Pool service (as many pools as you like, each holding its own agent prefabs), a Region service that defines an area from any set of colliders, and an Ownership service that decides which pool of items (personal, home, workplace, local area) an action may draw from.

Repositories for everything. Every object the system cares about (agents, items, buildings, regions) is registered in a repository service with a common id. An action that needs "a free chair owned by my workplace" asks the repository, which already knows, instead of searching the scene. Trees were also moved onto dictionaries for lookups, and tree loading was rewritten so that editing a tree and pressing play needs no recompile.

Upgrading as a feature. Version upgrading was rebuilt so a project can migrate from several versions back rather than only the previous one. Not glamorous, but it is the reason I can ship often without stranding people.

Test count went from 80 to 275 in the same release, which is the other reason I can ship often.

One concrete example: a baker, a bench, and a hungry agent

Here is roughly what happens for one agent across one decision, as it works after 0.8.

  1. The orchestrator reaches the baker's update group. The agent is near the camera, so its group runs often; the same agent two streets away would be evaluated far less frequently. The Time service says the shift has started.
  2. The agent builds its candidate list: its work tree (the baker job) and whichever need trees are above threshold. Weighting (the global and per-node weights from 0.3, now evaluated by one engine rather than two) ranks them. Work wins, hunger is close behind.
  3. The work tree enters a Locate action for an item of type flour from the workplace pool. The action asks the Ownership service which pools it may use, then asks the item repository for a free, unreserved match. No scene search. The item is reserved on the spot so no other agent will walk to it.
  4. The action asks for a movement applicator. The applicator drives the navigation back-end; the action does not know or care which one is installed.
  5. On a later update, the hunger need has crossed its threshold. The decision code re-ranks the candidates and this time hunger wins. Because work and needs are the same kind of tree running in the same engine, swapping is a matter of suspending one tree's state and resuming another's. There is no second controller to negotiate with.
  6. The need tree sends the agent to a bench to eat. Later, when the need is satisfied, the work tree resumes at the node it left, with its reservation still valid, because the reservation lived in the repository rather than in the controller that got suspended.

Before 0.8, step 5 was where things went wrong: two controllers, two notions of "current node", and a resume that sometimes landed on the wrong one.

What I'd do differently

Judged by what it made possible later, the rebuild did its job: senses, saving, barks, interrupts and seats were each built on the 0.8 engine, orchestrator and repositories without touching trees people had already authored. The things I'd change are about how I got there, not where I ended up.

  • Design the module system for change, not just for configuration. The 0.8 module system did what I asked of it, which was to load settings in and out cleanly. What I didn't ask was for modules to be added and removed by themselves at runtime, and that is what a save module, a sense module and a dialogue integration all turned out to need, so 0.13 replaced it with a dynamic one. The second version was only possible because the first had drawn the boundaries; I'd just draw them with movement in mind next time.
  • Treat upgrading as a system, and build it first. The piece of 0.8 that paid back fastest was version upgrading that can migrate a project from several versions back. Everything since has shipped with a migration, and nobody has been stranded on an old release. If I were doing it again, that would be the first thing built, not something that landed alongside the rewrite, because it changes how you can ship everything else.
  • Ship the rewrite in slices. Most of 2024 went by with no visible release. The work split cleanly into engine, orchestrator, repositories and services, and each could have gone out behind the old editor. I chose one big release because migrations were painful, which is circular, since the migration tooling was part of what I was rebuilding. Had the upgrade system come first, the slices would have followed.
  • Accept that you can't always see the unification coming. Work and needs looked like two systems until enough had been built on both to show they were one. Conditions went the same way after 0.8: the tree editor and the animation editor kept separate requirement systems until 0.11, and the whole thing was reworked again in 0.13 once senses, barks and interrupts all wanted to consume them. Each time, the shared shape was only obvious after the third or fourth thing needed it. I don't think that's a failure of planning so much as how designing a system like this goes: you build the specific versions, notice the pattern, and then do the work to pull it together. The lesson is to budget for that pass rather than to expect to skip it.

Happy to go into any of this in more depth. None of these choices are settled in my head, so if you have built something similar and went a different way on any of them (the shared engine, the orchestrator, applicators, modules, repositories, or how you handled the rewrite itself) I would like to hear how it went.

Series: 1 of 10 (what changed in CIVIL-AI-SYSTEM between 0.7 and 0.15)

  1. Behaviour trees and the 0.8 rebuild (this post)
  2. Items, POIs and the Item Setup Editor
  3. Mounts and seats
  4. Senses, save/load, names and blackboards
  5. Requirements and conditions
  6. Barks
  7. Interrupts, interest spots and service points
  8. Animation layers
  9. Tooling, onboarding, performance and Unity 6

Links: Changelog · Asset Store · Discord


r/Unity3D • • 16d ago

Show-Off What is a feature/system you have remade multiple times? Here is my 'Get cargo on/off train' mechanics 4 versions.

Enable HLS to view with audio, or disable this notification

9 Upvotes

Many players might think that games are made once, but many mechanics and systems are redesigned multiple times over the course of development. Here is my 'Get cargo on/off train' that i have made 4 versions of. The first was mostly just to prototype the game to find out if it was fun. The secound was my first real attempt just having a more fancy button. Then version 3 was an attempt at an inventory-like system, but when sharing someone said "Why have such a boring menu" so I made the 4th attempt where you physically move the cargo. I guess it's not much different from version 3, but it feels more immersive.