• Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.
Posesaver

Plugins + Scripts Posesaver

Download [<1 MB]
Hello! I love this plug-in so much, but I'd like to comment on a few things I’ve noticed while testing it:

1- It seems scenes aren’t saved when this plugin is active: when saving, only a JPG image is created, but no JSON file associated with that image. I don’t know if other users are experiencing the same issue as I am, but the plugin is useless if scenes can’t be saved. Disabling/enabling the plug-in won't work, as all saved poses disappear. Could it be the JSON file is being saved in a different location, or maybe I've missed something?

2- From what I’ve seen, each pose works like a “state machine.” I’ve tested it with the Clockwise Bj & HJ plugins and McGruber’s Gaze, and it seems that each pose stores the configuration of every plugin for all characters in the scene. (I've tested it with a threesome, and all works fine). I find it very useful for automating actions without having to use triggers. It’s intentional, right? I see, however, that when Clockwise Bj & HJ are in active mode, you need to double-click one of the poses saved by your plugin for it to be applied correctly (well, we all know these BL HJ plugins tend to keep doing whatever they were doing before you swith poses, moving hands or heads towards their targets and therefore distorting the pose).

2- Do you plan to add cameras for each pose, like in BL? That would be great, especially if the transitions between each camera could be smooth, like in BL.

Thank you very much, this plug-in is very promising, and it might become a nice, lighter alternative to BL, and so far, it doesn't throw error logs, at least, not in my case.
 
Hello! I love this plug-in so much, but I'd like to comment on a few things I’ve noticed while testing it:

1- It seems scenes aren’t saved when this plugin is active: when saving, only a JPG image is created, but no JSON file associated with that image. I don’t know if other users are experiencing the same issue as I am, but the plugin is useless if scenes can’t be saved. Disabling/enabling the plug-in won't work, as all saved poses disappear. Could it be the JSON file is being saved in a different location, or maybe I've missed something?

2- From what I’ve seen, each pose works like a “state machine.” I’ve tested it with the Clockwise Bj & HJ plugins and McGruber’s Gaze, and it seems that each pose stores the configuration of every plugin for all characters in the scene. (I've tested it with a threesome, and all works fine). I find it very useful for automating actions without having to use triggers. It’s intentional, right? I see, however, that when Clockwise Bj & HJ are in active mode, you need to double-click one of the poses saved by your plugin for it to be applied correctly (well, we all know these BL HJ plugins tend to keep doing whatever they were doing before you swith poses, moving hands or heads towards their targets and therefore distorting the pose).

2- Do you plan to add cameras for each pose, like in BL? That would be great, especially if the transitions between each camera could be smooth, like in BL.

Thank you very much, this plug-in is very promising, and it might become a nice, lighter alternative to BL, and so far, it doesn't throw error logs, at least, not in my case.
Hello Virtamales and thank you for the feedback!❤️👍 1. If this isnt happening then i surely gonna fix it couse then ive done something i wasnt supposed too.as far as my tests went saving presets functioned but i will have a look at it. ( im preoccupied a couple of days now but will try to do this as fast as i can). 2 the camera future should be there in "edit". Look in the tabs there.( You can choose between smooth cam off/on), but i will check this also. As for BL it was indeed a great inspiration and here goes almost all credit too CessyFx for sure, but i do intent to make it a simple plugin, kinda like Animatis is (.. its simplicity) , so this feedback you can rest asure i will tak to heart and try to make it exactly as you guys want it. a couple of days from now and im ready again for focusing on both my plugins🙂
 
I found that the texture information was also saved along with it. I didn't want this to happen. When I changed the appearance of the character and loaded the pose, I discovered that the texture of the previous character was being read.
 
I found that the texture information was also saved along with it. I didn't want this to happen. When I changed the appearance of the character and loaded the pose, I discovered that the texture of the previous character was being read.
im working on this and will have an update in a couple of mins(max30 min-1hour), as of now im doing a test to see if further changes is needed before releasing the new update. stay tuned :)
 
Kimowal updated Posesaver with a new update entry:

1.4.1

✅ PoseSaver – Update v1.4.1


New Features

Trigger System Enhancements

- Each pose now appears as a separate trigger action: "Load Pose 1: My Pose Name", "Load Pose 2: Another Pose",
etc.
- Easy to trigger specific poses from scene triggers
- Trigger names automatically update when poses are reordered

Pose Reordering

- Up/Down arrow buttons (▲▼) in Edit mode to reorder poses
- Arrows disabled when poses are at top/bottom
- All triggers...

Read the rest of this update entry...
 
While exploring plugin, I came across one incomprehensible thing: For each saved pose there are 10K lines of code, such as: all morphs, all items of clothing, all textures and settings of character materials, and much more.
It seems to me that this is an excessive amount of information for poses (or is it for future functions?)
 
This is a godsend since Poseme has so many randomly occuring issues in large scenes, I really hope to start using this as my main tool for scene creation.

Issue:
In the latest version (7) Plugin seems to still duplicate layers in Decal_Maker_2, reloads skin and loads saved hair on each pose load.
 
While exploring plugin, I came across one incomprehensible thing: For each saved pose there are 10K lines of code, such as: all morphs, all items of clothing, all textures and settings of character materials, and much more.
It seems to me that this is an excessive amount of information for poses (or is it for future functions?)
PoseSaver is currently saving more data than it actually needs because I originally built the save system with future flexibility in mind (morph states, clothing states, materials, etc.).
Now that the plugin has grown and I see how people are using it, I will trim down the saved data so it only includes what is truly required for pose switching. This will reduce file size, improve loading speed, and keep PoseSaver lightweight.
The goal is for PoseSaver to stay simple and efficient, without extra systems that other plugins already handle better.
So yes — this will be optimized soon. Thanks again for the feedback, it helps a lot! 👍🔥
 
This is a godsend since Poseme has so many randomly occuring issues in large scenes, I really hope to start using this as my main tool for scene creation.

Issue:
In the latest version (7) Plugin seems to still duplicate layers in Decal_Maker_2, reloads skin and loads saved hair on each pose load.
Wow thank you so much for that! :) il deff will fix this issue right away!
 
