CPU Performance Patch (Up to 30% faster physics, up to 60% more FPS)

Other CPU Performance Patch (Up to 30% faster physics, up to 60% more FPS)

Download [0 MB]
Overview Updates (4) Reviews (71) History Discussion
Not sure what I am doing wrong, I have an Intel I9-9900k cpu, with an Nvidia 2080 TI GPU. Not sure what settings I should have on this to make it work but when I load up my game, regardless of scene the characters are t-posed, no collission, and If I go to move a character then they stay perfectly still, however I can see their control atoms moving etc, just not the character themselves visibly. Any idea what Ive borked up?
 
JRMprivate12 said:
Not sure what I am doing wrong, I have an Intel I9-9900k cpu, with an Nvidia 2080 TI GPU. Not sure what settings I should have on this to make it work but when I load up my game, regardless of scene the characters are t-posed, no collission, and If I go to move a character then they stay perfectly still, however I can see their control atoms moving etc, just not the character themselves visibly. Any idea what Ive borked up?
Click to expand...
maybe the same issue this person had?
1707499710096.png
 
I think we need a wiki document of best configurations by chip

I have a computer science degree and have built my own machines 4 or 5 times and even I am uncertain if the configuration im using is optimal. I guess I could try out the profiler, but maybe we can create another documentation resource and put our best findings there on a per-chip basis? I can't imagine how confusing this is to someone who does tree work, is a personal trainer, or is in sales and is just here to jerk off.
 
keycode said:
View attachment 333221

the first test is with patch 10 and my 75% cores in linear list (if it means something: my system is windows 11pro, an official upgrade of my really old windows 10):

[threads]
computeColliders=18
skinmeshPart=1
affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18

[threadsVR]
computeColliders=18
skinmeshPart=1
affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18

the second test is with patch 11 (seems better, but besides seeing not relevant lot of "spikes" max-values 400-450fps during the benchm. scenes, I am not sure if it is really a more valid/positive result)

and:
[threads]
computeColliders=6
skinmeshPart=1
affinity=1,3,5,7,9,11,13,15

[threadsVR]
computeColliders=4
skinmeshPart=1
affinity=1,3,5,7,9,11,13,15

what I would ask to @turtlebackgoofy is if I was doing a mistake with computeColliders value in the second test
(because probably I should set computeColliders=1 instead of 6)

ps: sorry if the benchmark has not a whole standard comparative value: my vam is old like me with lot of morphs/vars and not a valid fresh install for sure
Click to expand...
hmm crank up the computeColliders to 24, lets see what happens:

[threads]
computeColliders=24
skinmeshPart=1
affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24

also try disabling perfcores and HT in bios:

[threads]
computeColliders=8
skinmeshPart=1
affinity=1,2,3,4,5,6,7,8
 
@turtlebackgoofy thank you for your hard work. You've a true hero for VAM community! :D

My results as as below,

Normal:

no patch.png


- Results patched on with istruction for Intel 12700K processors. @turtlebackgoofy I hope I've used the correct one? There's 40 FPS gain so I think I did.

1707500679905.png


patched.png


Also I've noticed that dik morph doesn't work correctly, for example:

1707503161287.png


- No patch

dik.png


- Patched

no dik.png
 
I am seeing some potential in optimizing the application of morphs in more complex scenes and when using tittymagic. It's not gonna improve the benchmark, but might improve dancing scenes a lot.
 
Verywell said:
@turtlebackgoofy thank you for your hard work. You've a true hero for VAM community! :D

My results as as below,

Normal:

View attachment 333222

- Results patched on with istruction for Intel 12700K processors. @turtlebackgoofy I hope I've used the correct one? There's 40 FPS gain so I think I did.

View attachment 333223

View attachment 333224

Also I've noticed that dik morph doesn't work correctly, for example:

View attachment 333235

- No patch

View attachment 333233

- Patched

View attachment 333234
Click to expand...
Its not the morph you showed thats messing up, its the local morph, Penis Length. It should be active but it isn't, find it, and adj it a little, and then default it, and it should fix it.
 
Amazing work!!! I also got a 5950x what do you mean by setting the affinity to CCD in task manager, because when i do set affinity in Task manager it shows me multiple CPU selection boxes, which should i chose for the CCD stuff?
 
