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

[Evo]

Tried, does not work! :C

Do you have BepInEx installed: Same error w/fix

 

[atani]

So far no problem whatsoever. Thank you @Evo

 

[Sally Whitemane]

I think some users download the patch and just copy-paste it into VaM's root folder without reading instructions.
By checking the SkinMeshPartDLL.ini file one can see it's tuned for a 8 (on Intel: Performance-) Core CPU.
Suboptimal if that's not in the PC. It should be tuned manually to match the CPU (Performance-) Core count.

Correct me if I'm wrong ofc. Afaik it does not detect the optimal configuration automatically. It's just that 8 is a good default. It's kinda "mainstream".

 

[ouroborolapse]

Feature Request: a script that auto tunes the ini based on the system

 

[Evo]

I think some users download the patch and just copy-paste it into VaM's root folder without reading instructions.
By checking the SkinMeshPartDLL.ini file one can see it's tuned for a 8 (on Intel: Performance-) Core CPU.
Suboptimal if that's not in the PC. It should be tuned manually to match the CPU (Performance-) Core count.

Correct me if I'm wrong ofc. Afaik it does not detect the optimal configuration automatically. It's just that 8 is a good default. It's kinda "mainstream".

Right, it's the same default config .ini file. If you previously tuned it to your CPU the same settings should still apply.

 

[gghhoosstt123]

I think some users download the patch and just copy-paste it into VaM's root folder without reading instructions.
By checking the SkinMeshPartDLL.ini file one can see it's tuned for a 8 (on Intel: Performance-) Core CPU.
Suboptimal if that's not in the PC. It should be tuned manually to match the CPU (Performance-) Core count.

Correct me if I'm wrong ofc. Afaik it does not detect the optimal configuration automatically. It's just that 8 is a good default. It's kinda "mainstream".

Well i am pretty retarded my self but even i look into the instruction to this to set the ini config accordingly and so far it had worked wonderfully for me so yeah people should really atleast give a few min to the instruction manual. Also glad version 12 was chosen instead of 13.

 

[Case]

I updated V12 because that's what I could use successfully. If there is enough interest in updating the 13beta1 version with these fixes, I can look into doing that as well. 13beta1 was unstable for me. (Share any info if you had that one working)

I'd be interested in an updated 13beta1!

And thanks a lot for your work!

 

[BStarG2]

