Recent content by octobiped

Lots of great plugins have (usually mild) heap size growth issues, such as UIAssist, Audiomate and Orifice Dynamics. The latter recently mitigated this issue by using structs instead of arrays for caching (according to the update notes) but it still happens, because to a certain extent it's...

Yeah, best to stay on that for now, V3 seems to be broken. Just a heads-up: if the memory limit slider is set above 20GB, it's best to decrease it to under 20GB to prevent VAM from crashing with a "too many heap sections" error.

I can confirm lblg's report, V3 does not display any UI elements. I don't know if the backend is still working (I can't test a scene right now, only had time to do a five minute check on the menu) but the frontend seems to be broken on V3. When I went back to V2, the UI window appeared again.

I tested this patch for around four hours in VR and I'm amazed. A complex scene that would lag multiple times per minute (with the GC triggering at random even at small heap sizes) is now running smoothly for ten minutes at a time. I only had a single "too many heap sections" crash in those four...

I'd love to try it out, but I have to be honest: the Patreon for it is still one of the worst I've ever seen. 20 dollars for immediate access is absurd pricing for a plugin, 12 dollars more expensive than VaM's Creator tier, and the same price as Captain Hardcore's full-featured version. On the...

No problem! Here are the values I changed: Stiffness to 0.05 Distance Scale to 1.75 Compression Resistance to 0.05 Collision Radius to 0.025 Collision Power to 0.15 Uniform Sim Strength sliders: Torso to 0.60, Limbs to 0.75 and all the others to 0.85 That makes the character far "squishier"...

No heap related crashes so far, and yes, FPS is tipically in the 150-300 range when soft body physics aren't too intense. I just loaded VAM Produce 69 as a test at its default configurations (no soft body, no HQ physics), and at the song selection screen it hovers around 70-90 FPS, but gets back...

After a few long sessions in VR, I have no issues to report so far. Performance has been more stable compared to patch 12, heap size growth is vastly slower than vanilla when using plugins that induce a "leak", and stutters are indeed way less frequent. No significant FPS problems that I can...

Some additional info on how my system is running, to help compare: - On latest Nvidia driver (551.61) - Virtual memory on automatic - Downloaded latest dependencies for VAM Produce 69 before loading it - 201 gigs of free storage space on C: - Intel XMP enabled in BIOS, RAM at 3600MHz (it's...

I have the exact same build as you, so I tried the same thing and it's loading fine for me. I played one of the songs to get past the song selection screen, and no problems occurred. Could it be some tweak in your boot.config file? I got along really well with kretos' additional recommended...

For the sake of additional info when testing, could you mention what those bugs were? Plus, maybe I or someone else can remember seeing those bugs before the patch. Also, thanks for the update!

I've been seeing this problem way before the patch, it's from vanilla VAM. Try tweaking physics rate and update cap.

Yeah, I felt considerable improvement in VR from doing the boot.config tweak. Excellent find, thank you! Also nice to know that render scale inside VAM isn't helpful for VR performance.

Happens regardless, even if I trigger memory optimization, but not necessarily permanent - perhaps it gets cleaned up over longer editing sessions. Anyway, those were the only "lesser-known" optimization problems I've noticed in VAM that felt worth mentioning, thank you for verifying them :)...

Yes, the problem is how there was performance degradation in the tests with the UI closed. While it's open, I know FPS loss is inevitable. What I found strange is that the more of the UI I loaded, the more the performance dropped afterwards, while it was closed. I figure it's kept in memory...