Nodes/Gimbal-ComfyUI/πŸ“ Gimbal GPS Anchor (Save)
ComfyUI Node

πŸ“ Gimbal GPS Anchor (Save)

Save a latent to disk so you can come back to it later

By FormAndNoiseΒ·Created about a month agoΒ·Updated 19 days agoΒ· 0
πŸ“ Gimbal GPS Anchor (Save)
  • latent_batch
  • gimbal_meta
  • wayfinder_meta
  • anchored_latent
  • waypoint_meta
  • waypoint_report
β—„select_index0β–Ί
β—„save_waypointfalseβ–Ί
β—„waypoint_namewaypoint_01β–Ί
β—„enable_perf_loggingfalseβ–Ί

Ever landed on a latent you love - a lighting setup, a composition, a character framing - and then had to rebuild it from scratch the next day because there was no way to save the thing itself? GimbalGPS_Anchor is the save button for that. It takes a latent (or a batch of them), picks one, and writes its exact tensor coordinates to a JSON waypoint file on disk, complete with statistics and a SHA-256 hash so you know it wasn't corrupted. Its sibling GimbalGPS_Load brings it back.

How it works

Inputs: latent_batch (often the output of a GimbalManifold_Explorer grid), select_index (which latent in the batch to anchor, default 0), save_waypoint (boolean - whether to write to disk at all), waypoint_name (the file's name, default waypoint_01), and enable_perf_logging. There are also optional gimbal_meta/wayfinder_meta dicts you can pipe in from a Compass Pro or Manifold Explorer if you want provenance baked into the saved file.

When save_waypoint is on, it writes to output/gimbal/<waypoint_name>.json under your ComfyUI output directory. The file contains the full tensor coordinates, per-channel stats, the hash, and any metadata you fed in. You always get three outputs: anchored_latent (the selected latent, ready to keep flowing through the graph), waypoint_meta (the dict version of what was saved), and waypoint_report (a readable string for debugging or display).

When you'd reach for it

The README's flagship use case is brand consistency: render a product with a lighting setup you like, anchor it as golden_arch_hero_v1, and in any future session load that exact latent and steer it onto new products with Compass Pro in Orthogonal_Projection mode. Same light grammar, new subject, no re-rolling. It's also just a nice way to bookmark a midpoint you want to explore further - pull the center cell out of a grid (index 4 of a 3Γ—3), anchor it, and come back tomorrow.

Installing

Standard pack install: ComfyUI Manager β†’ search "Gimbal-comfy" β†’ install β†’ restart, or git clone https://github.com/FormAndNoise/Gimbal-comfy into ComfyUI/custom_nodes. Dependencies are torch/numpy/pillow - already in ComfyUI, nothing to download. The README's clone URL is stale; FormAndNoise/Gimbal-comfy is the live repo.

Where people get burned

Three gotchas. First, save_waypoint defaults to false - if you anchor and forget to flip it, nothing is written and you'll look for a JSON that was never created. Second, waypoint files can be large (a full 16-channel FLUX latent is a lot of numbers), so don't treat this as something to spam on every render - only save the ones you'd actually revisit. Third, this is a latent bookmark, not an image: loading it later and re-sampling won't reproduce the exact render, because the KSampler's noise is part of the picture. You're bookmarking a position, and positions are reusable in a way pixels aren't. That's also the honest limitation of the whole GPS story - it's genuinely useful, but it's a niche workflow, and the pack has almost no community write-ups to crib from, so you'll be the one deciding when bookmarking earns its keep.

CategoryGimbal/Navigation

Inputs (7)

NameTypeDefaultDescription
latent_batchLATENTβ€”
select_indexINT00–4095β€”
save_waypointBOOLEANfalseβ€”
waypoint_nameSTRINGwaypoint_01β€”
enable_perf_loggingBOOLEANfalseβ€”
gimbal_metaoptDICTβ€”
wayfinder_metaoptDICTβ€”

Outputs (3)

NameTypeDescription
anchored_latentLATENTβ€”
waypoint_metaDICTβ€”
waypoint_reportSTRINGβ€”