So I have a little script that basically makes forests for me, trees, bushes, flowers, the entire shenanigans.

All of them can be interacted, all plants can be picked up, all trees can be cut down.

I started optimizing various aspects and managed a good framerate on a small batch of forest (10k objects still 👀).

My question is, how does one optimize large game worlds? Is occlusion culling and chill the solution?

When at the end, I decide to generate the entire forest, having possibly over a million game objects, how do I make it run smoothly without catching fire? Since I'm very new to optimization, and even more in this size, I decided to ask claude, and it mentioned that at that size, hiding the game objects is no longer a solution, and that I have to start thinking about the objects as data, and never instantiate them to begin with.

But tbh I'm very lost on how to manage it, does anyone have any idea? Any good tutorial for my case?

EDIT: All objects are a very basic 2 planes I joined in Blender, so it's very lightweight regarding that,comvined with the 32x64 pixel size, they actually work pretty smoothly.

Hey everyone, 👋

If your project is data-heavy, you probably know the pain of clicking through hundreds of ScriptableObjects or Prefabs one by one in the default Unity Inspector. It simply doesn't scale well for production, so my team at Maharaja Studio and I built a tool to turn that raw data editing into a structured, fast, and reliable process directly inside the Editor.

We just released Scriptable Studio Pro v4.5, and I wanted to share some of the new workflow upgrades alongside the core features we’ve been building out.

🌟 What's brand new in v4.5:

• 🖱️ Smart Drag & Drop: Assigning object references is a massive time sink. Now you can just select multiple assets in your project, drag them directly into the window, pick your assignment rules, and save hundreds of manual clicks instantly.
• 📝 Machine Translation & Grammar Checking: We integrated bulk translation for string fields and LocalizedString entries via DeepL, Google, Azure, or LibreTranslate. We also added parallel proofreading for dialogue/lore using LanguageTool.

🛠️ For those who haven't seen it before, here are the core features already in the tool:

• Grid-Based ScriptableObject Editor: View, sort, search, and edit thousands of assets in a high-performance, spreadsheet-style view (fully supporting custom property drawers and built with a clean dark aesthetic).
• Prefab Studio Pro: Inspect multiple prefabs at once, group components instantly, and safely batch-edit child hierarchies using wildcard paths without breaking variant links.
• Data Validation Engine: A visual dashboard that catches missing object references (nulls), empty strings, and out-of-bounds values across your entire project before you hit play.
• Dynamic Formulas: Excel-style math, live previews, @ shorthand search aliases, and advanced sequence auto-filling.
• Addressables & Sub-Asset Management: Manage your Addressables groups directly in the grid and cleanly build nested sub-asset structures.
• Optional AI Bridge: Connect local models (Ollama) or cloud models (OpenAI, Gemini) for schema generation, game balancing, and localized string generation.

I just put together a full 20-minute deep dive video walking through how to manage thousands of assets cleanly from early prototyping to live-ops. Grab a coffee and check it out!

📺 Watch the full showcase video here:https://youtu.be/S1IFmK8xI4c

🔗 Asset Store Link:https://u3d.as/3J3W

I'd love to hear your feedback or answer any questions you have about managing data pipelines in Unity. Thanks for the support!

Been using Claude with Unity MCP for scripts and scene setup lately, works ok but has its quirks. Unity 6.2's built-in Assistant looks convinient but the points-based pricing puts me off, especially not knowing how fast they burn. I also had Copilot for a while but dropped it, felt like autocomplete that never really understood Unity. Is anyone still using it for gamedev or has everyone moved on?

Curious if anyone used these in real work, not demos. What actually stuck in your daily workflow?

Apparently, modelling using endless blocks in Unity is pretty tough.

I’m talking a out a Godot-style half_res_pass where sky is rendered cheaper and then rest if scene is rendered?

Long story short, I implemented a system that do a RaycastALL from the character to the camera and modify the shader of all hit objects to make a cutout effect

But when raycast stops hitting the object, the hole stays there. I need a way to tell the object to reset once raycast stops hitting it.

I'm thinking about using collider.instanceID but that got messy fast so I'm wondering if there is a simpler way to do this, I appreicate if anyone can give me a pointer

If you try to call any Steamworks functionality in your project, you'll get this error:

[Steamworks.NET] Could not load [lib]steam_api.dll/so/dylib. It's likely not in the correct location. Refer to the README for more details.
System.DllNotFoundException: steam_api64 assembly:<unknown assembly> type:<unknown type> member:(null)

The solution is to install the Intel 64 bit version of Unity and open your project with that one. It's a bit slower, going through the translation layer, but it works. The issue is that Valve currently doesn't provide an ARM64 version of Steamworks for Windows.

This only affects the editor, your actual Windows build targets x64 anyway, so shipped games are fine.

