• Happy Holidays Guest!

    We want to announce that we will be working at reduced staffing for the holidays. Specifically Monday the 23rd until Jan 2nd.

    This will affect approval queue times and responses to support tickets. Please adjust your plans accordingly and enjoy yourselves this holiday season!

  • Hi Guest!

    Please be aware that we have released a critical security patch for VaM. We strongly recommend updating to version 1.22.0.7 using the VaM_Updater found in your installation folder.

    Details about the security patch can be found here.
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)

Try to close HT and set affinity=1,2,3,4,5,6,7,8

I did previously and I don't know if it really helped any, but I can try again. This time I also have ProcessLasso telling my VAM specifically to set CPU affinity to 0-15/P-cores, and enabled "high performance" profile for good measure, which is the first thing to make a noticable difference. But yeah I'll switch back to disabled HT and that SkinMesh.ini affinity setting.

EDIT: No difference with HT off and 1,2,3,4,5,6,7,8 affinity. I'm honestly gonna' switch back because I feel like my overall computer performance was a touch better.
 
Last edited:
I did previously and I don't know if it really helped any, but I can try again. This time I also have ProcessLasso telling my VAM specifically to set CPU affinity to 0-15/P-cores, and enabled "high performance" profile for good measure, which is the first thing to make a noticable difference. But yeah I'll switch back to disabled HT and that SkinMesh.ini affinity setting.

EDIT: No difference with HT off and 1,2,3,4,5,6,7,8 affinity. I'm honestly gonna' switch back because I feel like my overall computer performance was a touch better.
Ya, IMO It's not worth dropping HT or SMT just for VaM. I mean unless your using your PC Only for VaM, then sure? But I'd hope that's not the case, no offense to anyone :p
 
will check why resolution has such a big influence, maybe it influences physx somehow?
I'm running 1080p benchmark right now. Will update this post with results momentarily. But right now I'm like 100+ more FPS then when in 4k res.

Alright, so I may have accidentally adjusted the window screen size during the benchmark, and it caused a hickup. But either way, there is definitely a difference is PhysicsTime(ms), TotalTime and FPS.
1707926194854.png

1707926263133.png
 
Last edited:
...okay I feel extra dumb now. How do you want me to send it to you? I can't put a zip here and I can't seem to attach files in conversations either.

Though, at least someone else noted in the Benchmarks thread that there's a big difference in resolution between everything I'm running and what trety ran. They were only running 1080p and I'm running 2160p.

Here's my bench with 1080p (at 144Hz):

View attachment 334979
just uplod it anywhere and send me a link in DM
 
I'm running 1080p benchmark right now. Will update this post with results momentarily. But right now I'm like 100+ more FPS then when in 4k res.

Alright, so I may have accidentally adjusted the window screen size during the benchmark, and it caused a hickup. But either way, there is definitely a difference is PhysicsTime(ms), TotalTime and FPS.

Did you try the powershell scripts in https://hub.virtamate.com/threads/c...cs-up-to-60-more-fps.49738/page-9#post-149351
 
So, Just for the hell of it, I went and downclocked my CPU back to Factory 3.7GHz. Gots the same FPS, just worse Timings.
1707933348512.png
Gonna go OC it back to 4.55GHz

Will Resizable BAR do anything in VaM?
 
...okay I feel extra dumb now. How do you want me to send it to you? I can't put a zip here and I can't seem to attach files in conversations either.

Though, at least someone else noted in the Benchmarks thread that there's a big difference in resolution between everything I'm running and what trety ran. They were only running 1080p and I'm running 2160p.

Here's my bench with 1080p (at 144Hz):

View attachment 334979
Also dont know variations in his and your ram speed/timings, cpu/gpu voltages/overclocks. So variations in benchmarks should still be expected.
 
So, it's happened twice now, since using this patch, VaM has crashed on me. The error is Too Many Heap Sections have been reached. I've never gotten this error before using this patch.
Once it happened after loading a few scene consecutively one after another, yesterday.
And just now it happened with a borderline empty scene, with one person, that was sitting there idle for about 10mins. Came back, clicked something and it crashed.
This is what pops up immediately after getting the Too many heap sections error
1707939018365.png
 
So, it's happened twice now, since using this patch, VaM has crashed on me. The error is Too Many Heap Sections have been reached. I've never gotten this error before using this patch.
Once it happened after loading a few scene consecutively one after another, yesterday.
And just now it happened with a borderline empty scene, with one person, that was sitting there idle for about 10mins. Came back, clicked something and it crashed.
This is what pops up immediately after getting the Too many heap sections error
Do you have a file in C:\Users\Admin\AppData\Local\Temp\MeshedVR\VaM\Crashes ?
"Too many heap sections reached" occures if you are out of physical memory, I wonder what VaM is allocating, my patch doesnt allocate heap sections that it doesnt immidiatly free.
 
