Misiv's VaM Patch

Plugins + Scripts Misiv's VaM Patch

Download [2.99 MB]
I think the window scrolling falls outside the scope of what anyone would likely want from a CPU patch, I think that should be a separate plugin. I'm going to stay on version 1 because I don't want the window scrolling. I hope you make that optional for any future updates.
 
I think the window scrolling falls outside the scope of what anyone would likely want from a CPU patch, I think that should be a separate plugin. I'm going to stay on version 1 because I don't want the window scrolling. I hope you make that optional for any future updates.

That’s exactly why I’ll need to rename it

“CPU performance patch” will be a misleading name as future updates will also cover gpu performance, ram usage, changes to how vam handles certain tasks to make them faster, and other qol improvements and additions

I’ll make features optional where I can. Most changes will simply be part of the patch

At the end of the day, I’m making this patch for myself cuz I use it. I’m sharing it here cuz if it helps someone else too, why not? 😇
 
I personally love the scrolling so thank you for it. My hands are so shaky that I end up having a vibrating selection screen. :D
 
No. This patch works with all cpus. Everyone just needs to configure SkinMeshPartDLL.ini properly for their own processor
Ive been looking everywhere on what to set in the ini? Why is there no instructions? I must be blind.
I have a Ryzen 9 7900X3D
 
Ive been looking everywhere on what to set in the ini? Why is there no instructions? I must be blind.
I have a Ryzen 9 7900X3D
check the credits
1794820109587.png

1794820158312.png
 
... So uh, leancore is gone. No announcement from wanderer, no notifications from the HUB that the plugin was dirty and has been removed.
Anyone know what happened?

Bit worrying that it's disappeared. Typically those things happen due to a security issue.
 
MiSiv updated CPU Performance Patch v2.0 with a new update entry:

Update 2.2

Startup, performance, and QoL improvements

  • CPU Performance Patch 2.0 is now called VaM Patch.

  • VR scroll speed is now consistent regardless of how much content there is to scroll through.

  • VaM starts faster and saves a new VAR index in its main cache folder. Package JSON caches are built in parallel. You can adjust these options in PerformancePatches/Patch.ini

    My startup times on a ~1TB VaM installation...

Read the rest of this update entry...
 
Bug: applyMorphMaxPerChar is read from the wrong section of SkinMeshPartDLL.ini

Desktop: the per-character morph thread limit comes from [threadsVR] applyMorphMaxPerChar. The value in [threads] is ignored.
VR: the limit is always 1, whatever the file says, so morphs are applied on one thread per character.

Cause: In the INI handler, the first check for applyMorphMaxPerChar compares the section against "threadsVR" instead of "threads". It stores the value in the desktop slot and returns. The later [threadsVR] check for the same key can never be reached, so the VR slot keeps its default of 1. Nothing ever reads [threads] applyMorphMaxPerChar.

Fix: Change the section name in that first applyMorphMaxPerChar check from "threadsVR" to "threads".

Test: (desktop, -vrmode None, 1 Person, 60 morphs changing every frame)
I read the limit the patch was actually using from the DLL’s memory while VaM was running, and counted the patch threads that worked on morphs:

[threads] [threadsVR] Limit used Morph threads working
4333
4110
1666

All other desktop settings were read correctly from [threads].

Workaround: On desktop, put the value you want in [threadsVR] applyMorphMaxPerChar. There is no workaround for VR.
 
On desktop.
First impressions after 20 minutes testing.
v2.2 patch in a heavy scene (67gb Ram footprint)) the animations seemed smoother.... by just enough to stand out.
So that's really appreciated! :)
The faster morphs-cloths etc also :)

Question:
Notice for some penetrations that GC causes erratic jumps of 100mb at times, and they add up fast so GC starts to happen way quicker (tracking via Everlasters Performance Monitor).
Use 36gb GC.
At same notice, this starts to drop FPS for some of those penetration scenes.
Move characters to another pose and fps issue settles back down.
**Noticed with latest 2.2, that settling happened in 8 seconds rather than previous 45plus seconds. That was a really nice surprise. Hopefully keeps working that way.

Q: Is there any chance that in the future you could take a look at genital penetration ??
The other soft body physics/collisions all work well by comparison.