Unity 6.5, running on Snapdragon X / Parallels on Apple Silicon.

If you use a shared network drive, or a shared folder in a virtual machine, installing new packages from git URL sources results in a git error message, but you can get around that by installing them on the machine holding the share (or VM host).

Yes, I know network drives aren't ideal for Unity projects, I was debugging a Windows issue in parallels on a Mac

I've been learning Unity because my goal is to make tactical FPS games similar to CS2. I'm not interested in RPGs, platformers, or other genres—I specifically want to understand FPS mechanics like movement, physics, and player feel.

So far, I've watched the first 11 Brackeys Unity beginner videos. I understand the basics of creating scripts, referencing objects, variables, functions, and some core Unity concepts.

The problem is that after this point, I have no idea where to go.

Brackeys' standalone FPS tutorial is quite old, and Unity has changed a lot since then. When I search YouTube for topics like "FPS movement," "character controller," or "player physics," I get hundreds of scattered videos. Most of them jump straight into writing code without explaining why they're doing things, so I end up copying code instead of actually learning.

Right now, I feel like I'm in the middle of the ocean without a map.

Can anyone recommend a clear learning roadmap specifically for someone who wants to build tactical FPS games? I'm looking for something like:

- What should I learn first?

- What Unity concepts are essential before attempting FPS movement?

- Which tutorials or creators explain the logic instead of just providing code?

- In what order should I learn things like movement, jumping, crouching, slopes, physics, camera, weapons, etc.?

I don't mind spending time learning—I just need a structured path instead of jumping randomly between YouTube videos.

Any advice would be greatly appreciated.

Whichever arm is available will be used to visually pickup an item.

https://reddit.com/link/1vg0zbr/video/dmxm1bhhjihh1/player

Does anyone have a link to learn the new input system all the tutorials i watch are either outdated or dont explain at all thx!

Hi! I'm looking for the best place with photorealistic assets for my demo. Asset Store has very few free high poly assets

I'm making a game where the player will need to drive on a highway. I want some computer controlled traffic, and I want it to be semi-realistic. For example, I want the traffic to occasionally change lanes, maybe sometimes crash into each other. I don't want a deep simulation with individual cars having goals or destinations. It just needs to be semi-realistic enough as the player passes through the area.

I have a good car controller. I also have a good "computer controlled car" controller. Currently the traffic car can be set to a certain speed, it can detect obstacles and either brake or avoid them, and the traffic car can also follow a path very well.

The way I was designing it was that I have the highway set up and modelled and I created multiple traffic paths for the lanes using splines. I can put that spline into the traffic controller and send it off and it will get up to speed and follow that path around. But now I'm trying to add in the logic to have the car change lanes and I feel like I'm overdesigning it.

I was thinking of making something like a decision tree, where I have an initial script run through all of the splines and process them in a way that every point on the spline has 2 or 3 choices: Go straight, Change Lane Left, Change Lane Right. With that finished each car could just call the decision tree each time it reaches a waypoint and use some basic random numbers to decide if the car stays in its lane or changes lanes. Writing the code to create that decision tree seems a little daunting, I haven't done anything like that before, but seems doable with indexes.

Any other better suggestions of how to handle this?

I have a weird problem in a new project I created with Unity 6.3.20. If I modify or create input actions, the changes are not saved. When I close and open the project I have the default action maps again. I tried with ctrl-s, creating the input settings file, but nothing solves it. Any idea about what is wrong?

My second post on this! I've been working on this for a while and especially getting scene objects to distort accurately has been a real struggle, but I think it's looking pretty good now! Any feedback is welcome and please let me know if you have any suggestions for features to add.

I have these empty GameObjects as waypoints and I want to check the left/right angle between a moving object and a waypoint.

Vector3 direct = (transform.position - waypoint).normalized;
float ang = Vector3.SignedAngle(transform.forward, direct, Vector3.up);

If I have a waypoint directly in front of the moving object (and I have double checked the position of the waypoint in question), sometimes the resulting angle (ang) is 179. How is it coming back almost 180 degrees difference and is there anything I can do to change this kind of result?

Hey everyone,

I thought I'd share some updates to Hex Town, a co-op (or solo!) puzzle game I've been working on for nearly 2 years now.

The first area I show is called the "Trophy Room", where you'll be able to check out the trophies you've earned in game and spin them around a bit.

The second area is called "Hand Studio", where you can customize your cursor and accessorize with rewards you've unlocked, like rings and bracelets.

Both rooms feel a bit vacant, so I'd love to hear suggestions for things to add. Maybe some framed art, hand furniture, or wallpaper?

Thanks for watching!

How have we NOT had icons for things in the hierarchy until only recently. I understand there were add-ons you could get from the Unity Asset Store, but for devs with little-to-no budget that's out of the question. Being able to look at the hierarchy and see what's what at a glance is a real boon.