Unity scenes collect context that is hard to see at a glance.
A trigger volume belongs to one quest step. A spawn point is only active during a specific phase. A switch unlocks a door across the room. A designer leaves a note in chat, but the note is no longer visible when someone opens the scene a week later.
Custom gizmos can help, but writing a new gizmo for every gameplay system usually turns into its own maintenance job.
Here is a lighter way to think about scene annotations.
Start with What the Scene Needs to Explain
Before adding visuals, decide what kind of context is missing.
Most scene annotation needs fit into a few categories:
- labels for important objects
- notes or TODOs attached to a location
- links between related objects
- areas, ranges, or zones
- paths, patrol loops, routes, or flow lines
- warning markers for setup that needs review
The point is not to draw more things. The point is to make the scene easier to understand.
Keep Notes Close to the Object
If a note explains a specific object, attach the note to that object or place it at the location where the decision matters.
That is much easier to review than a note in a separate document saying “fix the cover spacing near the second arena.” When the note lives in the Scene view, the next person can see the context immediately.
Good scene notes are short and actionable:
- “Check player sightline after lighting pass”
- “Spawn group B only after alarm”
- “Cover spacing feels too wide”
- “Quest door depends on basement switch”
Show Relationships, Not Just Positions
Many Unity scenes are hard to read because relationships are invisible.
A button affects a door. A trigger starts a dialogue. A relay enables a group of lights. An AI route depends on several waypoints. The objects may be named well, but the relationship still takes time to reconstruct.
Links and paths are useful because they show intent directly in the editor. They answer “what is this connected to?” without forcing the reviewer to inspect every component.
Use Categories to Avoid Visual Noise
Annotations become useless if everything is visible all the time.
Use categories or filters for different review modes:
- level design
- AI
- spawn setup
- quest flow
- UI anchors
- TODOs
- warnings
- handoff notes
Then review one layer at a time. A clean AI pass, a clean quest pass, and a clean TODO pass are usually more useful than one scene view full of every possible marker.
Prefer Attribute-Driven Markers for Existing Scripts
Sometimes you do not want to add annotation components everywhere.
If a gameplay script already owns useful data, an attribute-driven approach can be cleaner. For example, an AI script might expose its patrol radius, a spawn script might expose a category label, or an interaction script might expose the object it unlocks.
That keeps the annotation close to the data that creates the meaning.
Save Custom Gizmos for System-Specific Debugging
Custom gizmos are still useful when a system needs precise visualization.
Use custom gizmos for specialized technical views such as nav data, procedural generation, physics traces, or bespoke debugging. Use general scene annotations for communication, design notes, review markers, and handoff context.
That split keeps simple notes simple.
Use a Scene Annotation Tool When the Pattern Repeats
If your team keeps adding one-off gizmos, leaving TODO objects in the hierarchy, or explaining scene relationships in chat, it may be time for a dedicated annotation workflow.
SceneSignal is built for this kind of editor-side scene readability. It supports Scene view notes, labels, links, areas, paths, waypoint editing, TODO context, and filters so busy scenes stay reviewable.
The goal is not to turn the Scene view into a dashboard. The goal is to keep useful context attached to the objects and locations where the work happens.
A Simple Annotation Workflow
Use this pass when a scene starts getting hard to read:
- Add labels only to objects that need explanation.
- Attach short notes to real scene locations.
- Use links for object relationships.
- Use paths for routes, patrols, and flow.
- Group annotations by category.
- Review one category at a time.
- Remove or resolve stale TODOs after each handoff.
Scene annotations work best when they reduce questions. If someone can open the scene and understand why the important objects are there, the annotations are doing their job.