fyi:
My Physics settings are:
went to 120hz from 90hz with latest 2.2.
Cap 3
HQ ON.

Not sure if genital penetration physics is an area of concern or interest for you.
Am happy to patreon.

Otherwise, appreciate alot this new big step with 2.2. :)
 
Thank you very much for sharing your work with us—it’s a very useful tool! However, I’ve noticed that it isn’t compatible with other plugins, such as the 'MouseWheelToTabChange' feature found in the 'qvaro UI Tweaks' plugin.
My question, is there any possibility of making it compatible, or perhaps including a mouse-wheel method for switching tabs?
Thanks again! (y)
 
I think the window scrolling falls outside the scope of what anyone would likely want from a CPU patch, I think that should be a separate plugin.
Agree with that. I expect FPS boost things from here only. I am one of those who really need this, as my 10-year-old Xeon E5-2680 v3 strongly disagrees with the parallelization approach used in "vanilla" VAM—an approach that is now implemented in the EVO build. I appreciate that someone is still working on further improvements, but I believe such additions should be considered on how useful they are to all users.
The changes in version 2.2 referred as "outline around Customize" are certainly not useful to everyone; you simply happen to find them useful for your own workflow. Therefore, such features should be completely disableable—for instance, via a boot configuration file or command-line parameters.
I also dislike the changes to package caching; I prefer to keep only the necessary assets in my packages, and with a total size of around 25 GB, it takes only 7 seconds to processing at startup. In reality, there is no improvement in access speed for me—the fact that the JSON data is now unpacked does nothing to optimize the most critical part: texture loading. I would prefer to disable this change entirely.

Furthermore, I’ve discovered a regression, likely linked to the feature referred as "Clothing, Hair, and Morphs tabs now open and switch pages instantly." The clothing interface has actually become slower for me — the tiles update time has increased from ~60 ms to ~200 ms. This is demonstrated in the video: the first part shows switching for patch 2.1.1, followed by patch 2.2, with a frame-by-frame breakdown and approximate timing measurements at the end.

P.S.
I’ve been working on my own patch for a while now, also based on the EVO build (for personal use only, not published). I appreciate that you’ve restored the public API and that you’re continuing development. Consequently, I plan to base my future work on a decompilation of your build. I have some developments that already significantly increase FPS and reduce start time for me. If you're interested, I could explain the concepts (they’re all quite simple). I plan to apply these to your build by decompiling it, though I’m not sure how much time that will take.
 
Is the cache function in the new version an enhancement to the original version's cache function, or a cache function independent of the original version? Will this function still work when the game turns off the cache function?
 
Last update (2.2) breaks UITweaks plugin, I can no longer scroll through pages

!> qdaro.UITweaks:Update() error: System.NullReferenceException: Object reference not set to an instance of an object
at qdaro.UITweaks.TabbedNavBy (.GenerateTabbedUI tabbed, Int32 delta) [0x00000] in <filename unknown>:0
at qdaro.UITweaks.TryNavigateHoveredTabs (Single x) [0x00000] in <filename unknown>:0
at qdaro.UITweaks.Update () [0x00000] in <filename unknown>:0
at qdaro.Utils.LogError(System.String name, System.Exception e)
at qdaro.UITweaks.Update()
!> qdaro.UITweaks:Update() error: System.NullReferenceException: Object reference not set to an instance of an object
at qdaro.UITweaks.TabbedNavBy (.GenerateTabbedUI tabbed, Int32 delta) [0x00000] in <filename unknown>:0
at qdaro.UITweaks.TryNavigateHoveredTabs (Single x) [0x00000] in <filename unknown>:0
at qdaro.UITweaks.Update () [0x00000] in <filename unknown>:0
at qdaro.Utils.LogError(System.String name, System.Exception e)
at qdaro.UITweaks.Update()
!> qdaro.UITweaks:Update() error: System.NullReferenceException: Object reference not set to an instance of an object
at qdaro.UITweaks.TabbedNavBy (.GenerateTabbedUI tabbed, Int32 delta) [0x00000] in <filename unknown>:0
at qdaro.UITweaks.TryNavigateHoveredTabs (Single x) [0x00000] in <filename unknown>:0
at qdaro.UITweaks.Update () [0x00000] in <filename unknown>:0
at qdaro.Utils.LogError(System.String name, System.Exception e)
at qdaro.UITweaks.Update()

