Get started with ARC Tessera

ARC Tessera is a 3D creation tool in your browser. The work runs on your own device, so you can create and edit your own scenes on every plan. Co-editing a scene someone else created needs the Standard plan or higher (lower plans can view it).

Create a scene

  1. Open tessera.arcgroup.kr.
  2. Click Blank scene, or use Open scene (.atess) to open a saved scene. You can also start from a template made for the job: Sculpting opens a sphere to sculpt in sculpt mode, 2D Animation opens a 2D stroke object in front of a facing camera with drawing and the dope sheet on, and VFX opens a ground, a camera and a compositing tree in camera tracking. Organization templates published by your admin appear in the same row (Standard or higher).
  3. Use Import to bring in glTF, FBX, USD, OBJ, STL, PLY or .blend models. A .blend import brings meshes, materials, material nodes (with their links and node groups), images (including tiled images), vertex groups, shape keys (with value animation), modifiers (the kinds we also have — stacked on the unapplied mesh), armatures (bones, pose, bone animation, meshes they deform and objects attached to bones that follow them), collections, object placement, cameras, lights and location/rotation/scale animation. If an image is stored outside the .blend file, select the .blend file and the image file together in the import dialog (they're matched by name). Image files can be PNG, JPEG, WebP, BMP, TGA, TIFF or PSD (for PSD, the merged image Photoshop saves alongside the layers is used). An object in several collections is placed in the first one. Nodes, modifiers or settings we don't have yet and images we can't find are skipped or set to the closest value, and you'll see a notice. We checked .blend files saved by version 5.x; files saved by versions older than 4.0 haven't been tested. OpenVDB (.vdb) files come in as volume objects (smoke, fire, clouds): the density grid is drawn, and flame and temperature grids are used when present. Very large files are drawn with voxels merged to fit the screen. To bring in a frame-by-frame sequence (for example smoke_0001.vdb, smoke_0002.vdb …), select all the files together in the import dialog; they become one animated volume. Scene frame 1 shows the lowest-numbered file, and the properties panel lets you change the start frame, the file number offset and what happens outside the range (show nothing, hold the first and last file, repeat, or play back and forth). 3D scan point clouds in LAS (uncompressed — LAZ isn't supported yet), E57, PTS and XYZ files come in as point cloud objects. Point colors and intensity are imported too, and points far from the origin, such as survey coordinates, are moved so their center is at the origin (the original position isn't kept). Files with more than 2 million points are evenly thinned to 2 million. In the properties panel you can change the point size, convert the cloud to a mesh, or convert a mesh to a point cloud (converting back restores the faces). Point clouds are drawn in the view only; they don't appear in the render view or animation renders yet. From DXF and DWG drawings (DWG versions R13 to 2018), 3D faces (3DFACE), polyface meshes, polygon meshes, subdivision meshes (MESH) and 3D solids are imported. Each layer becomes a collection holding one object with that layer's faces, and collections for layers that are off or frozen are hidden. Each color becomes a material. Block references are expanded with their position, rotation and scale, and drawing units are converted to meters (drawings without units are read as millimeters). A MESH with a subdivision level becomes its own object with a Subdivision modifier at the same level. Curved surfaces of 3D solids are split into the same triangles the ARC CAD 3D view uses, so they can look coarser than the original surface. 2D objects such as lines, text and dimensions, and paper space, aren't imported; you'll see how many were skipped.

Make things

Use the modeling, sculpting, UV, materials, animation and physics tools. Objects someone else is editing are marked as being edited.

Use the Workspace menu at the top left to switch the screen to the job at once. Modeling opens edit mode, Sculpting sculpt mode, UV Editing the UV editor, Shading the material node editor, Animation the dope sheet, 2D Drawing stroke drawing with the dope sheet, Rendering the render view, Compositing the compositing editor, Camera Tracking the scene camera and Scripting the script panel. Switching workspaces doesn't change the scene. Click the pin button next to it to open this scene in the current workspace; the setting is saved with the scene, so it applies when others open it and goes along with organization templates.

When you polish an animation, turn on Onion skin in the object properties. The selected objects appear at earlier frames in see-through red and at later frames in see-through green. You can set how many frames to show before and after and the step between them, or show keyframes only. This setting isn't saved with the scene.

To rig a human character, select the character mesh and choose Add › Armature · Human (basic). Twenty-one bones for the head, spine, arms and legs are placed to fit the mesh, and the mesh is bound to the armature with automatic weights so it follows the bones. With no mesh selected, a 1.8 m armature is added at the origin.

To turn a drawing or logo into 2D strokes, choose Add › 2D strokes · Trace image and pick the image file. The dark parts of the image become filled closed strokes (with holes), placed on the front view plane at a height of 2.

For a shattering object, select a mesh object, set the piece count, seed and gap under Fracture in its properties, then press Fracture. The mesh is split into convex piece objects and the original is hidden. With Add a rigid body to each piece on, the pieces fall when you play the animation. This works on closed meshes only.

In a liquid simulation (Fluid modifier with domain type Liquid), turn on Spray, Foam and Bubbles to create small particles where water collides and rises. Particles thrown out of the water become spray (they fall), those on the surface become foam (they drift with the water and disappear when their lifetime ends), and those under water become bubbles (they rise); they show as points in the view. You can change how many are made, the foam lifetime and the bubble buoyancy and drag, and they are saved with simulation bakes. They don't appear in the render view yet.

In a smoke or fire simulation (Fluid modifier with domain type Gas), turn on Adaptive domain to solve only around the smoke, which is faster. The domain box grows and shrinks with the smoke, and the domain outline in the view changes to the box being solved. Adaptive margin is the number of extra cells kept around the smoke, and smoke thinner than the Adaptive threshold counts as empty. Set Additional cells to let the box follow smoke out of the domain by up to that many cells (faces with border collision stop at the domain). Adaptive domain is off for domains with noise turned on.

To make smoke or liquid flow along a path you choose, turn on Guiding on the domain. With Guide source set to Effector, the fluid follows the motion of objects whose effector type is Guide (guide effectors are not obstacles); with Domain, it follows the flow of the domain chosen as Guide domain. You can shape the large motion with a low-resolution domain and have a high-resolution domain follow it. A higher Guide weight keeps more of the original flow so it follows later, and a larger Guide size follows only large swirls and keeps small motion. Guide velocity factor multiplies the guide velocity. Where several guide effectors overlap, Guide combine (maximum, minimum, override, averaged) decides the result.

Press ARC AI in the toolbar to open the ARC AI panel on the right of the view (Standard plan or higher, in organizations where an administrator has turned on the ARC AI service).

  • Ask: Ask about the scene. Answers are based only on what is in the scene.
  • Nodes: Describe a geometry node tree; it is built and added to the selected meshes.
  • Material: Describe a node material; it is built and assigned to the selected objects.
  • Motion: Add keys that move, rotate or bounce the selected objects, or orbit the camera around an object. Key values are computed from the scene.

Results are previewed in the view first and are not saved. They go into the scene only when you press Apply, and one undo or Revert AI change takes them back. Anything from the AI that can't be used, such as nodes or objects that don't exist, is left out, and the panel tells you how many. AI search in the asset browser finds assets by meaning within the list you are viewing. Usage counts toward the same monthly allowance (or company API key) as other ARC AI features.

To reuse another armature's animation, select the armature that should receive it, pick the source armature and the frame range under Transfer animation in its properties, and click Transfer. Bones are paired by meaning, such as hips, spine, arms and legs, even when the names differ (for example, a character from another program), and hip movement is scaled to the character's height. It works best when both armatures have a similar rest pose, such as a T-pose.

To find poses where the mesh passes through itself when the armature bends, select the armature and click Run test under Rig test in its properties. Each bone with weights on the mesh is rotated around its X, Y and Z axes one at a time, within the Rotation range and with the number of Poses per axis you set, and the poses where the mesh passes through itself (Self-intersection) or through other meshes you pick (Intersection with other meshes) are listed. If a bone has a local-space Limit Rotation constraint, that axis only turns within its limits. Faces that already overlap in the current pose aren’t counted. Each row shows the bone, axis and angle, the number of intersecting face pairs and the size of the overlapping area. Click a row to show that pose in the view only, with the intersecting faces outlined in red (dashed where they’re hidden inside the body). The scene doesn’t change; click Apply this pose to put the pose in the scene. The test runs without freezing the view, and you can click Stop at any time. Meshes over 150,000 triangles or tests over 3,000 poses aren’t run.

Geometry node trees you use often can become node tools. Turn on Use as tool at the top of the node editor and a Node tools menu appears in the toolbar: in object mode it applies the tree to each selected mesh, and in edit mode to the selected elements. Inside the tree, the Selection (tool) node gives the currently selected points, edges and faces, and Set Selection (tool) decides what is selected afterwards. Each run is undone with a single undo.

To change a geometry node tree's values right in the viewport, add a Linear handle or Dial handle node and connect a Value node to its Value input. Select just that object and the handle appears: drag the linear handle's arrow along its direction to change the value by the distance, or turn the dial's ring to change it by the angle (in radians). The handle's position and direction come from the values connected to the node, so it can follow the shape. Hold Ctrl while dragging to snap to fixed steps; each drag is undone with a single undo.

The Transform handle node moves, rotates and scales a matrix value in the viewport. Connect the Transform output of a Combine Transform node to its Value input, select just that object, and X, Y and Z handles appear for the Move, Rotate or Scale mode chosen in the toolbar. The Local/Global button in the toolbar switches the handle directions: Local follows the node's Rotation input and Global follows the world axes. Turn off a translation, rotation or scale axis on the node to hide that handle. Set the Transform Geometry node's mode to Matrix to apply a transform value to the geometry directly.

When you drag a handle, the editor follows the gizmo's Value input backwards to find the value to change. It passes through add, subtract, multiply and divide, Combine and Separate XYZ, Combine and Separate Transform, conversions between numbers and vectors, and group node inputs and outputs, and then updates a Value, Vector or Integer node or an unconnected field. If it reaches a value that differs per element or a node that can't be solved backwards, it leaves the values unchanged and tells you why.

When a Geometry Nodes modifier is last in the stack, instances made by nodes such as Instance on Points are not realized; the viewport draws the same mesh at every location in one pass. Scattering tens of thousands of blades of grass or stones keeps the viewport responsive. Up to 250,000 instances are drawn per object, and beyond that the modifier shows a too-large error. The render view and animation renders realize instances, so they show the same error when the realized result exceeds 8 million points. If another modifier follows, or when you convert to mesh, apply or export, the realized mesh is used.

Automate repetitive work with Scripts. Click Scripts in the toolbar to open a text editor and a console. Texts are written in JavaScript and saved with the scene; they can read the scene and add, move or restyle objects. Run (Ctrl+Enter) shows the output and the returned value in the console, and the console line runs a single line right away (variables from earlier runs don't carry over). Scripts can only view and edit this scene; they can't reach other documents, the network or sign-in details.

The Operator log tab in the Scripts panel lists the edits you make in this window, in order: adding, duplicating and deleting objects, location, rotation and scale, names and visibility, materials, adding modifiers, and location, rotation and scale keys. Copy as script or Insert as new text turns them into a script that does the same thing; run it on the scene as it was when the log started to get the same result. Edits that can’t be written as a script (mesh edits, lights and cameras, changing modifier values and so on) are marked Not converted to script on that step. Undone edits drop out of the log, and changes from people editing with you aren’t recorded. The log stays in this window only and isn’t saved with the scene.

To do the same thing to many scenes, use Batch processing. Send an action and the scenes (a list of scene IDs or a Drive folder) to POST /api/tessera/v1/batches with an ARC Workspace API key to create a job. Supported actions are scene operations (ops), scripts (script), export (export — glb, obj, fbx and more, saved as Drive files) and render (render — one PNG from the scene camera, saved as a Drive file). The work runs in the key owner's browser, not on the server: open tessera.arcgroup.kr/batch and click Start processing, and that tab processes the scenes one by one while it stays open. See progress and results on the same page or with GET /api/tessera/v1/batches/{id}. Permissions are checked for each scene when the job is created: actions that change scenes need edit access, and actions that create files need download access. Render works only in browsers that can draw with the graphics processor.

Render

Switch to the Render view and the image gets better over time. You can save the result as EXR (passes). For glass, subsurface, volume and line art, see Use materials and render effects.

On an HDR display, with nothing selected, turn on HDR display › View in HDR in the right panel. Light brighter than white — the sun, lamps, bright reflections — then shows brighter in the viewport and the render view. Peak brightness sets how many times brighter than white the brightest light can get; anything beyond what your display can show is clipped by the display. This setting is saved on this device only and doesn't change the scene file or what others see. Saved images (PNG, video) are still saved at normal brightness; save as EXR to keep the bright values.

Save and share

Scenes save automatically, and Download › ARC Tessera (.atess) gives you a file. Volume objects and smoke simulations can be exported with Download › OpenVDB (the scene's first frame) or Download › OpenVDB (.zip) (one .vdb file per frame). Sharing, comments and version history work the same as other ARC files.

File › Save a record to ARC Synapse saves a summary of the saved scene (frame range, objects, materials, collections and more) as an ARC Synapse work record. The record is saved in My Drive where only you can see it; share it from Drive to show your team. Sending the same version again doesn't create a new record. Only members of the organization can use it, and the organization's plan must include ARC Synapse. Records are never saved automatically.

File › Create 360° panorama creates a 360° image (JPEG, 2:1) looking all around from the current 3D view’s eye position. The center of the image is the direction you’re looking, and the floor grid and handles aren’t included. You can download the image or save it to the scene’s Drive folder, and open the saved image in Drive to look around by dragging. On a phone, select Device motion and turn the phone to look around. In a VR headset’s browser, select View in VR. The image includes standard 360° image information (GPano), so other 360° viewers can open it too.

View on your phone

When you open a scene on a phone-sized screen, it starts in Phone view. Drag with one finger to orbit the scene, and use two fingers to pan or zoom. Pick an object from Objects in the bottom bar, or tap Comment and then a spot in the 3D view to comment on that spot. If you can edit, drag the Move, Rotate and Scale handles or enter location, rotation and scale values in Properties to adjust the layout, and use Duplicate and Delete. Tap Full editor for the rest of the editing tools, such as modeling, materials and animation, though they work best on a computer because of the phone's screen size and memory.

Add-ons

Install add-ons from Extensions › Add-ons › Get add-ons. When you install one, it asks for permission to view or edit this scene, and it only works within what you allowed. A single undo reverts what an add-on changed. For example, Scatter copies the selected object around it with small changes in size and rotation. Organization admins can allow or block add-ons in the Admin console, and review and publish add-ons only your organization uses. New versions arrive automatically by default; if your admin chooses Users update, select Update in Manage add-ons (Manage add-ons and your organization’s add-on repository).

You can deploy materials, node groups, node trees, and brushes to your organization as an extension. Turn on Mark as asset for a material or node group in the selected object’s properties, and use Save brush in the Sculpt or Texture Paint panel to save the current brush settings as a brush. Click Export as extension above the Assets panel and enter the extension ID, name, version, and publisher to download an extension bundle (.json). An admin uploads the file to the extension repository, reviews it, and deploys it. Assets that need files outside the scene, such as materials that use images, are left out of the bundle. After you install a deployed extension, it appears in the Assets panel’s library list as Extension · name, and Append copies its assets into this scene. Pick appended brushes from the brush presets in the Sculpt or Texture Paint panel. These extensions run no code, so they don’t ask for permission to view or change the scene.

Good to know

Speed depends on your device's graphics performance. ARC Tessera doesn't work offline.

Was this helpful?

Need more help?

ARC AI can find the answer in Help. If that doesn’t solve it, contact us.

Contact us

Related help