The documentation is being updated. There may be incomplete sections.

Portals and Chokepoints

Portals

The portal node is a unique concept in graph-based applications. Like a "wormhole", portals allow you to connect nodes across vast gaps (or short ones) without visible connections. They not only improve your quality of life, but also dramatically change how you think of and use graphs.

When using the Infinity Graph, Portals can be used to connect nodes across different graphs.

Any output port in a node can be converted to a portal. You can create a portal in two ways:

  • Drag Out a connection. In the menu that shows up, select Make Portal.
  • Select one or more existing connections and press Ctrl + P to convert the connections into portal connections.

Once a portal is created, a small tab with the port's name will be visible next to the node.

You can connect to a portal in multiple ways:

Drag and connect to a portal like you would connect nodes normally. It will be converted to an invisible connection.

Drag Out a connection and you will be presented with a list of available portals organized by graphs. Select a portal to connect.

Drag Out a connection and type \ when the menu shows up. This will present you with a searchable list of all available portals.

Once a portal is connected, a tab showing the name of the portal will be visible on the target node's input port. The color of the tab represents the node type of the portal.

You can rename the portal node to change the name displayed in the portal tab.

To disconnect a portal from a target node:

  • Ctrl + right-click the node. You can select the port you wish to disconnect from the portal.

To convert the portal back to a normal node:

  • Drag Out a connection from the portal and select Remove Portal. Any connections to other nodes in the same graph will be converted to a normal connection. Connections to other graphs will be deleted.

Chokepoint

The Chokepoint node is a special node whose sole purpose is to help avoid re-connecting many nodes, while adding no memory overhead.

Often a graph ends up with natural chokepoints - a single node that is referenced by several other nodes. If at a later point you want to modify that important node, you would need to reconnect all the connections. This can be awkward, time consuming, and dangerous in some situations.

In this example, the second Erosion node is the chokepoint. It feeds several other nodes, while being a critical junction in the terrain's creation process. It is more or less the "last" node in the terrain creation.

The easy solution is to interject a Chokepoint node onto the important node. You can hold Shift while drag-dropping a Chokepoint on to the Erosion node to interject it and have Gaea reroute all connections. See Node Workflow for more information.

Now everything is routed through the Chokepoint, allowing you to experiment with the Erosion node later, and only reroute a single connection when needed.

The Chokepoint can be further organized by making its output a portal. You can select all the outgoing connections and press Ctrl + P to turn them into portal connections. This is especially useful when working with multiple graphs.