Repository navigation
Releases
Releases · stephomi/nomad-link
0.11.48
- The
color,roughness,metalnessandopacitytexture channels carry an
intensity, how much of the texture shows. At 0 the mesh looks as if the channel had no
texture. An absentintensityreads as 1.0, so older peers keep working. - Blender: the material follows Nomad's texture shading. The color texture multiplies
the vertex paint instead of replacing it, roughness and metalness mix with their vertex
paint by the intensity, and the vertex alpha multiplies the opacity. The texture factor
applies too, and both values travel back to Nomad and through .nom files.
0.11.47
- Blender: File → Export → Nomad Sculpt (.nom) saves the scene as a Nomad file, without
a running link. It writes the hierarchy, linked duplicates as instances, UVs, vertex paint,
the sculpt mask, face groups, hidden faces, shape keys as sculpt layers, the material with
its textures, lights and camera objects, the selection, and the 3D viewport as Nomad's
camera. N-gons are triangulated. - Blender: a .nom import keeps a slightly skewed transform exact. Blender's own decomposition
used to round it off by up to 1e-3. - Blender: a Scene or Selection send keeps the copies Nomad's repeaters made (#3). Each copy
follows its owner, flaggedrepeat: a Nomad still holding the repeater ignores it, and a
fresh scene gets it as an ordinary object. A copy with its own mesh used to be dropped, and
every copy went missing in a Nomad without the repeater. - Nomad's
hellono longer carriesbridge_version. No bridge read it, so the protocol
version stays 1.
0.11.46
- The
displacementtexture channel carriesmidandworldbeside itsfactor, and the
factor is now a height in scene units: a vertex moves (sample − mid) × factor along its
normal. An absentmidreads as 0.5, so older peers keep working. - Houdini: the displacement texture gets the matching USD
bias, so the surface stays where
Nomad shows it instead of rising by half the height. - Toolbag: the Height displacement takes the height as its Scale (in scene units, Relative
Scale off) andmidas its Scale Center. The map used to arrive alone, at Toolbag's own
scale.
0.11.45
- Blender: vertex groups survive a full mesh from Nomad. A layered mesh sends every stroke as
a full mesh, and the rebuild used to drop the groups with the old geometry. Names always
come back; weights come back when the vertex count is unchanged. - No protocol change.
0.11.44
- Houdini: a copied Nomad Link Out node is a new object in Nomad. The copy used to inherit
the original's mesh id, so sending from it replaced the original's mesh instead of adding
one. Pasting now clears the id, and a copy made with an older build heals itself on send. - No protocol change.
0.11.43
- Blender: a shape key value outside [0, 1] reaches Nomad on the layer's offset factor, where
the slider is unbounded and signed. The raw value used to land on the main intensity, which
composited it correctly but pinned its [0, 100%] slider display at 100%. - Blender: the add-on welds UVs before sending — corners meeting at the same point share one
texcoord. They used to arrive one texcoord per corner, so on the Nomad side every edge read
as a UV seam and Face Groups built from UV islands came out one group per face. - Lights travel under Nomad's own type names —
directional,point,spot,
environment— where they used to borrow Blender'sSUN,POINT,SPOT,
ENVIRONMENT. Update the bridges along with Nomad: to an older bridge every light now
reads as a point light, and an older Nomad reads the new names the same way. The Blender
add-on and the Toolbag plugin in this release speak the new names. - Primitives stay primitives between two Nomads: a sphere, tube, or lathe arrives on the
peer still parametric, config and all, instead of frozen into a mesh. Bridges see no
difference — the arrays remain the object, so anything that ignores the new block gets
what it always got. - Validating a primitive no longer strands it on the peer. The peer kept holding a primitive,
which cannot take sparse edits, so it refused every stroke after the validate and the
object stopped updating for the rest of the session. - A mesh shows the paint it receives rather than ignoring it: a channel that arrives with
per-vertex color, roughness, metalness, or opacity turns that channel on. A validated
primitive used to render in its flat material color on the peer while sitting on the paint
it had been sent. - Repeaters (array, curve, mirror, radial) travel with their config, so a Nomad peer rebuilds
the copies itself instead of receiving them one by one. Bridges keep receiving the copies as
ordinary objects. - Protocol:
light_typerenamed (breaking), and two new blocks —primitive(§7.1.2) and
repeater(§10.4).
0.11.42
- Blender: Edit Mode changes reach Nomad while you make them. Blender keeps those edits in its
own mesh until the mode ends, so until now they only travelled once you went back to Object
Mode. - Blender: an add-on that keeps a modal operator open for the whole session no longer freezes
the link. Updates are only held while a sculpt or paint brush stroke is in flight, the one
case where applying them could crash Blender. - Blender: the panel says which mesh paused and why — Edit Mode, Dyntopo or Multires — and
drops the message once it has caught up. - No protocol change.
0.11.41
- Toolbag: Follow Nomad's view is Nomad's shared Working View setting rather than a local
one, so ticking it in the plugin turns view sync on for the session, and a change made in
Nomad or another bridge shows up in the checkbox. - Toolbag: the transfer is faster.
- A flat material color travels as vertex data: primitives were white in Blender's Shading tab.
- No protocol change.
0.11.40
- Blender: the connection no longer stalls on "Waiting for Nomad" when another add-on keeps a
modal operator running. Session packets are applied while one is in flight; scene packets are
still held until it ends, and the panel shows how many are waiting. - No protocol change.
0.11.39
- Toolbag: color and emissive maps are read as sRGB, every other channel as raw data. The
color space is set on the texture, not on the slot, so a map never speaks for the vertex
colors sharing that slot. - Toolbag: per-channel texture factors, displacement maps, normal-map Y flip, and
subsurface color. Clearing a channel removes its map instead of leaving the old one. - No protocol change.