Few benchmarks from me on 13900k and 4090 at 1444p. I found that using config from readme, works the best from my limited testing.

Clean VAM
from 164fps to 218 fps 32% increase
from 2.72s phys to 1.71s
base_no_affinity.png
patch11_vamHT_patch_affinity.png

VaM with 8k vars
from 129fps to 147fps 13% increase
from 3.44s phys to 2.86s
base2.png
patch11_2.png

Massive performance improvement. Great work!
Sadly VaM with a lot of vars stills has almost 2x slower physic time.
In case you would take a look I'm attaching my ThreadProfile from beefy VaM (rename json to zip).
newplot.png
 

Attachments

  • ThreadProfile.json
    3.2 MB · Views: 0
Last edited:
Lifson said:
Its not the morph you showed thats messing up, its the local morph, Penis Length. It should be active but it isn't, find it, and adj it a little, and then default it, and it should fix it.
Click to expand...
I've also noticed that multiple scenes I have now have shortened lengths. Wasn't the most recent update supposed to fix that? Are we doing something wrong?
 
turtlebackgoofy said:
I am seeing some potential in optimizing the application of morphs in more complex scenes and when using tittymagic. It's not gonna improve the benchmark, but might improve dancing scenes a lot.
Click to expand...
Here's me really hoping you go ahead with this :D . I mostly use dance scenes, and I tried to use Naturalis once. The glute physics tanked my performance so much that I had to disable it and leave only Titty Magic. I have a 5900x.

By the way, I'm under the distinct impression that your performance patch fixed a camera stuttering issue with MMD VMD Player. Not sure, though; perhaps others could confirm.
 
By the way, not sure if this was discussed before but does the automatic Scheduling / Affinity shenanigans by Windows (Power Plans, Performance Mode, etc) and the Chipset Drivers (either AMD or Intel), along the use of Game Mode (in Windows) and GameBar (which should automatically detect when an application is a 'game' and optimize CPUs / CCDs from there) would have any positive or negative impact on what the Patch is trying to accomplish? And also, how about NVIDIA Control Panel's own Threaded Optimizations setting (Auto, by default) which is supposed to offload some operations to the CPU I believe?

I'm asking this because - to be frank - I've been tempering with this since version 8, with all sorts of .INI values, and I have not seen any worse or better performance. It's the same, either way. However, I do already have all those automatic operations going on all over the place in Windows (and everything in the BIOS is pretty much set to Auto, except I believe Core Performance Boost which I did manually set to Enable, but that's it). I did also set VAM as "remember this is a game" in GameBar, and when I monitor the CPU usage with AMD's Ryzen Master app, it does say that only my X3D CCD0 is being used and the other CCD(1) is dormant when VAM runs.

I guess my question is this then: Is the patch trying to do what all those automatic operations do already? And that might explain why in my situation I simply don't see any improvements (neither worse, mind you)?
 
BStarG2 said:
By the way, not sure if this was discussed before but does the automatic Scheduling / Affinity shenanigans by Windows (Power Plans, Performance Mode, etc) and the Chipset Drivers (either AMD or Intel), along the use of Game Mode (in Windows) and GameBar (which should automatically detect when an application is a 'game' and optimize CPUs / CCDs from there) would have any positive or negative impact on what the Patch is trying to accomplish? And also, how about NVIDIA Control Panel's own Threaded Optimizations setting (Auto, by default) which is supposed to offload some operations to the CPU I believe?

I'm asking this because - to be frank - I've been tempering with this since version 8, with all sorts of .INI values, and I have not seen any worse or better performance. It's the same, either way. However, I do already have all those automatic operations going on all over the place in Windows (and everything in the BIOS is pretty much set to Auto, except I believe Core Performance Boost which I did manually set to Enable, but that's it). I did also set VAM as "remember this is a game" in GameBar, and when I monitor the CPU usage with AMD's Ryzen Master app, it does say that only my X3D CCD0 is being used and the other CCD(1) is dormant when VAM runs.

I guess my question is this then: Is the patch trying to do what all those automatic operations do already? And that might explain why in my situation I simply don't see any improvements (neither worse, mind you)?
Click to expand...
Try to use Process Lasso with the following affinity rules:
1707561331414.png

1707561336854.png