I don't know if it's due to this patch or I just never noticed it before, but when I'm using the Q3/Steam Link, I get better FPS if there is a window sitting on top of the blank VAM display on the desktop. Doesn't matter which one or how big it is, there's a stutter that goes away as soon as something bumps VAM from the foreground. VAM is just a blank black window, not even a mirror of the VR display, so I'm not sure why obscuring it would have any impact, but it definitely does.
 
I don't know if it's due to this patch or I just never noticed it before, but when I'm using the Q3/Steam Link, I get better FPS if there is a window sitting on top of the blank VAM display on the desktop. Doesn't matter which one or how big it is, there's a stutter that goes away as soon as something bumps VAM from the foreground. VAM is just a blank black window, not even a mirror of the VR display, so I'm not sure why obscuring it would have any impact, but it definitely does.

I have literally always observed this on the Index/SteamVR and thought I was crazy. Glad to know I'm not...about this. >_>;
 
Uhm, even before the patch, i was disabling HT since my 10900k+3090 build. It just needed for VaM1.x\Intel. This system was able to game AAA games\blender-max stuff just fine.
Same comes to 13900k+4090 now. It's beefy enough to handle anything these days since we're already 'bottlenecked' by current gen consoles.
 
Fresh Vanilla VaM, yum:

Benchmark-20240204-231033.png



Patched:
Benchmark-20240214-223852.png

SMT off
[threads]
computeColliders=6
skinmeshPart=6
applyMorphs=6
skinmeshPartMaxPerChar=3
applyMorphMaxPerChar=3
affinity=1,2,3,4,5,6,7,8

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

[profiler]
enabled=0
 
Last edited:
I have a pretty old machine.

CPU: i7-7800X
GPU: Asus GeForce GTX 980

Would I be able to use this? If so, what settings would be recommended?
 
Try this
[threads]
computeColliders=4
skinmeshPart=3
affinity=1,2,3,4,5,6,7,8,9,10,11,12

[threadsVR]
computeColliders=4
skinmeshPart=3
affinity=1,2,3,4,5,6,7,8,9,10,11,12

[profiler]
enabled=0

You should adjust this value
skinmeshPart=3

The 3d is not the same, it has different things.
I tried these settings and also setting everything to 6 and both results the same, fps dropped massively.....
 
Maybe it works for me, I just don't feel it, I don't know why my GPU and CPU never get full usage when I play VAM.
 
Do you have a file in C:\Users\Admin\AppData\Local\Temp\MeshedVR\VaM\Crashes ?
"Too many heap sections reached" occures if you are out of physical memory, I wonder what VaM is allocating, my patch doesnt allocate heap sections that it doesnt immidiatly free.
Yes I do have one from each of the two crashes. Is there a particular part you are looking for from it? It contains some personal info, so I wouldn't post it without sifting through the whole thing first. It does note that my systems total physical memory used at the time of crash was only 59%.
 
I tried these settings and also setting everything to 6 and both results the same, fps dropped massively.....
These settings are for version 11, I haven't had time to test version 12.
My BIOS is default, no OC or Ryzen Master (I just changed the XMP profile of the RAM).
Unless you have a RTX 5090 Ti :LOL:, MacGruber benchmark causes GPU bottleneck, better use "CPU High Physics Benchmark" which is default in Vam together with MSI Afterburner to see CPU usage (maybe not all cores and threads are used).

Baragus did not see the increase until he changed benchmarks (150 to 190 FPS).

 
Yes I do have one from each of the two crashes. Is there a particular part you are looking for from it? It contains some personal info, so I wouldn't post it without sifting through the whole thing first. It does note that my systems total physical memory used at the time of crash was only 59%.

In the file C:\Users\Admin\AppData\Local\Temp\MeshedVR\VaM\Crashes\Crash_[DATE]\error.log
Only the entry between
Stack Trace of Crashed Thread XXXX:
(lots of lines)
and
Stacks for Running Threads:
 
These settings are for version 11, I haven't had time to test version 12.
My BIOS is default, no OC or Ryzen Master (I just changed the XMP profile of the RAM).
Unless you have a RTX 5090 Ti :LOL:, MacGruber benchmark causes GPU bottleneck, better use "CPU High Physics Benchmark" which is default in Vam together with MSI Afterburner to see CPU usage (maybe not all cores and threads are used).

Baragus did not see the increase until he changed benchmarks (150 to 190 FPS).

weird that macgrubers benchmark causes GPU bottleneck, the graphics are kinda... 2015-ish lol
 
Back
Top Bottom