Kimowal updated Posesaver with a new update entry:

1.4.2

✅ PoseSaver – Update v1.4.2


Major Improvements:

Trigger System Enhancements
- Each pose now appears as individual trigger action ("Load Pose 1: Name", "Load Pose 2: Name", etc.)
- Added up/down arrow buttons in Edit mode to reorder poses
- Triggers automatically update when poses are reordered

Massive Performance & File Size Optimization
- Reduced pose file sizes by ~95% (from 10,000+ lines to ~200 lines per pose)
- Poses now save ONLY positions...

Read the rest of this update entry...
 
It records plugin states, atomdata, and god knows what else :) Check presets size, its like 500mb lol. I' m working on this, I use it as structure and change almost every line of code. I love the idea but there was a bunch of things to be fixed and also bunch of things that can be implemented, witch I did.
  • ✅ Instant transition
  • ✅ Auto-next, fade, subtitle, timed triggers
  • ✅ Camera checkpoints, loops
  • ✅ Save scene and presets are fixed
  • ✅ Morphs toggle
  • ✅ Many more
I love the idea and I make edit for myself and I made lot of changes and spent a lot of time on it. I could release it if you approved it....
 

Attachments

  • Screenshot 2025-11-23 014151.png
    Screenshot 2025-11-23 014151.png
    360.6 KB · Views: 0
  • Screenshot 2025-11-23 014212.png
    Screenshot 2025-11-23 014212.png
    333.8 KB · Views: 0
  • Screenshot 2025-11-23 014231.png
    Screenshot 2025-11-23 014231.png
    352.7 KB · Views: 0
  • Screenshot 2025-11-23 014321.png
    Screenshot 2025-11-23 014321.png
    336.4 KB · Views: 0
  • Screenshot 2025-11-23 014343.png
    Screenshot 2025-11-23 014343.png
    334.4 KB · Views: 0
