My AI-enhanced Request:
Please save and restore the Detail On/Off and Model On/Off visibility states for worksession-attached files when reopening the .rws file.
References & Context
- “Layout / Detail visibility with worksession and wishes” (2016) – Detail-level visibility changes for attached files reset when reloading; top-level visibility only persists. McNeel Forum
- “HideInDetail with worksession doesn’t remember hidden objects” – Confirms visibility per detail isn’t saved for non-active files; logged in YouTrack as RH-37146. McNeel Forum
- “Are Worksession Layout Detail issue resolved in Rhino7?” (2020 & 2025) – Users report the issue persists in Rhino 7 and Rhino 8, referencing RH-37146 explicitly. McNeel Forum
- “Save state of layers in worksessions/linked blocks” (2022–2023) – Highlights that local layer visibility in details is not retained even when parent layer states are saved. McNeel Forum
- “Saving Visibility States of Worksessioned Layers and Objects” (2024) – Work is stuck in long sessions hiding details; workaround recommended is linked blocks with Layer State Manager. McNeel Forum
- “Worksession doesn’t save hidden/changed objects/layers” (2022) – Users note hiding features (e.g.,
HideInDetail) aren’t retained and linked blocks are the fallback. McNeel Forum - “Quick question: Work sessions DON’T save layer changes? Intentional?” (July 2025) – Discussion continues, confirming layer visibility and properties still don’t persist—likely unintended behavior. McNeel Forum
Why This Matters
- It eliminates the need to manually reconfigure visibility settings every time a worksession reloads.
- It supports consistent and accurate documentation workflows, especially for teams working with multiple views or layout details.
- It boosts efficiency and reduces errors in complex, multi-file workflows.