Socket types

SceneCity has its own socket types and they have nothing to do with Blender’s sockets. The usual color codes you’re used to (yellow for images, blue for vectors and coordinates, grey for values etc…) don’t have the same meaning in a SceneCity node graph.

You should not connect a socket type to another socket of a different type. If you need to convert a socket type to another, you may use a converter node if such node exists. For instance there’s a node that can convert paths to curves.

Mesh data socket

_images/socket_mesh_data.png

Mesh data is SceneCity’s internal representation of a mesh. It contains the vertices, edges, faces, normals, UVs etc… Not to be confused with a Blender mesh.

Map socket

_images/socket_map.png

A map is like a grayscale image, it has only one channel, no color. But unlike an image, it is not a raster, it is continuous. It may be based on a precedural noise function, or based on a raster image, or mixed.

Texture set socket

_images/socket_texture_set.png

A texture set is like a PBR material, it’s a collection of images, each one for a different channel in the PBR workflow (and other useful maps). Ultimately they are meant to be output as images and used in materials (or shaders in realtime 3d jargon).

Objects socket

_images/socket_objects.png

A collection of objects.

Paths socket

_images/socket_paths.png

Paths are like polylines, they are a sequence of linked points, with a start point, and an end point. Unlike graphs, they cannot branch, meaning a point can only have 2 links at most: one before, one after. A point cannot be disconnected, except if the path has only one point. They are in 3d.

Curves socket

_images/socket_curves.png

These are similar in concept to Blender’s bezier curves. They are in 3d.