### Per-camera visibility snapshots for DAZ Studio. Capture once, recall anywhere.
Stop hiding and un-hiding the same fifty props every time you switch shots. **VisiSnap Pro** lets you save the exact visibility state of every node in your scene as a named snapshot, keyed to the camera you are looking through. One click later you are back to that exact lighting rig, that exact wardrobe combination, that exact prop arrangement, on the exact camera you used to set it up.
Built for visual novel authors, comic creators, animators, and anyone who renders the same scene from multiple angles with different sets of things shown or hidden.
---
## Why you need it
If you have ever:
- Built a complex interior and had to manually hide the ceiling and front wall before every angle change
- Lit a scene three different ways for three different times of day and lost track of which lights belong to which look
- Switched cameras and watched your "lights off" version come back to life because you forgot what was hidden
- Watched a render crawl because off-camera props, hair cards, and SSS-heavy figures are still in the scene eating GPU memory and ray bounces
- Wished DAZ Studio had a real "save view" feature that remembered visibility, not just camera position
VisiSnap Pro fixes all of that. Permanently.
---
## How it works
1. **Set up your scene** for a specific camera angle. Hide what you do not want rendered, show what you do.
2. **Open VisiSnap Pro** from the Scripts menu (one click, or assign a keyboard shortcut).
3. **Click Save**. The current visibility of every node in the scene is captured as a slot, automatically tagged with the active camera.
4. **Switch cameras**. Set up a different look. Save another slot. Repeat.
5. **Need to come back later?** Open VisiSnap Pro, pick the slot, click Apply. Your scene is restored in one undoable step.
That is it. No exporting, no manual checklists, no "wait, was the curtain supposed to be open in this shot?".
---
## Key features
### Faster renders, by design
Every node hidden by a snapshot is a node Iray (or 3Delight, or Filament) no longer has to process. Pre-build "render-ready" slots that hide everything off-camera: props behind the wall, the figure standing in the next room, the hair card on the character whose back is to the lens, the SSS-heavy double sitting on the couch in the establishing shot. Apply the slot, render, move on. On heavy interiors this routinely cuts GPU memory use and render time by a real, measurable margin, without you having to remember the cleanup list every single time.
### Camera-aware slots
Each snapshot is tied to a specific camera by label. Switch the camera in the picker and the viewport switches with it, so you always see exactly what you are about to capture or restore.
### Smart diff view
Before you apply a slot, see a clean breakdown of what will change: which nodes become visible, which become hidden, which are missing from the scene since the snapshot was taken. No surprises.
### Two apply modes
- **Non-destructive** (default): only touches nodes that exist in the snapshot. Anything added to the scene afterwards is left alone.
- **Strict**: exact restoration. Anything not listed in the snapshot is forced hidden.
### Full DAZ undo integration
Apply wraps the whole operation in a single undo block. One Ctrl+Z reverts everything in one shot.
### Confirmation dialogs
Save and Apply both ask for confirmation, with a visibility count preview so you know exactly what is about to happen. Per-slot "do not ask again" option for the slots you trust.
### Per-scene storage, JSON format
One snapshot file per scene, stored in your DAZ app-data folder (configurable). Human-readable JSON. Move it, version it, share it, edit it by hand if you want.
### Survives renames and edits
Slots remember each node by internal name, asset URI, and label. Rename a prop in the Scene pane? VisiSnap Pro still finds it. Delete a prop? The slot still loads, the missing item is flagged in the diff, nothing else breaks.
---
## What's included
- **VisiSnap-Pro.dse** - the main tool (single-file install, no DLLs).
- **Install-VisiSnap-Pro.dse** - registers VisiSnap Pro as a Custom Action and adds it to the Scripts menu. Run once after install.
- **Uninstall-VisiSnap-Pro.dse** - cleanly removes the Custom Action. Your snapshot files are never touched.
- **ReadMe** with full install, usage, and uninstall instructions.
Installs through DAZ Install Manager like any standard DAZ product. Or extract and use‥
---
## Compatibility
- **DAZ Studio 4.x** (tested on 4.23, the long-term reference build).
- **DAZ Studio 6** (tested on the public beta releases).
- **Windows, macOS, Linux**. Pure DAZ Script, runs anywhere DAZ Studio runs.
---
## Who it's for
- **Visual novel and comic creators** rendering the same room from twenty angles with twenty different lighting setups.
- **Anyone fighting render times on heavy scenes.** Build per-camera "render-ready" slots that strip out everything off-screen, slash VRAM pressure, and shave minutes off every frame. The savings stack up over hundreds of renders.
- **Animators** previsualizing a sequence and snapping between blocking states.
- **Product and architectural renderers** producing multiple variants of the same scene.
- **Anyone who has ever hand-edited a hidden-nodes list** because they could not remember which Smart Content combo was the "night" version.
---
## FAQ
**Will this work with my existing G8, G9, or custom rigs?**
Yes. VisiSnap Pro operates on any node in the scene, of any type. Figures, props, lights, cameras, primitives, instances, all supported.
**Does it modify my scene file?**
No. Snapshots are stored as JSON files outside your scene. Applying a snapshot changes node visibility, which is undoable in one step. Your `.duf` file is only touched when you save the scene yourself.
**Can I move my snapshots between machines?**
Yes. Snapshot files are plain JSON, one per scene. Copy them anywhere. The configurable storage folder makes it easy to keep them next to your scene files if you prefer.
**Does it work with subset scenes or merged scenes?**
Yes. Node identity is resolved on apply via a three-way fallback (internal name, asset URI, label), so most scene reorganization survives.
---