It records plugin states, atomdata, and god knows what else :) Check presets size, its like 500mb lol. I' m working on this, I use it as structure and change almost every line of code. I love the idea but there was a bunch of things to be fixed and also bunch of things that can be implemented, witch I did.
  • ✅ Instant transition
  • ✅ Auto-next, fade, subtitle, timed triggers
  • ✅ Camera checkpoints, loops
  • ✅ Save scene and presets are fixed
  • ✅ Morphs toggle
  • ✅ Many more
I love the idea and I make edit for myself and I made lot of changes and spent a lot of time on it. I could release it if you approved it....
Hey Mo84!
Thanks a lot for the enthusiasm!
I really appreciate that you liked the idea enough to dig into the code and experiment with your own changes. That means a lot to me. 😊

Just so you know - many of those issues are already fixed in the latest version (v8):

✅ File size bloat SOLVED - Was saving morphs/textures/plugins (10K+ lines). Now only saves positions (~200
lines). Went from 500MB to ~5KB per pose.
✅ Morphs toggle - Already implemented. savePluginStates = false by default. Morphs/expressions handled by other
plugins.
✅ Save scene fixed - Excluded all appearance data (skin/hair/clothing/decal layers).
✅ Instant transitions - Physics optimized with velocity zeroing + settling time.

Your features I DON'T have yet:
- Auto-next with fade
- Subtitles
- Camera checkpoints
- Timed triggers
- Loops

These sound really useful!

(A few options:

Option 1: Pull latest PoseSaver v8, add your features on top (clean foundation, no bloat)

Option 2: Release your version as a separate plugin with credit (e.g., "PoseSaver Extended by [YourName], based on
PoseSaver by Kimowal" , could be really valuable for the community!)


About releasing this version:

As of now PoseSaver is still under very active development, and I’m currently working on optimizing the internals, trimming unnecessary data, and improving several systems. Because of that, I’d prefer to keep all public releases unified so users don’t get confused by different versions or forks.


That said, you’re absolutely welcome to experiment and use your modified version privately however you like — and if you have ideas or improvements you think should be in the official plugin, just share them and I’ll gladly take a look.


Thanks again for the feedback and energy — it really motivates me to keep improving PoseSaver! 🔥💜
 
It seems you removed a bit too much information from the pose. :geek:

_
Morphs that are labeled "pose" (e.g. finger bend, JMC,.etc) it would be good to include in the saved POSE
 
I wonder how the internal(VaM) pose loading process works...:unsure:
 
It seems you removed a bit too much information from the pose. :geek:

_
Morphs that are labeled "pose" (e.g. finger bend, JMC,.etc) it would be good to include in the saved POSE
DJESUS!! :ROFLMAO: hold on il get it fixed soon. im about to release a new plugin so im finishing that then i will adress this! SORRY!!
 
I wonder how the internal(VaM) pose loading process works...:unsure:
i tried to make the same problem occur, what i did was posing hand in front of stomach, then behind, in mouth even. but i dont seem to get the same problem, even whit hands in mouth. could you try to use other poses to see if you have the same problem?, maybe it occurs because the hand controller might be dragged too much after placed on the chest?(im just trying to find reasons it happened :ROFLMAO: :)🤗), you could try out https://hub.virtamate.com/resources/microphysics-mixer.62551, it might help also.
 
Last edited:
Thank you so much for creating such an amazing plugin!

This plugin is incredibly easy to use. After registering many of my favorite poses, the thumbnail list on the right side of the screen ended up extending beyond the visible area.

I would really appreciate it if you could add scroll buttons or page navigation buttons to the thumbnail list. Please consider it!
 
Thank you so much for creating such an amazing plugin!

This plugin is incredibly easy to use. After registering many of my favorite poses, the thumbnail list on the right side of the screen ended up extending beyond the visible area.

I would really appreciate it if you could add scroll buttons or page navigation buttons to the thumbnail list. Please consider it!
Thank you for using it! 🤗 i will dont worry, il try to have that implemented next time i do an update, thank you for the feedback :)
 
