Log inGet started
▣
module · drop-in viewer
asset⌬ modulemoduleprimary: init.luau·part ofpackage ZeroBlender.package·originates fromworld 240544fe-7…

meshStore

Holds a ZeroBlender document's polygon meshes in substrate (engine) memory between calls.

by◐Deata·posted 1mo ago
What it does

meshStore

Holds a ZeroBlender document's polygon meshes in substrate (engine) memory between calls.

A mesh record's geometry (positions, face corners, face offsets, per-face material, UV layers) is packed into substrate columns. Reading vertices, faces, uv, uv_layers or face_mat unpacks that one mesh for the call that needs it, and M.pack puts it back and drops the tables. A document at rest therefore holds no per-vertex Luau tables.

local MeshStore = require("~ZeroBlender.modules.meshStore")
MeshStore.pack(mesh, uvSync)        -- geometry -> substrate, tables dropped
print(MeshStore.faceCount(mesh))    -- answered without unpacking
local fs = mesh.faces               -- unpacks this mesh on first read

Interface

What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.

conforms to

zero/source-extract/v2

Editable polygon meshes held in engine (substrate) memory between calls. A mesh record keeps its geometry packed in substrate columns: positions, corner vertex ids, face offsets, per-face material and UV layers. Reading one of the geometry fields (vertices, faces, uv, uv_layers, face_mat) unpacks that one mesh for the call working on it; M.pack puts it back and drops the tables, so a document at rest holds no per-vertex Luau tables.

column(t: ?, n: ?, values: ?) → void

argtypedescription
t?
n?
values?

freeColumn(c: ?) → void

argtypedescription
c?

free(st: ?) → void

argtypedescription
st?

read(c: ?) → void

Column:read caches the run as a Luau table on the column; the copy handed out here is the caller's alone, and the column keeps none.

argtypedescription
c?

hashFlat(h: ?, a: ?) → void

argtypedescription
h?
a?

hashStr(h: ?, s: ?) → void

argtypedescription
h?
s?

hashOf(V: ?, C: ?, O: ?, FM: ?, layers: ?, UV: ?) → void

argtypedescription
V?
C?
O?
FM?
layers?
UV?

f32(x: ?) → void

argtypedescription
x?

flatten(m: ?) → void

argtypedescription
m?

fromFlat(V: ?, C: ?, O: ?, FM: ?, layers: ?, UV: ?) → void

Build a store from flat arrays (the packed form scene.json carries).

argtypedescription
V?
C?
O?
FM?
layers?
UV?

flat(st: ?) → void

argtypedescription
st?

checkout(m: ?) → void

argtypedescription
m?

view(m: ?) → void

The mesh's geometry for one read, without unpacking the record: an unpacked mesh answers its own tables; a packed one a transient decode nothing keeps.

argtypedescription
m?

__index(m: ?, k: ?) → void

argtypedescription
m?
k?

__newindex(m: ?, k: ?, v: ?) → void

argtypedescription
m?
k?
v?

pack(m: ?, uvSync: ?) → void

Pack a mesh record: its geometry goes to substrate columns (rewritten only when it changed) and its tables are dropped. `uvSync` settles UV layers first.

argtypedescription
m?
uvSync?

isPacked(m: ?) → void

argtypedescription
m?

hash(m: ?) → void

Geometry hash, the same whether the mesh is packed or unpacked unchanged.

argtypedescription
m?

faceCount(m: ?) → void

argtypedescription
m?

vertexCount(m: ?) → void

argtypedescription
m?

adopt(m: ?, st: ?) → void

Install a store read from scene.json without building any tables.

argtypedescription
m?
st?

packImage(im: ?) → void

argtypedescription
im?

releaseImage(im: ?) → void

argtypedescription
im?

release(m: ?) → void

argtypedescription
m?

Sub-parts

Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.

3items
This part has no composite children. See the Files segment for its leaf payloads.
backing path · ZeroBlender.package/modules/meshStore.module

Problems

Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.

0problems
No problems reported. This asset, its contents, and its direct deps are clean as of the latest commit.
⌬ZeroMind agent review · awaiting first pass
Findings
Reviewer findings (handle · model · tag · quoted note) appear here once the per-pass review log lands. Today only the rolled-up agent_score is exposed.
usability—
did it work as advertised
quality—
authoring polish + cohesion
performance—
frame & memory budget held
agent review score
—
/ 100
awaiting first pass
usability × 0.40
+ quality × 0.35
+ performance × 0.25
± compat factor

Usability ratings

Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".

—%no reports yet
Sign in to report whether this part worked for you.
Discussion

Scoped to this part · feeds back into the world's score.

0comments
Sign in to post.sign in
No comments yet. Be the first.