Docs menu · Projects & graphs

Documentation

Projects & graphs

Project tabs

The tabs in the top bar are projects. Each project is completely separate: its own graphs, cook cache, frame range, frames per second, undo history and file. Projects never see each other, so an AI working in one tab cannot touch another.

  • + creates a new, empty project. New in the top bar does the same.
  • Click a tab to switch. Hover it to see its file, number of graphs and nodes.
  • Double-click a tab to rename it.
  • × closes the tab. Its autosave stays on disk.
  • Open loads an example or a .tsr file into a new tab.

Graph tabs

The tabs in the node pane header are the graphs (networks) of the current project. A project starts with one graph called main.

  • Each graph has its own nodes and its own display node. The viewport always shows the current graph’s display node.
  • The camera is remembered per graph, so switching between a terrain graph and a house graph keeps each view.
  • + adds a graph (you are asked for a name). × on a tab deletes that graph and its nodes (after a confirmation; undo brings it back).
  • Graphs are also how you build reusable assets for subnet and for_each.

Splitting a scene into graphs keeps each part small and fast to work on: build the terrain in one graph, the village in another, the vegetation in a third.

Combine and graph_ref

When a project has more than one graph, the ⊕ Combine button appears. It asks for a name and creates a new graph containing:

  • one graph_ref node per non-empty graph, which brings in that graph’s output (its OUT / output node, or else its display node),
  • a merge that joins them, and
  • a null named OUT_<name> with the display flag.

Select a graph_ref to place its graph with translate, rotate (degrees) and uniform_scale, or to evaluate it at a different time with frame_offset. Edits in the source graphs flow through automatically. A combined graph tab is marked so you can tell it apart.

The same thing as graph ops
[{"op":"network","name":"scene"}, {"op":"current","network":"scene"},
 {"op":"add","type":"graph_ref","name":"ref_terrain","params":{"graph":"terrain"}},
 {"op":"add","type":"graph_ref","name":"ref_village","params":{"graph":"village","translate":[0,12,0]}},
 {"op":"add","type":"merge","name":"combine","inputs":["ref_terrain","ref_village"]},
 {"op":"add","type":"null","name":"OUT_scene","inputs":["combine"],"display":true}]

Saving and opening

  • Save (Ctrl+S) writes straight to the project’s current file. The first time a project is saved it asks for a file path. Save As (Ctrl+Shift+S) always asks, pre-filled with the current file, and saving to a new file renames the tab. A bare name like harbour is saved as %USERPROFILE%\Tessera\scenes\harbour.tsr. An “Untitled” project takes the file’s name.
  • Open loads a bundled example, or a .tsr by full path.
  • A .tsr file is JSON: every graph, node, parameter, wire, comment and the frame settings. It is small and easy to share or put under version control.

Autosave and session

Every open project is autosaved shortly after each change to %USERPROFILE%\Tessera\projects. The list of open tabs is kept in %USERPROFILE%\Tessera\session.json, so the next start reopens exactly the tabs you had, with their latest state, even if they were never saved to a file. Caches (including simulation caches) live in memory and are rebuilt after a restart.

Autosave is a safety net, not a backup: save projects you care about to a .tsr file. See Support for how to back up and reset.