Large meshes in the browser
Scenaven converts VTK on the server and draws the result in the browser. Conversion can complete successfully while wireframe and surface with edges are unavailable for part of your scene—or for the whole dataset if every mesh is very dense.
The viewer defaults to shaded surface for interactive review on large geometry. Edge drawing is optional: it helps on modest meshes, but it is not required to inspect shape, mesh quality, or field results when Surface and scalar coloring are available.
Server capacity and viewport display
| Layer | Responsibility |
|---|---|
| Server | Read VTK, run filters and Python, store the session, export the visual mesh |
| Browser | Camera, colormaps, scene tree, and display styles on the downloaded surface |
The browser receives a surface mesh and field data sized for interactive viewing—not a full copy of the solver grid.
Display styles
| Display style | Viewer draws | Dense meshes |
|---|---|---|
| Surface | Shaded triangles from the server mesh | Available |
| Points | Vertices | Available |
| Wireframe | Edge lines computed in the browser | May be unavailable |
| Surface with edges | Surface plus edge lines | May be unavailable |
Surface and points use geometry already present after conversion.
Wireframe and surface with edges require a second pass in the browser to enumerate unique edges from triangles. On very high triangle counts, that pass can exceed what a single browser tab can handle reliably. The viewer then keeps surface active and explains the limit in a short message.
For dense surfaces, Surface with field coloring and the usual camera tools is the primary review mode. You do not need edge lines to read contours, compare regions, or judge whether a surface looks smooth or faceted—wireframe is extra detail when the mesh is small enough to afford it.
Volumetric VTK vs surface geometry
Volumetric uploads (unstructured grid, image data, assembly volume blocks) keep the full cell grid on the server for filters, compile, and Python. The browser still receives a visual surface—extracted boundary or exported shell triangles—not a shaded copy of every cell.
Surface uploads (poly data, faceted shells, sheet meshes) usually map directly to the same drawable triangles you inspect in the viewport.
Edge-display thresholds use one rule for both paths: triangle count on the visual mesh for that scene-tree geometry row, not VTK cell count and not a separate “volume limit.”
| What you might compare | What controls wireframe / surface with edges |
|---|---|
| Cells in the server session | Not used for this limit |
| Triangles on the row’s downloaded visual mesh | Yes — per-row figures below (typical 2 million / 400 thousand defer band) |
| Multi-part or assembly scenes | Each geometry row is evaluated separately |
A huge cell count does not by itself disable wireframe; a dense extracted skin can disable edges even when the volume grid looked modest—and a very large volume can still allow edges when the drawn surface is coarse enough.
Size limits for edge display
Limits apply per mesh (each scene-tree geometry row), not only to the entire file once. In a multi-part or assembly dataset, one very fine part may disable edges on that part while coarser parts still allow wireframe or surface with edges.
2 million
Triangles (typical maximum, per mesh)
Wireframe and surface with edges are not offered at or above this triangle count
400 thousand
Triangles (typical defer band, per mesh)
Below the maximum: edge lines are often not built on first paint; the first switch to wireframe or edges may take longer
*N*
Shown in the viewer
Exact threshold in the message when a mesh exceeds the limit (same meaning as the figures above)
The 2 million and 400 thousand figures are the usual defaults. Your message may quote specific values such as 2,000,000 triangles.
Load path (reference)
Upload VTK → server conversion → visual mesh → browser → surface draw
Whether edge display modes are available is decided after the visual mesh is ready in the browser, separately for each mesh, not during server conversion.
Messages you may see
| Message (summary) | Interpretation |
|---|---|
| Wireframe / surface edges unavailable above 2,000,000 triangles; showing surface only | That mesh exceeds the edge limit; use Surface or Points on that row |
| Same text with another number instead of 2,000,000 | Same rule; use the quoted figure as the limit for that mesh in that session |
| Same text after changing display style | Requested style is not supported for that mesh; viewer remains on surface |
| No message, but wireframe is slow the first time | Mesh may be in the large-but-under-max band; edge topology is being built on demand |
Progress during upload: Local conversion (on-prem) or Cloud conversion (hosted).
How Scenaven handles this
- Server: ingest VTK, run filters, extract, and Python on the session dataset, then export a visual mesh for the tab.
- Browser: draw surface and points from that mesh; compute wireframe and surface with edges only when that mesh’s triangle count is within the edge budget.
- Over the limit (per mesh): keep surface (or the style you had before), show the threshold in a short message, and leave server-side data unchanged.
- Large but under the limit: defer edge-line work on initial load; prepare edges when you first choose wireframe or surface with edges, which can take noticeable time once.
- Design intent: prioritize a stable tab on real CFD and CAE surface sizes; treat edge modes as a convenience for smaller meshes, not a guarantee for every part in every session.