3D view
The project's 3D view: draws whatever the project gives it (scenes, 3D files, live positions, robots with any number of joints, several at once, fleets, rockets, vehicles), with the models, textures and sounds of the project's assets; live while a run goes on, then replays; numbers, events and controls on top.
How it works
One 3D view for every kind of project: it draws what the project gives it, through its inputs (scenes, 3D files, telemetry) and the project's assets (Data > Assets), so a new project needs data and assets, not a new view. With nothing to show yet, the view is an empty floor with the esacode logo at the origin and the axes rising from it (x red, y green, z blue).
Connect a scene (for example the Landing sweep's trajectories), 3D files (GLB, glTF, OBJ, STL, PLY, for example from the Library block) or Telemetry with positions: while a run goes on, the bodies it streams ({"drone": [x, y, z], "pad": [x, y, z]}) move live, smoothly and at real speed, and the recorded runs replay when it ends. With a scene and models together, a model can take the place of an entity (Model for).
What it draws comes from the project: the 3D models, textures and sounds in the project's Assets (Data > Assets: models/robot-spot.json, models/forklift.glb, textures/flashlight.jpg…) are the ones it uses, found by name; the view's own copies serve only projects that have none.
Robots (arms, hands, legs, mobile bases, whole cells: any number of joints, chains or trees, several robots at once): connect a robot model (esasim.robot/1, such as xarm6.robot.json.gz from xArm 6 model: joints with name, parent, type revolute, continuous, prismatic or fixed, xyz, rpy and axis, a mesh per link; or put it in the project's assets) and the live telemetry of the block that moves it: the joints channel poses it, with any number of joints ({"j1": 12.5, "j2": …}, a list {"q": […]}, or by name {"joints": {"shoulder": 12.5}}; degrees, or "units": "rad"), serial arms or trees (hands, legs, several arms on one body; revolute, prismatic and fixed joints), and several robots at once ("robot": its name), the twin channel poses a see-through copy (the digital twin beside the real worker), and the scene channel places the table, sheets with live pictures, cameras and the tool around it.
Orbit with the mouse, play back with the timeline, follow the drone. Lighting, shadows and the environment are set in the settings. Fly the camera with a 3Dconnexion SpaceMouse (3D mouse button, in Chrome, Edge or Opera), save pictures, and record videos of what you see or render the replay frame by frame (MP4, WebM or PNG frames) to download or keep in a dataset.
Fleets: a block that streams a grid world (esasim.warehouse/1, such as Warehouse fleet) and its robots is drawn as a hall with racks, stations and docks from the 3D files wired in (rack_d, amr…): robots move smoothly, show what they do with their light strip, draw their routes (Routes), colour where they wait (Heat map), and the run plays back on the timeline when it ends; click a robot to follow it, Cinematic for a slow orbit.
With inbound flow, receiving stations get a conveyor through the wall with the deliveries waiting on it, pack-out desks one where packed orders leave, and the shelves show the run's real packages, put away and picked one by one; Shelf use colours the faces by how often they were used and the packages by class. The hall has walls and a roof seen only from inside, with lights on the ceiling.
On top of any scene: Numbers shows live fields as tiles, the event channel's texts appear on the right, and Controls (the same lines as the Controls view, plus pick NAME to send a place clicked on the floor) puts buttons, sliders and choices in the bar that send commands to the running blocks. 3D files whose models have names (such as the anatomy of Labels to 3D models: a structure per model, grouped) get a Parts list: show or hide each part or group, find one by name, point at a model to see its name, click it to find it in the list, and cut through the models with a plane (across, front to back, side to side).
Several 3D files can be shown one at a time (Models), with a list to choose which, and without the floor (Show the floor) they float at the centre of the view.
With a soft-body model of the same case (Soft body model), the anatomy becomes soft tissue (each surface's vertices slide on the iso-surface of its structure's spheres as they move): organs sag, sway and push each other as you turn and move the body, the skeleton fixed and the skin around them; Soft tissue in the Parts list sets gravity, softness and damping (1: the tissue settles at once, without swinging back), pauses, resets; dragging turns the body (with Ctrl it moves it) so gravity and inertia act, and Pull drags an organ; organs collide with each other and with the bones (ribs too).
Set 3D mouse moves to The model and the mouse drag also turns the model, with or without soft tissue. The skin is see-through with a white sheen where the light glances off it, so the body's shape reads at a glance.
Anatomy looks wet: a clear coat that catches the light, over a procedural surface for each tissue (liver lobules, the spleen's grain, bowel folds, muscle fibres, the heart's folds in a darker red with patches of fat, the lung's air sacs, vessel walls, lobulated glands, and bone with a light grain, darker and yellowish where its surface is hollow or folded, measured on each bone's shape), made on the graphics card from the model's own coordinates, so it needs no texture files and stays on the tissue as it deforms (Tissue textures turns it off).
Metaballs (with soft tissue) shows the spheres of the soft-body model as they move (the chest wall between the ribs in muscle red), the anatomy see-through around them; each structure weighs what its volume of tissue weighs, shared by its spheres in proportion to their volumes.
Rockets: a block that streams a flight (esasim.rocket/1, such as Booster mission, or the attempts Booster landing: train replays while it learns) is drawn at Earth scale: the launch pad on the coast, the sea out to the curved horizon with its swell, the drone ship heaving and rolling, the sky darkening with height and the stars above the air; the booster with its grid fins and legs moving as flown, nine engines whose plume grows and widens as the air thins (shock diamonds low down), the entry burn wrapping the booster in fire, re-entry glow and soot, the landing burn splashing on the deck and lighting it, steam at lift-off, the exhaust trail, condensation at Mach 1, thruster puffs, the second stage firing its vacuum engine after separation.
Buttons in the bar orbit the booster, the second stage, the ship or the pad as they move (drag to turn, wheel to zoom, right-drag to pan), Tracking follows the booster with a long lens from the ground and Free leaves the camera where you put it (the 3D mouse flies it).
Camera puts a view on board instead (interstage, engines, grid fin, second stage, the ship's deck or the tracking camera), so several views of the same flight can sit side by side.
Cars on a ramp (esasim.car/1, from the Ramp stunt block): the stunt at night at a test site: black tarmac with one white line leading into a concrete crescent ramp, open on its sides, with its steel tower behind it, red light lines along the run-up that light up from the ramp out to the car and follow it, and red lights along a barrier mirrored in the tarmac; a follow spot high on a tower that keeps the car in a pool of light and throws its shadow on the tarmac or the deck, and the car's two headlights lighting the ground ahead; the stunt's own car (a licensed model shipped with the view, its glass black; a GLB or glTF car wired to the view takes its place) with its wheels steering, turning and riding on their springs, the white plumes of its cold-gas jets, the beams of its two laser rangefinders (the Sensors button), an air-system panel (the car from above: each nozzle lit with its thrust in % while it blows, the level of both tanks, the suction fans), and when it crashes it breaks: dents, wheels and panels coming off, shattering glass, sparks.
Its sounds (the Sound button; they start with a first click in the view): motors, tyres, the suction fans sucking air in under the skirts, a soundtrack that loops (the Music button turns it off; a recording takes it in), each jet on its own valve (placed left or right where it is on the car), wind, every wheel touching down and the crash.
A stunt run is sent whole ahead of time and played on the view's own clock, so it never stutters (nor does a recording of it). How far off the white line the car is, and how askew, shows in the panel once it has gone over the end. Broadcast-style cameras (Director, Chase, Orbit, Side; car: chase and car: side for fixed views).
Camera car: telemetry makes the view a telemetry window instead: charts of every sensor of the car over the run (speed, height and the laser rangefinders, distance off the line, attitude, turn rates, g, nozzles, fans and air), drawn up to the moment the stunt shows, in step with the other views, without 3D or sound.
A resupply drone in a village (esasim.resupply/1, from the Resupply drone block): a Mediterranean hill village built from the block's layout (plastered houses with flat roofs behind parapets, windows with shutters, doors, balconies, awnings, bougainvillea, water tanks, solar heaters and dishes on the roofs; a mosque with its green dome and minaret, a water tower, a telecom mast, olive groves, palms and cypresses, walled yards, parked cars, lanes, paved plazas, street lamps and their wires, hills all round), lit by the hour of the day (the sun's place and colour, dusk, night with lit windows, the street lamps and the moon) and the weather (clear, haze, overcast, rain with wet streets, dust, fog).
The heavy quadcopter carries its casualty-care kit from the base (a pad with its lights, a windsock) to the medic's plaza (an orange marker, a strobe, green smoke drifting downwind, a field tent), lands, leaves the kit and flies home; its rotors blur as they speed up, its lights flash, it blows dust off the ground when low.
Sensors shows the numbers (its GNSS: a good fix, jammed, spoofed or caught; how well its cameras navigate, its navigation error, landmark fixes, the battery), a map (the way flown and where it thought it was, the jammed area, the landmarks), its 26 range beams and a ring where it thinks it is. Captions say what happens as it happens; GET READY, 3-2-1 and the result appear in every view and in recordings.
Cameras: Director (cuts by itself), Chase, Orbit, Top, Free; village: chase and village: top for fixed views. Sounds: the four rotors, the wind, the rain.
A humanoid robot learning to walk (esasim.humanoid/1, from the Humanoid block): a Unitree G1 (a rigged model by KenzoDkohno22T, CC BY 4.0, shipped with the view), a Unitree H1 or an Apptronik Apollo (their MuJoCo Menagerie models, shipped with the view), whichever the block trains, every link placed where the simulation puts it, walking down a lane in a test hall (polished concrete, ribbed walls, light bars on the ceiling, soft shadows) with a start line and a marker every 5 m.
While it learns, an episode is replayed now and then; with Walk it walks live, steered from the bar (speed, heading, reset). A drive line in Controls (drive) puts a pad of buttons in the bar, held to drive the robot (forward, back, turn, step aside, stop), and drives it from the keyboard too (W A S D or the arrows, Q E to step aside, Space to stop), sending drive = {x, y, turn}.
Push in the bar is a hand: it stays on (the pointer an open palm) and each click on the robot pushes the part clicked, the way the camera looks, until Push is clicked again or Esc. Arrows on the floor show what it is asked to do and what it does, its footprints stay a while, each step makes a thump and a fall a louder one (Sound).
The esacode logo and the EsaSim name are painted on the hall's long walls, and the logo on the floor in a few places. Sensors shows its speed asked and done, the turn, how far off the line it is, the height of its pelvis and the load on each foot.
Cameras: Director (cuts between side, front, follow, low and crane shots), Follow, Side, Front, Orbit, Free, Robot's eyes (the depth camera in its head, where the block puts it) and Depth camera (the distance it measures, red near to blue far); humanoid: follow, side, front, eyes and depth for fixed views.
When the block sends a course, the ground is built from it: a rectangular circuit whose lane runs round rounded corners, with a square of bumps (rubber granulate, the hollows dark), a concrete ramp up to a plateau and down again (grooves across it, yellow-and-black edges), a square of blocks of different heights in steel edging, a square of moving tiles that rise and fall each on its own rhythm (in step with the simulation), a concrete staircase up to a landing and down again with a yellow nosing on every step and handrails, and a square of smooth ice in a steel frame; or a playground (the block's Playground): a sandbox in a timber frame whose sand keeps footprints, a pool of water with ripples spreading where the feet go in, gravel, stepping stones, curbs and a few steps, each named on the floor; inside it a training yard of four flights with their riser heights painted and coloured; each part named on the floor.
The lane leaves the rough squares, the tiles and the stairs bare; the cameras follow the circuit's turns and ride up and down with the robot; Sensors says what it walks on and shows the elevation map its policy reads (dots on the ground: cyan level, orange higher, blue lower).
Camera humanoid: telemetry makes the view a telemetry window instead: charts of its speed and turn (asked and measured), its height above the ground and the ground under it, its attitude, gyro and accelerometer, the load on each foot (with when each is down) and the angles and torques of its legs, the last 20 s live or the whole episode in a replay, beside a board of all its joints (each angle within its range, each motor's torque against its limit), in step with the other views, without 3D or sound.
Inputs
| Input | Takes | What it is |
|---|---|---|
Scene or 3D filesscene | 3D scene or Files or Stream json, gz, glb, gltf, obj, stl, ply | A scene (esasim.scene/1 JSON), 3D models and point clouds, a robot model (.robot.json.gz) and/or live telemetry; a soft-body model (esasim.softbody/1, from Soft body model) with the anatomy of the same case; or a rocket flight (esasim.rocket/1) Takes several connections. |
Settings
| Setting | Default | What it does |
|---|---|---|
Environmentenvironment |
outdoor | One of: outdoor, studio, night |
Qualityquality |
high | One of: high, balanced, fast |
Show the floorfloor |
on | Off: models float at the centre of the view, with no ground |
Modelsmodels |
side by side | Several 3D files: all of them side by side, or one at a time with a list to choose which One of: side by side, one at a time |
Tissue texturestextures |
on | Anatomy: each tissue gets its own surface, computed on the graphics card (liver lobules, muscle fibres, bowel folds, the heart's fat, the lung's air sacs, bone darker in its hollows…). Also a switch in the Parts list |
Show the metaballsmetaballs |
off | Soft tissue: draw the spheres of the soft-body model moving with the tissue, the anatomy see-through around them. Also a switch in the Parts list |
Show the gridgrid |
on | |
Show trajectoriestrails |
on | |
Playback speedspeed |
1 | From 0.1 to 20 |
Model formodel_for |
empty | With a scene and 3D files (for example from the Library block): the scene entity the first model replaces, such as drone. Entities can also name their model in the scene ("model": "quadcopter.glb"). |
Live channellive_channel |
empty | Positions streamed while a run goes on are drawn live. Leave empty to use any telemetry item with positions ({"drone": [x, y, z]}), or name its channel, such as pose. |
Robot: joints channeljoints_channel |
joints | Telemetry channel whose items carry the robot's joint angles in degrees: {"j1": 12.5, "j2": -30, …} |
Robot: twin channelghost_channel |
twin | Joint angles of a see-through copy, such as the digital twin beside the real robot |
Robot: objects channelscene_channel |
scene | Objects around the robot: {"units": "mm", "objects": [boxes, sheets with live pictures, cameras, the tool]} |
Robot: behind real time (seconds)delay |
1.2 | Live data comes in batches: a small delay keeps the motion smooth From 0.2 to 10 |
3D mouse speedmouse_speed |
1 | How fast a 3Dconnexion SpaceMouse moves the camera. From 0.1 to 5 |
3D mouse movesmouse_mode |
The camera | The camera: it flies as the cap moves (push to go forward, twist to turn). Move the scene: the scene follows the cap instead, as if you held it. The model (3D files): the model turns around its centre as you tilt and twist the cap, moves as you push it, and comes closer as you pull it; the camera stays. One of: The camera, Move the scene, The model |
Numbersnumbers |
empty | Live fields shown as tiles: channel.field=Label:format, separated by commas (format time or %), such as kpi.orders_h=Orders / hour, kpi.avg_order_s=Average order:time. Empty = none (a fleet shows its own). |
Events channelevents_channel |
event | Items of this channel with a text appear on the right, newest last |
Controlscontrols |
empty | One per line, as in the Controls view: button LABEL · slider NAME MIN MAX START [STEP] · select NAME a,b,c · switch NAME · text NAME · pick NAME (then a click on the floor sends NAME = [x, y]: a cell of a grid world, else metres). A control named like a live field follows its value. |
Controls: channelcontrol_channel |
control | The controls send {"control": NAME, "value": …} on this channel, like the Controls view |
Fleets: show the routesroutes |
on | |
Fleets: show the heat mapheat |
off | |
Cameracamera |
free | Rockets: free gives the orbit and tracking cameras with the buttons in the bar; the others fix this view on a camera on board the booster, on the second stage, on the drone ship's deck or on the ground, for a wall of views of the same flight. Cars (esasim.car/1, such as Ramp stunt): car: chase and car: side fix this view on a camera behind the car or on the side of the ramp. Resupply drones (esasim.resupply/1, such as Resupply drone): village: chase and village: top fix this view behind the drone or straight down over it. Humanoid robots (esasim.humanoid/1, such as Humanoid): humanoid: follow, humanoid: side and humanoid: front fix this view behind, beside or in front of the robot; humanoid: eyes shows what the camera in its head sees, humanoid: depth what that camera measures (distance in colour), humanoid: telemetry makes the view a window of charts of its sensors and a board of its joints. One of: free, onboard: interstage, onboard: engines, onboard: grid fin, second stage, drone ship deck, tracking (ground), car: chase, car: side, car: telemetry, village: chase, village: top, humanoid: follow, humanoid: side, humanoid: front, humanoid: eyes, humanoid: depth, humanoid: telemetry |
Where it runs
In the browser, on the flow's View page and in the run's results, in a sandbox without network access. It needs no worker.