And, what are those yellow highlights for?
If it now includes page scrolling patches, they aren't working
1794996666559.png


Add toggle-able modules at least, most of us just want better performance and less clutter 🫠
 
Last edited:
Bug: applyMorphMaxPerChar is read from the wrong section of SkinMeshPartDLL.ini

Desktop: the per-character morph thread limit comes from [threadsVR] applyMorphMaxPerChar. The value in [threads] is ignored.
VR: the limit is always 1, whatever the file says, so morphs are applied on one thread per character.

Cause: In the INI handler, the first check for applyMorphMaxPerChar compares the section against "threadsVR" instead of "threads". It stores the value in the desktop slot and returns. The later [threadsVR] check for the same key can never be reached, so the VR slot keeps its default of 1. Nothing ever reads [threads] applyMorphMaxPerChar.

Fix: Change the section name in that first applyMorphMaxPerChar check from "threadsVR" to "threads".

Test: (desktop, -vrmode None, 1 Person, 60 morphs changing every frame)
I read the limit the patch was actually using from the DLL’s memory while VaM was running, and counted the patch threads that worked on morphs:

[threads][threadsVR]Limit usedMorph threads working
4333
4110
1666

All other desktop settings were read correctly from [threads].

Workaround: On desktop, put the value you want in [threadsVR] applyMorphMaxPerChar. There is no workaround for VR.

I checked it, and you're right. Thanks 🤗 I'll fix it soon
 
Agree with that. I expect FPS boost things from here only.
The changes in version 2.2 referred as "outline around Customize" are certainly not useful to everyone
That's why you can disable these features in the new tab :giggle:

I believe such additions should be considered on how useful they are to all users.
The main goal of this patch is to improve how I personally use vam. I'm not making it for everyone, mainly for myself. I just happen to share it on the hub so others can benefit from it too if they want. I genuinely enjoy tinkering with this stuff, which is also why I try to listen to what other users would like to see changed or improved.

I also dislike the changes to package caching; I prefer to keep only the necessary assets in my packages, and with a total size of around 25 GB, it takes only 7 seconds to processing at startup. In reality, there is no improvement in access speed for me
Furthermore, I’ve discovered a regression, likely linked to the feature referred as "Clothing, Hair, and Morphs tabs now open and switch pages instantly." The clothing interface has actually become slower for me — the tiles update time has increased from ~60 ms to ~200 ms.
25 GB is extremely small. No wonder switching tabs is much faster for you when there's barely anything to load. To put it very simply, when you open tabs, vam normally checks and prepares everything you have. With this patch, it only checks and prepares what you're currently accessing, on the fly.
This is aimed more at people who have significantly more content. Without this optimization, switching tabs and searching for clothing/hair by name, especially morphs, can take a very long time and even cause vam to freeze for a moment. At that point, we're talking seconds, not milliseconds

For cases like yours, with such a small AddonPackages folder, I'll try to make this feature toggleable in the INI configuration file, I'll try to do the same for the other future major features as well 😇

does nothing to optimize the most critical part: texture loading.
Faster texture and asset loading is what I'm currently testing and preparing for the next update. A side effect will be even faster loading of the hair/clothing tabs, because one of the new features will allow multiple images to load simultaneously, so thumbnails will load in batches instead of one by one

I could explain the concepts (they’re all quite simple).
Sure, I'd love to hear it. Maybe you've got a cool idea I haven't thought of.

Thanks a lot for taking the time to look into this and for your honest opinion 🥰
 
Last update (2.2) breaks UITweaks plugin, I can no longer scroll through pages
I don't use UITweaks, so I don't know exactly what's causing the issue. But assuming you mean "scrolling through pages," the plugin might simply have nothing to scroll through because, in 2.2, only the tab you're currently accessing is prepared. That's just my guess, though. I'll investigate it more thoroughly when I have some free time. If I can't make it compatible, there will still be an option for you to disable this patch feature, which I'm planning to add in the next update.

And, what are those yellow highlights for?
Please read the post in Updates 😇
 
Tabs open a lot faster now. Still using VPB/VPM for proper instant speed but it's nice for the few instances where only the native menu does what I need.
 
Back
Top Bottom