On my 13900k it basically means: allow vam to use P cores only and force everything else to switch to E cores (everything except system processes).
I have no idea if it actually makes any difference, didn't test it yet but this it what I'm using since the beginning.
Also in options -> power -> performance mode I added VaM.exe
 
Hi guys
I’m Not much of tech guy.
So I just copy the files and run vam? Or do I need to add codes somewhere also!?
My cpu is i7 12650H laptop with rtx 3060
Many thanks
 
hijku said:
Try to use Process Lasso with the following affinity rules:
View attachment 333467
View attachment 333468
On my 13900k it basically means: allow vam to use P cores only and force everything else to switch to E cores (everything except system processes).
I have no idea if it actually makes any difference, didn't test it yet but this it what I'm using since the beginning.
Also in options -> power -> performance mode I added VaM.exe
Click to expand...
Thanks for your reply.

However, as I mentioned, just using GameBar (probably that alone) does make my VAM use _only_ my X3D cores, as it is what GameBar is supposed to do (at least for the X3D processors). All I have to do is to click on the box that says VAM should be considered as a 'game' and that's it, leave it there and it does the rest automatically. And I can confirm that's the case with Ryzen Master, checking my CPU / CCDs activity, and totally can see that my CCD0 (X3D cores) is the only one active when VAM runs, while the others are on stanby / sleep (and are only activated when I get out of VAM and do other things in the Desktop).

So when it comes to affinity, I think GameBar already was doing it all along, which might explain why with this patch nothing seems to happen (for me anyway), since the patch does seem to attempt doing exactly what GameBar does. In other words, this patch seems to work for people who either don't use GameBar (or didn't apply VAM to it, as a game), or dunno... not sure if that's actually what is happening, it's only a hypothesis.
 
turtlebackgoofy updated CPU Performance Patch (Up to 30% faster physics, up to 60% more FPS) with a new update entry:

Bugfixes, faster morphs and easier thread settings

- Doesnt use AVX anymore, it didnt bring any benefit turns out
- Fixes the bug when a default morph is not applied when copied from one character to another until it was changed
- Morphs are a lot faster now if you have Naturalis or other Plugins that add dozens of morphs
- Complex characters with lots of applied morphs are faster now. This is not noticeable in the benchmark scenes.
- Now can just bruteforce the threadcount if you dont care about power consumption or thermal throtteling
Click to expand...

Read the rest of this update entry...
 
turtlebackgoofy said:
Instead of running those costly functions in C# they get processed faster in native code optimized for AVX2.
Click to expand...
Nice. But still, yikes, and my CPU doesn't handle AVX2 unfortunately. Hope this does end up implemented at least tentatively as an option in the base game. Maybe talk Meshed up and see if you can't get at least a couple bucks out of it?
 
Singaia said:
Here's me really hoping you go ahead with this :D . I mostly use dance scenes, and I tried to use Naturalis once. The glute physics tanked my performance so much that I had to disable it and leave only Titty Magic. I have a 5900x.

By the way, I'm under the distinct impression that your performance patch fixed a camera stuttering issue with MMD VMD Player. Not sure, though; perhaps others could confirm.
Click to expand...
if your FPS doesnt match the physics rate you get stutters. Now that character processing is faster the next physics update doesnt have to wait for the previous frame anymore and there is no more stuttering.
 
BigBoobCoomBlast69 said:
Nice. But still, yikes, and my CPU doesn't handle AVX2 unfortunately. Hope this does end up implemented at least tentatively as an option in the base game. Maybe talk Meshed up and see if you can't get at least a couple bucks out of it?
Click to expand...
I removed AVX2 and downgraded to SSE in newest version, the AVX2 heated up the cores too much and it actually turned out to be slower than SSE.
 
You must log in or register to reply here.

Similar threads

virtamater
Guides QoL upgrade to spice up old scenes...
Replies
7
Views
139
SlimerJSpud
SlimerJSpud
DemonLord
Guides New CPU or GPU? FPS monitor
Replies
1
Views
409
Sally Whitemane
Sally Whitemane
LDR
Scenes Spicy Teacher Update to V2---More position!
Replies
3
Views
517
LDR
LDR
Boom_bot
Morphs Breast up
Replies
0
Views
470
Boom_bot
Boom_bot
VaMChan
Hairstyles Half up
Replies
0
Views
567
VaMChan
VaMChan
Back
Top Bottom