Scenes Slut show - Your personal Exhibition Hall

[supperGR]

This is great news, I find it takes 5-10 minutes loading from a fast SSD with a core i7-14700k - the part that takes the time is the Atom Contents bit, sometime seems to tie things up there,

The Scene is fantastic, every time I load it up I find new features, I saw you credited the walking to Reign Mocap, which scene is it from? I love the muscle flex morphs in it and can't find those in a Reign Scene? Thanks

Hi!

Yes, load time is exactly the main issue I’m focusing on right now. Of course, loading speed varies a lot depending on how many VARs someone has in their AddonPackages folder, but even in a relatively clean test VAM install, SlutShow still takes a very long time to load.
That’s actually the core reason why I created scenes like “Under the Ocean” "Afterlife of an Angel" and more recently “SnapSHOT!” as standalone projects — to offload and isolate heavy systems from SlutShow and reduce its overall complexity.

Based on what I learned while building SnapSHOT!, I’ve started porting its custom core plugins back into SlutShow. These plugins are now used to manage hundreds of pose states and the current eight color theme systems. By hard-coding a lot of repeated logic into dedicated managers, I was able to significantly reduce JSON size and redundancy.
At this point, both major core plugins have been mostly migrated successfully. In my personal editing VAM setup (around 2000 VARs), the original v71 version took about 9 minutes to fully load. With the current optimized build, load time is down to around 5 minutes. I’m still fine-tuning logic details, and once things are stable, I’ll release an update.

Regarding the walking timelines: they actually come from two different sources. The first (and probably the one you noticed) is from ReignMocap’s “RM-WalkEnhanced”, along with his excellent free scenes. Unfortunately, it seems he has already left the HUB .
The rest come from my old timeline collection, originally created by MK_47 — thanks for reminding me, by the way! I realized I forgot to credit him properly in the UI during the last update . Sadly, he also left the community long ago, and those resources are no longer available. This is basically my way of keeping those great animations alive and visible.

As for the realistic muscle shaking you mentioned — that credit goes to CheesyFX’s ShakeIt plugin, which does a fantastic job there.

 

[supperGR]

supperGR updated Slut show - Your personal Exhibition Hall with a new update entry:

Major Core Refactor & Performance Update

Ver.75
Update – Devlog (Major Performance & Core Refactor)​

Separated the SnapSHOT module and replaced core logic with dedicated plugins, significantly reducing duplicated logic and greatly shrinking overall JSON size.

Based on early testing, load times show a clear improvement.
In my editing VAM setup (approximately 2000 VARs), the original v71 version required around...

Read the rest of this update entry...

 

[mikeriko]

sry but is there any future plan to bring the snapshot back so it could be just one scene again? or perhaps making snapshot into plugin or subscene so that we can add it into scene ourself?

 

[supperGR]

sry but is there any future plan to bring the snapshot back so it could be just one scene again? or perhaps making snapshot into plugin or subscene so that we can add it into scene ourself?

No worries, that’s a very reasonable question

Ideally, yes — having everything inside a single scene would absolutely make sense, and from a management and user perspective it would be cleaner and more convenient. I originally designed it that way as well.

However, the reality I had to face is performance. VAM’s engine is quite old, and once a scene reaches a certain level of complexity, it starts to struggle — not only with FPS, but especially with load times. I received a lot of feedback from users saying that long loading times significantly reduce their motivation to even open the scene, and that’s something I couldn’t ignore.

That’s the main reason I made the difficult decision to separate Snapshot. After splitting it out, I was able to develop dedicated core plugins specifically for Snapshot, and they work quite well in isolation. That said, they’re not “perfectly portable” yet. While the logic data size has been reduced dramatically, the number of UI elements that need to stay head-locked is still quite large, which makes reintegration non-trivial.

So yes — if I can further reduce atom and UI overhead in the future, re-integration is absolutely something I’d like to explore again. For now, keeping Snapshot separate is the best balance I’ve found between usability, performance, and long-term maintainability.

Thanks for asking — feedback like this genuinely helps shape where the project goes next