i tried to make the same problem occur, what i did was posing hand in front of stomach, then behind, in mouth even. but i dont seem to get the same problem, even whit hands in mouth. could you try to use other poses to see if you have the same problem?, maybe it occurs because the hand controller might be dragged too much after placed on the chest?(im just trying to find reasons it happened :ROFLMAO: :)🤗), you could try out https://hub.virtamate.com/resources/microphysics-mixer.62551, it might help also.
I do not know how else to compare the loading of poses..
can you check these poses for yourself?

! name: person (Otherwise, hierarchy of bones will reset)
2025-11-23_120327.jpg
 

Attachments

  • Preset_RIG3 st 10A.vap
    77.7 KB · Views: 0
  • Preset_RIG3 ac 01.vap
    74 KB · Views: 0
I do not know how else to compare the loading of poses..
can you check these poses for yourself?

! name: person (Otherwise, hierarchy of bones will reset)
View attachment 543900
ok tested them, the issue your having is the lhand are set behind the back of the person atom in your pose, this can conflict when changing poses like in posesaver, nor is it ment to be set so far back. i tested by dragging the handcontroll so the hand kinda just touch the breast (but still grabbing) and it worked just fine., its just a matter of correcting the hands in your pose and you should be good.
 
Having a branch of Cheesy's excellent PoseMe for poses only is a great idea.
Have you thought about adding the ability to save additional atoms position/rotation instead of just person/toys?
Maybe limited to just a short list of atoms (eg cua's) that the scene creator needs to give a predefined name to for it to be recognised and stored.
 
ok so ive just posted my new plugin LookCam Assistant(which is why i didnt want it in posesaver, this works along with it :) ) , i have also started a new update for Posesaver but this will not be ready for at least 2-3 hours maybe more(hopefully not.). stay tuned my friends and than you again for your feedbacks and ideas your all truly appreciated:)🙏
 
Having a branch of Cheesy's excellent PoseMe for poses only is a great idea.
Have you thought about adding the ability to save additional atoms position/rotation instead of just person/toys?
Maybe limited to just a short list of atoms (eg cua's) that the scene creator needs to give a predefined name to for it to be recognised and stored.
Nope!! i hadnt and im dynamiccly now hitting my head against the table for not thinking of that! 😁😂🫡 thank you!! il be sure to add it! this was great!!❤️‍🔥
 
Kimowal updated Posesaver with a new update entry:

1.4.3

PoseSaver - Update 1.4.3

1. Additional Atoms Feature (NEW)

- Feature: Save position/rotation of CUAs, props, and other atoms with poses
- How It Works: Atoms with matching name prefix are saved/restored with pose

Backend Implementation:

- New Fields in PoseData:
- saveAdditionalAtoms (bool, default: true)
- atomNamePrefix (string, default: "PoseSaver_")
- additionalAtoms (JSONClass storage)
- Capture Method: CaptureAtomTransform(Atom atom)
- Saves: type...

Read the rest of this update entry...
 
I think I've found a difference from the standard pose loader. Presets from the poses menu are loaded with the (v2) tag, which significantly changes the loading process. I tried editing the pose saved in VAM (I removed this tag), and the poses started to apply exactly the same way in your plugin. When I put the tag back in place, the pose loads much more smoothly, without any jerking or other issues.
I can't say for sure, but you should definitely give it a try.
2025-11-23_174217.jpg
 
Back
Top Bottom