PoseSaver Update Text (Hub “Updates” section)(no new text-just a quickfix)
PoseSaver v1.5.x – Multi-Camera UI fix
- Fixed a layout issue with the Multi-Camera System on higher resolutions.
- On 2560×1440 and 2560×1600 (and some UI scale combinations), the camera buttons could overlap the pose thumbnailsor appear misaligned.
- Fully resolution-independent and UI-scale-independent
- Used as the parent for all camera buttons,
This should fix the misaligned/overlapping for users on 1440p / 1600p or other non-1080p setups, while behaving exactly the same as before on 1080p.
If there still are issues please give me feedback.
PoseSaver Update1.5.4
PoseSaver v1.5.x – Multi-Camera UI fix
- Fixed a layout issue with the Multi-Camera System on higher resolutions.
- On 2560×1440 and 2560×1600 (and some UI scale combinations), the camera buttons could overlap the pose thumbnailsor appear misaligned.
- Fully resolution-independent and UI-scale-independent
- Used as the parent for all camera buttons,
This should fix the misaligned/overlapping for users on 1440p / 1600p or other non-1080p setups, while behaving exactly the same as before on 1080p.
If there still are issues please give me feedback.
PoseSaver v1.5.3 - Update Notes
UI FIX: On-Screen Thumbnail Layout & Camera Button Alignment
PROBLEM FIXED:
Previous version had UI layout issues when displaying pose thumbnails on screen, particularly at different
resolutions (1080p, 1440p). Camera selection buttons were misaligned with thumbnails, and pagination controls
were partially cut off on 1080p displays.
MAJOR FIX: Look/Appearance Distortion Issue Resolved
PROBLEM FIXED:
Previous versions (1.4.3 - 1.5.1) could cause character shape distortion when switching between poses. This happened because PoseSaver was capturing morphs that belong to the Look's appearance preset, not just pose-specific morphs. When loading poses, these saved Look morphs would overwrite or conflict with the current appearance.
THE SOLUTION: Baseline Morph Snapshot System
PoseSaver now uses a smart delta-save system that only captures morphs that actually change during posing, keeping your Look/appearance intact.
HOW IT WORKS:
1. When you save your first pose, PoseSaver automatically captures a "baseline snapshot" of current morph values
2. Each subsequent pose only saves morphs that DIFFER from this baseline
3. Look morphs that were already set stay in the baseline and aren't saved in poses
4. When loading poses, only pose-specific morphs are applied - your Look stays perfect!
NEW UI CONTROLS:
• "Capture Morph Baseline" (green button) - Manually capture/update the morph baseline
• "Clear Morph Baseline" (red button) - Reset baseline (will auto-recapture on next save)
RECOMMENDED WORKFLOW:
1. Load your scene and apply your favorite Look/Appearance preset
2. Add PoseSaver plugin to the Person atom
3. (Optional) Click "Capture Morph Baseline" to lock in the current appearance
4. Start creating poses - only pose changes will be saved!
BENEFITS:
✓ No more shape distortion when switching poses
✓ Smaller pose file sizes (only actual pose morphs saved)
✓ Looks/Appearance presets remain intact
✓ Compatible with all existing poses (backward compatible)
✓ Works automatically - baseline captures on first save
TECHNICAL DETAILS:
• Baseline is stored per-atom and persists across all poses
• Uses epsilon comparison (0.0001) for float precision
• Only affects morphs in Custom/Atom/Person/Morphs/female|male directories
• Appearance/body morphs in other directories are never affected
• Clear and recapture baseline anytime if you change Looks mid-session
This update restores the reliable behavior from v1.4.2 while maintaining all the improvements from recent versions.
Hopefully fixed the Look-dependent shape distortion bug in PoseSaver
The Problem:
- PoseSaver 1.4.3+ was resetting ALL pose morphs to default if they weren't explicitly saved in the pose
- This broke Looks that store their base shape morphs in Custom/Atom/Person/Morphs/... folders
- When switching poses, these Look morphs would get reset to default, causing distortion
Hopefully this is history now. but il need you guys to test it.
Update: Improved Timeline Compatibility (Scoped Control)
Some users experienced issues where a pose change would cause Timeline to behave unpredictably — especially when the next pose uses an On Enter trigger to start a Timeline animation.
Previously, the workaround was to add an “On Exit → Stop & Reset Timeline” trigger.
However, this stopped every Timeline instance in the scene, including ambient systems like daylight cycles, vehicles, blinking lights, etc.
This update introduces a safer and more controlled behavior inspired by the BodyLanguage pattern:
Before (User’s Issue)
- Using an “On Exit → Stop & Reset Timeline” trigger stopped all Timeline plugins in the scene
- Ambient or unrelated Timeline animations were unintentionally shut down
- Result: Conflicts, broken atmosphere, and extra work to restart everything manually
After (Improved Scoped Behavior)
- Scoped Control – PoseSaver interacts only with Timeline running on the same atom
- Selective Restart – The system stops Timeline cleanly, then restarts only the clips assigned to the active pose
- Ambient Safe – Timeline plugins on other atoms (lights, vehicles, props) are untouched
- Clean Transitions – Timeline clip references are stored per pose for precise re-activation
- No Scene-Wide Side Effects
This ensures Timeline behaves predictably without disrupting background or environmental systems.
Usage
Huge thank you to Bigbricksontheoverall for pointing this out!
- Automatic Detection
Timeline on the same atom as PoseSaver is detected automatically on load.- Selective Per-Pose Clips (Future UI)
Users may optionally assign specific Timeline clips to poses.- Zero Configuration
Works out of the box without needing user setup or additional triggers.- Fully Backward Compatible
Poses without Timeline data behave exactly as before — unaffected by this feature.if there still any issues please give me more feedbacks
just a minor fix this time :
Character distortion bug FIXED - Morphs properly reset between poses
Transitions now INSTANT by default - No more slow smooth transitions
If you find any other issues please tell and il try to get at it as fast as possible.
Big Thank you`s goes to Babu and Fttp for the feedback on these issues![]()
PoseSaver 1.4.9 – Thumbnail Strip & Pagination Stability
Small but important stability pass on the screen thumbnail system.
This update finishes the work from 1.4.6–1.4.8 and makes the right-side strip reliable even with many poses.
Right-Side Thumbnail Strip Polished
- Thumbnails are now anchored a bit lower on the screen so they no longer overlap VaM’s top-right UI bar.
- The vertical strip keeps the model and scene center clean while still giving quick pose access.
- Works correctly with multiple pages of poses.
Pagination Controls – No More NullReference
Previously, some users could trigger:
PoseScreenCanvas.CreatePaginationControls: Object reference not set to an instance of an object
especially after saving a lot of poses and paging through them.
This is now fixed:
- Extra safety checks around the internal button group.
- Old pagination UI is destroyed safely before new controls are created.
- Pagination only shows when there is more than one page.
Result: no more errors and fully stable previous / next arrows.
Save New Pose + Thumbnails More Reliable
- Repeatedly using “Save New Pose” with many poses now keeps thumbnails and pagination in sync.
- The page counter (1/3, 2/3, etc.) and arrows stay visible and update correctly as new poses are added.
- Clicking a freshly saved thumbnail no longer risks odd behaviour or layout glitches.
If anything still acts weird with large pose sets or unusual resolutions, please let me know – feedback helps me keep polishing PoseSaver
![]()
PoseSaver 1.4.8 – Minor Fix Update
Small fix this time — thank you fttp for reporting the issues!
Fixes in this update:
- Missing Arrow Buttons
When repeatedly using “Save New Pose”, thumbnails stopped showing after 8 entries and the arrow buttons disappeared.
This is now corrected — pagination shows properly again.- NullReferenceException on Pagination
Some users received this error when saving multiple poses in a row:
CreatePaginationControls: Object reference not set to an instance of an object
This has been fixed and pagination is now stable.- Character Distortion When Clicking Thumbnails
In some cases, clicking a newly saved pose thumbnail after “Save New Pose” caused the character’s shape to distort.
This happened mostly with certain presets.
The issue is now resolved.- Handstab UI Adjustments
The handstab section has been cleaned up and improved for better usability.
All known issues from the report are now fixed.(if i missed something please tell)
Thank you for helping me improve PoseSaver!
Update 1.4.7 – Timeline Auto-Keyframe Protection
✔ Fixed: Timeline overwriting animations when loading poses
Some users experienced that loading a pose in PoseSaver would trigger Timeline’s “Auto-keyframe all controllers”, causing Timeline to automatically create new keyframes and overwrite existing animation data.
This is now fully resolved.
What’s New
🛡 Automatic Timeline Auto-Keyframe Protection
PoseSaver now detects any active Timeline plugin and temporarily disables its auto-keyframe system while a pose is loading.
This prevents Timeline from generating unwanted keyframes.
How it works
- Detection
PoseSaver scans all atoms for Timeline and uses reflection to access the internal autoKeyframeAllControllers flag.- Protection
Before loading a pose, PoseSaver disables auto-keyframing on all detected Timeline instances and stores their original state.- Restoration
Once the pose is fully applied, all Timeline instances are returned to their previous settings automatically.
Works with different Timeline versions (includes safe try/catch handling).
Benefits
No more accidental overwriting of Timeline keyframes
You can load poses freely while animating
Seamless and invisible — no buttons, toggles, or setup required
Timeline settings are restored exactly as they were before pose load
Fully safe and non-intrusive
User Experience
You can now:
- Use PoseSaver while animating in Timeline
- Keep auto-keyframe on without worrying
- Switch poses rapidly with zero risk to your animation work
The fix is automatic — the only thing you’ll notice is that your Timeline keyframes stay exactly where they should.
Thank you Babul for pointing this out!