I agree, an update to include 13Beta1 would be nice, it would give us all the option to try both: one with version 12, one with 13Beta1; and seeing then which one is more stable for us, etc (in my case I've been using 13Beta1 for months without major issues).

Thank you very much for doing this Evo (I'm aware that Meshed is planning to officially include the performance patch in a future VAM1 update, but it will happen after VAM2 Beta 1 comes out, we might still be a few months away from that official update; so in the meantime this will help us upgrade our VAM with the security patches + keeping the extra oomph from the performance patch).

 

[timitnrop]

Do you have BepInEx installed: Same error w/fix

No, what is that?

 

[XHZ]

How to set for 10700KF 3070 ？

 

[qwerty134930]

I updated V12 because that's what I could use successfully. If there is enough interest in updating the 13beta1 version with these fixes, I can look into doing that as well. 13beta1 was unstable for me. (Share any info if you had that one working)

Ack, I had 13beta1 working and I actually updated VAM after seeing this had updated, I should have read the patch notes...
I don't really have any info to add other than 13beta1 was working for me and I had more fps on that version before updating (downgrading?) to 12evo, so I would be interested in a version of that that runs on the latest version of VAM.

 

[Sally Whitemane]

How to set for 10700KF 3070 ？

That's an 8 Core CPU based on official Intel 10700KF specifications:
https://www.intel.com/content/www/us/en/products/sku/199325/intel-core-i710700kf-processor-16m-cache-up-to-5-10-ghz/specifications.html
The patch is already be tuned for 8 Cores 'out of the box'. No manual tuning of SkinMeshPartDLL.ini needed in this case.

Btw. VaM creates a new thread per "Person" in the scene. As result the performance gains should be most noticeable in scenes with more.

No, what is that?

BepInEx is a software to modify games. Very popular for Unity bases games.
Because VaM is Unity based some (mostly expert) user have been using it with VaM too.
If that would have been installed it could have conflicted with the performance patch I guess.

 

[MDKSBG]

In a non-updated VAM, does this script have improved performance compared to the previous version?

 

[vasyapupkin96]

Sorry for stupid question. Is this balanced SkinMeshPartDLL.ini for ryzen 5 7600?

Mine config:
[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
engineAffinity=1,3

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

Chatgpt suggests:
[threads]
# First core = 1
# Skip every second core if SMT is enabled in BIOS.
# For Ryzen 7600, you would use cores 1, 3, 5, 7, 9, and 11.
# If SMT is disabled, you could use cores 1, 2, 3, 4, 5, 6 (but keep the highest performance ones).

affinity=1,3,5,7,9,11

# Set the number of threads per task.
computeColliders=4
skinmeshPart=4
applyMorphs=4

# This will use the maximum number of threads to maximize FPS.
# You can leave this as 4 if you want to balance performance, or adjust depending on scene complexity.

skinmeshPartMaxPerChar=4
applyMorphMaxPerChar=4

 

[stylesi]

Thanks! Upgrading 13beta1 would be nice too as I used it over b12: 13beta1 was more stable for me.

 

[darkesthours443]

Never had an issue with 13beta1 like some have reported here. Have used it for over 6 months, on an extreme basis.

 

[VRCube]

I updated V12 because that's what I could use successfully. If there is enough interest in updating the 13beta1 version with these fixes, I can look into doing that as well. 13beta1 was unstable for me. (Share any info if you had that one working)

"
- Generate less garbage per frame
- Delay garbage collection until we wait for the GPU to render
- Should result in less stutter
- Slightly lower FPS due to delays in the GPU rendering "

I never experienced any issues with it. But these updates did seem important. I don't know how much they helped but I can't imagine he did that for nothing. I'd appreciate having the newest version of the patch updated if you have the time! Really appreciate you working on it, that's for sure!

 

[kretos]

I was using 13b too for long time.

 

[Anand]

I was holding off updating VAM until Performance Patch was also updated to support the security patched release. When Evo released the updated v12, it was great news. But 13b has been stable for me since forever so I hesitated for a while. But I finally decided to bite the bullet and went ahead with Evo's patch of v12.

I took the plunge and updated VAM and then I patched it with Evo's v12. I have not had much time with it, so I don't have much to report yet. But the install went well and everything seems to be back as normal - minus the security hole.

Anyway, it's a long wided way of saying thank you to Evo. (and to MeshedVR for the Security fix)

 

[Evo]

I was holding off updating VAM until Performance Patch was also updated to support the security patched release. When Evo released the updated v12, it was great news. But 13b has been stable for me since forever so I hesitated for a while. But I finally decided to bite the bullet and went ahead with Evo's patch of v12.

I took the plunge and updated VAM and then I patched it with Evo's v12. I have not had much time with it, so I don't have much to report yet. But the install went well and everything seems to be back as normal - minus the security hole.

Anyway, it's a long wided way of saying thank you to Evo. (and to MeshedVR for the Security fix)

Awesome. I'll do 13beta1 too.

 

[Ascend0r]

"
- Generate less garbage per frame
- Delay garbage collection until we wait for the GPU to render
- Should result in less stutter
- Slightly lower FPS due to delays in the GPU rendering "

I never experienced any issues with it. But these updates did seem important. I don't know how much they helped but I can't imagine he did that for nothing. I'd appreciate having the newest version of the patch updated if you have the time! Really appreciate you working on it, that's for sure!

the updated garbage collection is problematic with some things
when garbage collection is delayed stuff like browserassist plugin will crash when enabling var manageent if you have a lot of vars

there should be an option to disable it

 

[kurowan]

I wish there was something inside the game that said "It is applied!" So I could at least now if it's working properly. Running benchmarks for 30 minutes to know is not ideal

 

[BStarG2]

I wish there was something inside the game that said "It is applied!" So I could at least now if it's working properly. Running benchmarks for 30 minutes to know is not ideal

In the description (under Spoilers, FAQ section):

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
------- ---------- --------
1260 SkinMeshPartDLL.dll C:\Games\vam\PerformancePatches\SkinMeshPartDLL.dll