Settings

Overview

Settings are stored in the browser, not in the model. They follow the person at the machine rather than the twin: a colleague opening the same link sees their own settings, and a delivery can lock individual tabs so an operator cannot change them.

Open them from the gear at the bottom of the left bar. The tabs scroll horizontally when the panel is narrow; the arrows at both ends move through them.

The viewer version and build number sit at the bottom of every tab. Quote that line in any support question — it identifies the exact build you are looking at.

Visual

The largest tab, and the one to reach for when the model runs sluggishly or looks wrong.

Group	What it holds
Visual Presets	A named set of all visual settings. Save your own with Save settings as preset
Render Mode	Shaded or a reduced mode, plus how strongly the environment lights the scene
Environment / Floor	Background, floor on/off, floor brightness and colour, checker contrast, reflection strength and blur
Tone Mapping	The curve that maps rendered brightness to the screen
Lighting & Shadows	Directional light, intensity and colour, shadows on/off, shadow intensity, quality, shadow-map size and radius
Post-Processing	Bloom intensity, threshold and radius
Display	UI zoom from 75 % to 200 %, source markers, the drive axis gizmo, toolbar labels, antialiasing and render resolution
Renderer	The 3D backend and static mesh batching — the batching switch is a kill switch for render problems and reloads the viewer
Camera	Perspective or orthographic, and the field of view

If the frame rate is low, work down this list: shadow quality, then shadow map size, then resolution, then antialiasing, then reflections. Each step gives back noticeably more than the one before it costs in appearance. Before spending long on it, check that the browser is on the right graphics card at all — Browser & GPU setup explains how, and why a fast workstation can still be rendering on the CPU.

UI zoom is worth knowing about on a panel PC: at 125 % or 150 % the overlay stays legible at arm’s length without touching the operating system’s scaling.

Mouse & Touch

Rotate, pan and zoom speed, the inertia that keeps a movement gliding after you let go, and Adaptive Nav, which scales the speed with how far the camera is from what you are looking at — the setting that stops a large plant from feeling sluggish and a small assembly from flying past you. Reset defaults puts the group back.

Zoom speed applies to the mouse wheel, the trackpad and pinch alike.

Start View

The camera position a model opens with. Without one, the viewer fits the model into the view — good enough for browsing, rarely right for a delivery.

Frame the view you want, then Save current camera as start view. It is stored per model, so different twins can each open where they should. Clear start view returns to fit-to-bounds.

Simulation

Controls the local simulation rather than the connection to a machine.

Physics (whole scene) decides whether moving parts become physical bodies when they leave a conveyor — falling, sliding and stacking instead of disappearing. Without explicit physics zones in the model, the whole scene counts as one zone.

Full physics — all conveyors is a beta step further: every non-radial conveyor runs as a physical belt. Both take effect on the next model load, which the tab says on the switch itself.

Groups

A model brings visibility groups with it — fences, housings, covers. This tab decides two separate things:

• Default visibility — which groups are hidden when the model loads. Hiding the fence by default is the usual first move on a cell.
• Excluded from overlay — which groups do not appear in the Groups panel at all. Use it to keep an operator’s list short rather than to hide something.

Where your content lives

Earlier versions had a Local Folder tab that pointed the viewer at one fixed working folder on your machine, with a prescribed models/ and library/ layout. That tab is gone, and so is the working folder behind it.

Content now belongs to a project. A project holds your documents and the libraries attached to it, and it is the project — not a global setting — that decides where those bytes live: kept by the browser, or stored in a folder you pick on your own machine. Nothing about the folder layout is prescribed any more; a folder is a place, not a type.

You manage all of this in the Documents dashboard rather than here in Settings. If you still have an old working folder on this machine, Backup ▸ Old Working Folder below brings its contents across.

Interfaces

Interface protocol selects how the viewer talks to a controller when it is not going through realvirtual CONNECT.

Signal display decides how much a signal chip shows — from the full name with value down to a compact form — and which details the tooltip adds: value, address and source, comment, binding. It is a global default; a specific usage in the model can override it.

Multiuser

Shared sessions, where a delivery has them: server URL, join code, display name, and the role you connect with — Observer watches, an operator role may interact. The state line shows whether you are connected, and a switch keeps the multiuser button out of the toolbar when the feature is not wanted.

AI

The AI bridge and the documentation index behind AI diagnosis. Switched on, the tab is the inventory of the bridge: connection state, port, and every tool it exposes, by name. That inventory is the point. It opens only after you have seen what it can reach on this device — deliberately, because an assistant with access to a running machine view is not something to switch on absent-mindedly.

Dev Tools

Diagnostics, and the fastest answer to “why is this model slow”:

• Scene (from GLB) — triangles, meshes, drives, GLB size and load time, straight from the loaded file.
• Optimization — what the loader did with it: materials merged, geometries shared, static and textured batches formed.
• Rendering — frame rate, frame time, draw calls, textures, JS heap, and which renderer is active.
• Picking & Highlight — how long a click takes to resolve, split by acceleration structure.
• Performance budget — each of those against a target, in percent. The bar that is at 100 % is the one to fix.
• GPU — which graphics card is drawing the scene, which others the browser exposes, and a warning when it has picked the wrong one. See Browser & GPU setup.
• GPU benchmark, profiler overlay and library cache round it off; clearing the library cache is what you do after swapping a .glb on disk under the same name.

The experimental 3D backend switch replaces the Three.js view with an Omniverse RTX stream while HMI, signals and charts stay as they are.

Tests

Runs the browser test suite. Available on the Vite development server only — in a delivered viewer the tab reports exactly that.

Backup

Export settings writes everything on this page to a file; Import reads it back — the way to give a second machine the same setup without clicking through every tab.

Reset all settings to defaults clears the saved browser settings and reloads. Clear legacy WebViewer data removes leftovers from an older storage scheme; saved documents are not affected.

Old Working Folder is the way back to a working folder from an earlier version. Copy into this project brings the whole folder across — libraries, thumbnails, knowledge files and all — into the project you have open. It is safe to run more than once: files already brought over are skipped, and nothing in the old folder is changed or deleted, so you decide yourself when to clear it out. The section appears only in a browser that can read local folders at all, and it does not expire — a machine that still has an old folder can be picked up months from now.

See also

• The interface — where these settings sit on screen
• Navigation and controls — what Mouse & Touch changes
• Documents — what a document brings with it