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

SortaLewd · May 8, 2025

Anyone else been experiencing crashes with the newer versions? Just recently updated vam and updated this patch and now my vam crashes every so often whereas it very rarely crashed beforehand on the previous vam version before the security patch and the previous cpu performance patch version..

makojira · May 9, 2025

hello. firstly, i want to say that i am an amateur about these kind of things. i have setup a new vam instance since the old instance got me stuck on loading model janie. i managed to get the benchmark to work in the new instance but see no improvement. ive checked with powershell it showed 1136 SkinMeshPartDLL. Also since my CPU isnt listed in the post i set the settings to amd 7800. could anyone help me with this? Thanks!

JC318 · May 9, 2025

SortaLewd said:
Anyone else been experiencing crashes with the newer versions? Just recently updated vam and updated this patch and now my vam crashes every so often whereas it very rarely crashed beforehand.

Yes, I am actually. Do you have more .dlls in where your VaM.exe is?

SortaLewd · May 9, 2025

JC318 said:
Yes, I am actually. Do you have more .dlls in where your VaM.exe is?

Only additional dlls I have are for BepInEx and Reshade.

JC318 · May 9, 2025

SortaLewd said:
Only additional dlls I have are for BepInEx and Reshade.

Dang, was hoping we had the same issue. (Though, I don't recognize those.) For me, even installing this patch on a new copy of VaM causes errors. I figured more people had to have issues with this. By chance, are you using Windows 11 as your OS?

SortaLewd · May 9, 2025

JC318 said:
Dang, was hoping we had the same issue. (Though, I don't recognize those.) For me, even installing this patch on a new copy of VaM causes errors. I figured more people had to have issues with this. By chance, are you using Windows 11 as your OS?

I'm still on Windows 10

Evo · May 9, 2025

SortaLewd said:
Only additional dlls I have are for BepInEx and Reshade.

Search this thread for BepInEx. Related

SortaLewd said:
Anyone else been experiencing crashes with the newer versions? Just recently updated vam and updated this patch and now my vam crashes every so often whereas it very rarely crashed beforehand on the previous vam version before the security patch and the previous cpu performance patch version..

If v13beta1 crashes for you, look at the history and use v12evo. I don't have the bandwidth to figure out why it crashes for some installs and not others.

vamp3003 · May 13, 2025

Hey guys I am currently on the 7800x3d and a 4080 super.
I have a chance to upgrade to the 9800x3d for basically almost no cost.
I assume not much of an improvement in VAM correct?
Would the 9900x3d or 9950x3d give me more? Or not really since they are dual CCD?
I would also probably get the 5090 shortly so unless any of the 9800/9900/9950 helps with that is there a point in upgrading cpu?

poopsecks · May 16, 2025

Should "Desktop" and "VR" CPU optimizations be the same? My Quest 3 is coming in tomorrow and I just wanted to make sure there wasn't anything special i needed to do to the ini file as i just copied and pasted the same settings for the VR sections:

Here is what mine looks like if anyone is curious: It is for my 13900k CPU with the hyperthreading turned off, and according to my bio's my core 5 and 6 are my highest binned cores with the highest frequency so that is why i have the engine physics running on 5 and 6:
Please let me know if iam missing anything important or if there is something I should adjust differently:

[threads]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#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
affinity=1,2,3,4,5,6,7,8
engineAffinity=5,6

[threadsVR]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
affinity=1,2,3,4,5,6,7,8
engineAffinity=5,6
[profiler]
enabled=0

vamp3003 · May 19, 2025

I am assuming this is fine for the 9800x3d? Was using it with the 7800x3d so they are very similar and one CCD.

Code:

[threads]
computeColliders=6
skinmeshPart=6
skinmeshPartMaxPerChar=6
applyMorphs=6
applyMorphMaxPerChar=6
#affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
affinity=1,3,5,7,9,11,13,15
#engineAffinity=1,3

[threadsVR]
computeColliders=6
skinmeshPart=6
skinmeshPartMaxPerChar=6
applyMorphs=6
applyMorphMaxPerChar=6
affinity=1,3,5,7,9,11,13,15
#engineAffinity=1,3
[profiler]
enabled=0

Seraphim · May 21, 2025

makojira said:
hello. firstly, i want to say that i am an amateur about these kind of things. i have setup a new vam instance since the old instance got me stuck on loading model janie. i managed to get the benchmark to work in the new instance but see no improvement. ive checked with powershell it showed 1136 SkinMeshPartDLL. Also since my CPU isnt listed in the post i set the settings to amd 7800. could anyone help me with this? Thanks!

You were gpu bottlenecked in both instances. cpu cant do more because of it. (0.00 wait times)

poopsecks · May 29, 2025

i9-13900k + 7900xtx results:
(avg/min1%/max1%)
Patch HT-ON: 112.14/69.06/263.62
No-Patch HT-ON: 112.59/68.67/230.32
Patch HT-OFF: 112.30/69.30/268.16
No-Patch HT-OFF: 111.79/68.11/212.83

Screenshots of full results:
Patch HT-ON:

No-Patch HT-ON:

Patch HT-OFF:

No-Patch HT-OFF:

Here are my ini's; please let me know if there is something in there I should change to make it run better:
HT-ON ini:

[threads]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
affinity=1,3,5,7,9,11,13,15
engineAffinity=9,11

[threadsVR]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
affinity=1,3,5,7,9,11,13,15
engineAffinity=9,11
[profiler]
enabled=0

HT-OFF ini:

[threads]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#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
affinity=1,2,3,4,5,6,7,8
engineAffinity=5,6

[threadsVR]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
affinity=1,2,3,4,5,6,7,8
engineAffinity=5,6
[profiler]
enabled=0

stylesi · Saturday at 4:29 AM

poopsecks said:
i9-13900k + 7900xtx results:
(avg/min1%/max1%)
Patch HT-ON: 112.14/69.06/263.62
No-Patch HT-ON: 112.59/68.67/230.32
Patch HT-OFF: 112.30/69.30/268.16
No-Patch HT-OFF: 111.79/68.11/212.83

Screenshots of full results:
Patch HT-ON:
View attachment 492891
No-Patch HT-ON:
View attachment 492890
Patch HT-OFF:
View attachment 492892
No-Patch HT-OFF:
View attachment 492889

Here are my ini's; please let me know if there is something in there I should change to make it run better:
HT-ON ini:

[threads]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
affinity=1,3,5,7,9,11,13,15
engineAffinity=9,11

[threadsVR]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
affinity=1,3,5,7,9,11,13,15
engineAffinity=9,11
[profiler]
enabled=0

HT-OFF ini:

[threads]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
#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
affinity=1,2,3,4,5,6,7,8
engineAffinity=5,6

[threadsVR]
computeColliders=8
skinmeshPart=8
skinmeshPartMaxPerChar=8
applyMorphs=8
applyMorphMaxPerChar=8
affinity=1,2,3,4,5,6,7,8
engineAffinity=5,6
[profiler]
enabled=0

You're sure it is running ok?

Do this to check:

How do I check if the patch is running?

Open vam, wait until you see the main menu. Then open powershell and execute
Code:

Get-Process | select VaM.exe -expand Modules -ea 0 | where {$_.ModuleName -like 'skinmeshpartdll.dll'}

If its running, it should output

Size(K) ModuleName FileName
------- ---------- --------
11136 SkinMeshPartDLL.dll X:\VAM\PerformancePatches\SkinMeshPartDLL.dll

Get-Process | select VaM.exe -expand Modules -ea 0 | where {$_.ModuleName -like 'skinmeshpartdll.dll'}[/ICODE]

poopsecks · Saturday at 5:16 PM

stylesi said:
You're sure it is running ok?

Do this to check:

Open vam, wait until you see the main menu. Then open powershell and execute
Code:

Get-Process | select VaM.exe -expand Modules -ea 0 | where {$_.ModuleName -like 'skinmeshpartdll.dll'}

If its running, it should output

Size(K) ModuleName FileName
------- ---------- --------
11136 SkinMeshPartDLL.dll X:\VAM\PerformancePatches\SkinMeshPartDLL.dll

Get-Process | select VaM.exe -expand Modules -ea 0 | where {$_.ModuleName -like 'skinmeshpartdll.dll'}[/ICODE]

Yes, I got that. are my scores too low? What range of scores would be normal for my type of system?

glodomorrapl · Sunday at 6:00 AM

now that i ran this patch for a few sessions, i have to ask - anyone getting consistent improvements with this patch?
like generally it works faster, proven by the benchmarks from earlier. but then it sometimes craps out and tanks performance hard with long and frequent stutters, ironically due to one of the cores being blasted at near 100%

here's an example, same scene, same animation. first one is without the patch, second one is with the patch.

Neovisual · Sunday at 2:33 PM

glodomorrapl said:
now that i ran this patch for a few sessions, i have to ask - anyone getting consistent improvements with this patch?
like generally it works faster, proven by the benchmarks from earlier. but then it sometimes craps out and tanks performance hard with long and frequent stutters, ironically due to one of the cores being blasted at near 100%

here's an example, same scene, same animation. first one is without the patch, second one is with the patch.
View attachment 493897
View attachment 493898

Yea I think it is a hit or miss... the load time of scenes certainly improved, but I also feel that I have better performance on some scenes without the patch.

vamp3003 · Tuesday at 4:22 AM

Anyone running into "too many heaps" crash because of this patch? Hardware should be plenty, 64gb ram, 9800x3d, rtx 5090.
Consistently happens on SlamT scenes for me, and I narrowed it down to this being the issue because if I disable the patch (use the original VAM DLL) the scenes work fine.
I actually used browserAssist to offload every single var so as far as VAM sees, there are basically no vars in the usual location and still happens.

Evo · Tuesday at 1:22 PM

vamp3003 said:
Anyone running into "too many heaps" crash because of this patch? Hardware should be plenty, 64gb ram, 9800x3d, rtx 5090.
Consistently happens on SlamT scenes for me, and I narrowed it down to this being the issue because if I disable the patch (use the original VAM DLL) the scenes work fine.
I actually used browserAssist to offload every single var so as far as VAM sees, there are basically no vars in the usual location and still happens.

I've updated the resource description to make it clearer there are 2 updated versions.

Since there is currently no pattern on what causes v13beta1 to crash for some users, please report your specs if that version is stable for you to at least create some data.

I have an understanding of the memory management changes and can see where the issue might be. If I could utilize time dilation to allow me to fit about 48-96 hours into a 24 hour day, I would probably have time to improve it.

poopsecks · Tuesday at 2:51 PM

vamp3003 said:

I am assuming this is fine for the 9800x3d? Was using it with the 7800x3d so they are very similar and one CCD.

Code:

[threads]
computeColliders=6
skinmeshPart=6
skinmeshPartMaxPerChar=6
applyMorphs=6
applyMorphMaxPerChar=6
#affinity=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16
affinity=1,3,5,7,9,11,13,15
#engineAffinity=1,3

[threadsVR]
computeColliders=6
skinmeshPart=6
skinmeshPartMaxPerChar=6
applyMorphs=6
applyMorphMaxPerChar=6
affinity=1,3,5,7,9,11,13,15
#engineAffinity=1,3
[profiler]
enabled=0

I believe those are the default settings; I believe you can get alittle bit more out of your CPU by changing the settings alittle bit:

I would use the reference the author recommends for that CPU, which is:

computeColliders=8
skinmeshPart=8
applyMorphs=8
skinmeshPartMaxPerChar=8
applyMorphMaxPerChar=8
affinity=1,3,5,7,9,11,13,15

This is my understanding of the guide for the engine affinity:
and for the #engineAffinity you would just list your fastest cores or leave it blank if you don't know, because the 1 and 3 listed in your ini are the default settings and may not be your 2 fastest cores so you would have to check in Ryzen Master if you have an AMD.

For intel; the bios will list your fasetest cores; but affinity numbers will be different based on if you have HT "on" or "off".

vamp3003 · 2025-06-05T14:15:37-0400

Evo said:
I've updated the resource description to make it clearer there are 2 updated versions.

Since there is currently no pattern on what causes v13beta1 to crash for some users, please report your specs if that version is stable for you to at least create some data.

I have an understanding of the memory management changes and can see where the issue might be. If I could utilize time dilation to allow me to fit about 48-96 hours into a 24 hour day, I would probably have time to improve it.

Yes was using patched13beta1evo and then someone suggested to use patched12evo and it no longer crashes.
Is v12 missing any perf gains in comparison?

Evo · 2025-06-05T19:47:11-0400

vamp3003 said:
Yes was using patched13beta1evo and then someone suggested to use patched12evo and it no longer crashes.
Is v12 missing any perf gains in comparison?

v13beta1 is actually slightly lower gains but reduced how often stutters occur

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

Member

New member

Attachments

Member

Member

Member

Member

Active member

New member

Member

New member

Active member

Member

Active member

Member

New member

New member

New member

Active member

Member

New member

Active member

Similar threads