• Hi Guest!

    We have posted a new VaM2 dev log on Patreon, starting a monthly cadence of written progress updates between Beta releases. Highlights include the new Gizmos System, Selection Carousel, and Modes System with Context-Specific Editing. Beta1.2 is 15 of 21 items complete.

    Read the full post on Patreon, or follow progress on the public Trello roadmap.

VaM 1.x VAM loses up to 35fps per person atom if "Cycle Select Person Atom" was used

Threads regarding the original VaM 1.x

Nova_eXelon

New member
Joined
Feb 2, 2022
Messages
5
Reactions
4
Hi everyone.

This is hard to describe in one sentence so here we go again (also I don't know if this is a known issue):

After losing FPS seemingly at random I tried out a few things and this is what it came down to:
Screenshot 2026-04-13 223242.png
Screenshot 2026-04-13 223807.png

This is vanilla VAM with nothing extra installed. I made an empty space, forest background, one light source and four person atmos. Where does the difference in FPS come from? Just cycling through every person once and nothing else. Its about 3 FPS per person here but with a fully loaded scene with three person atoms full of plugins, more complex hair and clothing I go from ~128 FPS to ~95 in Desktop Mode just by clicking "Cycle Select Person Atom" once - not even for every person atom! In VR I go all the way down to 25 FPS. So a scene that is totally playable with up to 60 FPS in VR has now come to a crawl. And those FPS don't come back btw. as going into Play Mode again or reloading the scene doesn't cut it. VAM itself needs to be reloaded.

In that heavy scene (I can make screenshots later if needed) I noticed GPU utilization goes from 100% down to ~70%. So my CPU is now somehow the bottleneck (9800X3D, RTX4090, 64GB RAM).
I can get some FPS back by using trigger setups that just disable any plugin that isn't absolutely necessary at that moment. Like Better Bends isn't needed in every pose for example. As if trigger setups aren't a pain in the ass to setup already.

Is this a known issue or a bug or unavoidable?

Some insight would be appreciated.
Thank you!
 
Back
Top Bottom