Anyone else's softbody physics and certain morphs get broken? The patch works well but soft physics now makes female breasts jiggle like water balloons. I'm guessing morph issue could be from another plugin or modding, but soft physics issue only happened for me after the performance patch.
- Thread starter turtlebackgoofy
- Start date
turtlebackgoofy
Well-known member
- Messages
- 222
- Reactions
- Points
- 63
the jiggle happens in all versions of vam if your FPS is lower than your physics rate. It happens because deacceleration wasnt applied often enough and the breast position flew too fast and out of bounds.
justkiddingbutnot
Member
- Messages
- 34
- Reactions
- Points
- 8
I know of one user who's experiencing them in the same spots during asset loading every time, they say. They also have reduced their morphs quite a bit, as this error (prior to this patch) used to happen primarily when someone had 10,000+ morphs, and this is a known limitation of VAM, but the error persists for them, although I don't know what their total morph count is, but I could find out. Maybe this patch is touching on that and could improve it there. The scene they were using was "Nicho's 2+1 templated".
As for me, I'm not getting the error. I don't aggressively seek out morph packs, though, and I have a 14900K + RTX 3090 + 32GB.
justkiddingbutnot
Member
- Messages
- 34
- Reactions
- Points
- 8
Please share your boot.cfg. "job-worker-count" should equal # of threads, so 16. Also, and turtle may correct me here, but I believe you need to reduce your parameters by the amount of threads reserved for the Unity engine, so set to 14 in your case. When you have it set to 16, that means processes are falling into the hyperthreads, which will cap efficiency at 50/50, because they are one core split into 2 and share the power equally. If you're not using something like ProcessLasso, you might really benefit from disabling HT. It's not that great when you have 8 p-cores, especially when you have twice as many e-cores. It was really great when Pentiums had 1-2 cores. If it wasn't set that way, and you change it, run your benchmark and share again, and let's see what impact that has.
Last edited:
keycode
Active member
- Messages
- 267
- Reactions
- Points
- 28
was it not already mandative to disable hyper-threading to get better profit from the "patch (and as I naively discovered not only from the "patch")?
Last edited:
Is it possible to use this patch and raytracing using this guide? https://hub.virtamate.com/resources...-only-for-nvidia-gpus-and-desktop-mode.14288/
It involves renaming the executable so I suspect it might not hook correctly like that.
It involves renaming the executable so I suspect it might not hook correctly like that.
turtlebackgoofy
Well-known member
- Messages
- 222
- Reactions
- Points
- 63
it will work
As is? No editing required? Weird, I had bad fps when following this guide even when I turned ray tracing off.
turtlebackgoofy
Well-known member
- Messages
- 222
- Reactions
- Points
- 63
when you rename the VaM_Data folder you just need to the patched Assembly-CSharp.dll into the renamed folder, so its at the same location as before you renamed the folder (ergo doing nothing)
Yep, I use this patch with the SOTTR.exe/SOTTR Data SSRTGI GeForce Experience overlay and it works great in desktop, so it might be something else bottlenecking your fps.
On a related matter, don't use the last two GeForce Experience driver updates as they screw with the SSRTGI overlay settings being saved. Last stable version is 546.65
What happens when you run it in VR?
Well firstly, I don't think you even see the ray tracing effects while in VR, and then it just slows everything down. I've only ever tried it once in VR with it enabled.
mori_e
New member
any performance benefits from using sotr.exe instead of vam.exe?
Only benefit is being able to use the GeForce Experience overlays in SOTTR. I've run both vam.exe and sottr.exe with this patch in desktop and the fps etc are the same.
Rickyziggy
New member
- Messages
- 7
- Reactions
- Points
- 3
I Have this: AMD EPYC 7543P 32-Core Processor 2.80 GHz
( Shadow PC) What settings should I have?
( Shadow PC) What settings should I have?
Also having the heap issue with larger scenes. I tried loading it without the patch and it loads fine. It seems that for some reason the heap is not clearing when it gets large while loading the scene using the patch.
Without Patch:
- Heap size grows to ~27 GB, automatically triggers memory optimization, falls back to ~12 GB, repeats until scene is loaded
With Patch
- Heap size grows over ~27 GB and get Fatal gc error: Too many heap sections
As a workaround using patch, you can manually trigger memory optimization in Performance 2 tab to clean up the heap when it grows big while loading the scene but pretty annoying, as you have to manually clean up the heap > 10 times during the load. Not sure if this helps diagnose the issue at all, but just what I'm seeing.
P.S. Amazing patch, thank you for your work on this!
Without Patch:
- Heap size grows to ~27 GB, automatically triggers memory optimization, falls back to ~12 GB, repeats until scene is loaded
With Patch
- Heap size grows over ~27 GB and get Fatal gc error: Too many heap sections
As a workaround using patch, you can manually trigger memory optimization in Performance 2 tab to clean up the heap when it grows big while loading the scene but pretty annoying, as you have to manually clean up the heap > 10 times during the load. Not sure if this helps diagnose the issue at all, but just what I'm seeing.
P.S. Amazing patch, thank you for your work on this!
rabbit1qaz
Active member
- Messages
- 300
- Reactions
- Points
- 28
Im not sure about performance. i use it only to get nvidia screenshot with alt+f1
it do not even work with nvidia overlay like Fake Ray tracing, i do not know why it do not work, if i run clean instal of vam it work but with 10K vars and plugins and reshade it give info that application is not supported though screenshots and recordmovie works
FreeMaster69
Active member
- Messages
- 120
- Reactions
- Points
- 28
Mine didn't completely stop opening but it did slow down after 3 or 4 scene loads. I am going to try your suggestion.
stylesi
Active member
- Messages
- 111
- Reactions
- Points
- 43
Hmmm, I do get this sometimes, not too often though.
turtlebackgoofy
Well-known member
- Messages
- 222
- Reactions
- Points
- 63
I just wondered, are you able to download older versions of this resource?
stylesi
Active member
- Messages
- 111
- Reactions
- Points
- 43
turtlebackgoofy
Well-known member
- Messages
- 222
- Reactions
- Points
- 63
nah, just wondered if my beta release blocked the stable oneVia history tab, yes!
New release?
stylesi
Active member
- Messages
- 111
- Reactions
- Points
- 43
awww, beta is stable for me!
Is your Performance mod btw compatible with FSR mod? I.e. this
GitHub - fholger/openvr_fsr: Add Image Upscaling via AMD FidelityFX SuperResolution or NVIDIA Image Scaling to SteamVR games
Add Image Upscaling via AMD FidelityFX SuperResolution or NVIDIA Image Scaling to SteamVR games - fholger/openvr_fsr
github.com
Or this fork of Vrperfkit (original is from fholger too):
GitHub - RavenSystem/VRPerfKit_RSF: OpenVR Performance Toolkit RavenSystem's Fork
OpenVR Performance Toolkit RavenSystem's Fork. Contribute to RavenSystem/VRPerfKit_RSF development by creating an account on GitHub.
github.com
So the question obviously is, that can you use these (or either of these) together with your awesome CPU Performance Patch and get maximum FPS in VaM VR mode?
I'm having the exact same issue, but with the lips on some of my models.
