Is anyone getting reliable parameter handoff using Rhino.Inside to drive a 1.5 m x 3.6 m unitized grid and keep Revit curtain panel families light? I need schedules and shop details to sync when we tweak mullion back-legs and gasket bites, and I’d love to tag a THERM Uf (e.g., 0.35 W/m²·K) without manual re-entry…
I’d bind a “shared parameter” for Uf (number, Discipline: Energy) to Curtain Panels and Mullions and have Rhino.Inside push it by GUID to the TYPEs so tags and schedules stay in lockstep. For back-legs and gasket bites, drive only the numeric instance params via RiR and keep the panel geometry dumb, or Revit bogs down faster than a soggy gasket. Are you writing to types or instances, and is that Uf param truly shared with a fixed GUID?
Use Thermal Transmittance parameter for Uf to tag 0.35 W/m²·K. Driving back-legs via global parameters yet, @OP?