• Hi Guest!

    Please be aware that we have released another critical security patch for VaM. We strongly recommend updating to version 1.22.0.12 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)

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

Does anyone know if I install the latest VAM update, how that will impact this?

I had that latest VAM patch but this massive performance improvement (on 5950X) is much more important to me than some security patch, so I replaced the DLL with this faster version, and seems to be working fine with it, and back to "two characters in fancy lighting scene still faster than original VAM with just one". I'll obviously update when this patch is available for new VAM patch but could be ages for that, so not waiting.
 
I had that latest VAM patch but this massive performance improvement (on 5950X) is much more important to me than some security patch, so I replaced the DLL with this faster version, and seems to be working fine with it, and back to "two characters in fancy lighting scene still faster than original VAM with just one". I'll obviously update when this patch is available for new VAM patch but could be ages for that, so not waiting.
I agree. Did the same.
 
I agree. Did the same.
I had that latest VAM patch but this massive performance improvement (on 5950X) is much more important to me than some security patch, so I replaced the DLL with this faster version, and seems to be working fine with it, and back to "two characters in fancy lighting scene still faster than original VAM with just one". I'll obviously update when this patch is available for new VAM patch but could be ages for that, so not waiting.
No improvment, no difference for me on my 12700H (mobile). with ou without CPU patch so my VAM is in now 1.22.06. Bye bye CPU patch.
 
Hate to be the one to ask, but do we know if turtlebackgoofy is actually working on an update, I've only seen mention from MeshedVR of the creator being notified a patch was coming, nothing from the creator to say anything was planned?

Not sure why this fix isn't applied to the main program, surely the two parties could work something out.
 
I have created an updated version of this patch for 1.22.0.7. Let me know how I can help with the review.
If permission is all you are waiting for, then we need to get a hold of turtlebackgoofy, so this update can go online.
 
An updated version which supports VAM's latest update (1.22.0.8) would be much appreciated :)

(not sure if turtlebackgoofy is still active, but asking just in case; thank you)
 
One apparently exists for 1.22.07. I don’t have it. But what I know is it’s stuck in approval process. I understand the person who made the changes rightfully wants to seek turtlebackgoofy’s approval.

But man. Will we ever see it?
 
Is this even developed anymore?
Perhaps the reason why we haven't seen anything in a while is because they want to make sure that the security patches are all sorted first? Considering we just got another one today, it would have made anything released previously obsolete.
 
Perhaps the reason why we haven't seen anything in a while is because they want to make sure that the security patches are all sorted first? Considering we just got another one today, it would have made anything released previously obsolete.
It has been discussed on discord. Meshed has been in contact with the author, and they apparently intend to update it, but responses have reportedly been slow.

Meshed has also opened the idea of including the patch in the Vam core so it no longer needs to be added manually.

Hopefully, the answers well come soon.
 
It works for me, no stutter happened in baseline3, one or two times in patch12
fastest cores: 5, 3
View attachment 338959
INI:
[threads]
computeColliders=6
skinmeshPart=6
applyMorphs=6
skinmeshPartMaxPerChar=6
applyMorphMaxPerChar=6
affinity=1,2,3,4,5,6
#engineAffinity=3,5

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

[profiler]
enabled=1
View attachment 338960
patch12
View attachment 338961

大佬你好,我也是5600,但是使用V13很容易报错too many heap sections。
V12也有同样报错的情况,但频率比V13少。
这是我的参数,想请你帮忙看一下~
boot.config的:
gfx-enable-gfx-jobs=1
gfx-enable-native-gfx-jobs=1

gfx-disable-mt-rendering=0
wait-for-native-debugger=0
gc-max-time-slice=3
job-worker-count=12
single-instance=1



SkinMeshPartDLL的:
[threads]
computeColliders=6
skinmeshPart=6
applyMorphs=6
skinmeshPartMaxPerChar=6
applyMorphMaxPerChar=6
affinity=1,2,3,4,5,6
#engineAffinity=3,5

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

[profiler]
enabled=1

谢谢!
 
After install the Assembly-CSharp.dll.
Can not load sence and morph.
The following the error i got.
Any solution?
I am using a 12900k

!> Exception during Restore of geometry: System.MissingFieldException: Field '.DAZMorph.appliedValue' not found.
at (wrapper dynamic-method) DAZCharacterSelector.DMD<DAZCharacterSelector..RestoreFromJSON> (DAZCharacterSelector,SimpleJSON.JSONClass,bool,bool,SimpleJSON.JSONArray,bool) <0x00079>
at Atom.Restore (SimpleJSON.JSONClass,bool,bool,bool,SimpleJSON.JSONArray,bool,bool,bool,bool) <0x006f0>
 
After install the Assembly-CSharp.dll.
Can not load sence and morph.
The following the error i got.
Any solution?
I am using a 12900k

!> Exception during Restore of geometry: System.MissingFieldException: Field '.DAZMorph.appliedValue' not found.
at (wrapper dynamic-method) DAZCharacterSelector.DMD<DAZCharacterSelector..RestoreFromJSON> (DAZCharacterSelector,SimpleJSON.JSONClass,bool,bool,SimpleJSON.JSONArray,bool) <0x00079>
at Atom.Restore (SimpleJSON.JSONClass,bool,bool,bool,SimpleJSON.JSONArray,bool,bool,bool,bool) <0x006f0>
Try clearing Cache folder
 
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)
 
Back
Top Bottom