Any news on when this will be released?I probably will release VAMExcite which is the "brother" plugin of VAMM2 that allows it to work in interactive mode ^^
hey I'm pretty new to VAM all I wanted to do was to add my custom VA pack to the character on other peoples scenes and I finally understood the logic by adding one of the legacy voice packs via button trigger, this legacy VA pack is shared by @VAMFantasy and the files were grouped into 7 groups, these are GROUP_ClaireInt0..... to int4 and also org and prep org groups. I added these groups via Play VA groups automatic button trigger and it worked but it only plays 1 of those groups, my expectation from plugin was detecting the name of the group (for instance if the group name is int0 play that on int 0 stage) and also you say on your VA demo it picks and plays "random" VA file from the loaded ones. if you can add a feature like I explained that changes all vanilla sound files with our owns it would be great, people could use their own VA and sound packs this way. I was using the AudioMate plugin for this use but that plays sounds randomly from the collection and doesn't have intimacy feauture like VAMM2 plus it is a pain in the ass setting it up in a scene cause most of the scenes are using VAMM2
thanks for the reply, I think you think way too professional about "sound libraries", the way I created my audio pack was ripping a audio of porn video and then I cleaned it added compression and equalizer and noise removal, and then I cut the moans and small/dirty talks and lasty properly named them, I ended up with 106 .waw file from a 16 min videoThis has been discussed over and over on both VAMM1 and VAMM2 discussion threads. I've suggested people to send me serious libraries, none of them ever did it. And the amount of people with the skillset or patience to do that is so minimal that my time is better spent elsewhere on my plugins.
The VA system is not tied to the arousal system as it makes no sense. When Excite will be available, it will be a way to control VA based on the arousal.
So that you don't misunderstand me, I'm never against suggestions and ideas. As most of my plugins and discussions show. But I'm also pragmatic and I prefer to work on things that benefit a lot of use case/creators or even simpler, my needs. When I'm spending time doing something for 3 persons, which will probably be used in 2 scenes over 3 years... i'm not spending time on things that will be used widely for every possible scene.
If there is no other solid voice plugin, with serious features and excellent voices, there's a clear reason behind that: money/means and time/knowledge. The moment people see the INSANE amount of time you have to spend to make a voice great, they pretty much drop the ball. And this, with just the VAMM1 complexity. With VAMM2 and it's average 500 to 2000 files per voice, it's even worst.
If there's any "user customizable voice" in the future, it might only be on VAM 2. And I'm saying "might"... not will![]()
Could you possibly advise?
I did go through with update method 1 and it did not resolve the problem. Update method 2 seems irrelevant, because Vammoan or Vamatmospehere are not present in the save file as I've tried to remove them initially to fix it thinking if there are no references to the plugins that are the main suspects in this case then there will be nothing to load and VaM will stop trying to do that. Update method 3 is what I've done first thing when I encountered this issue.Read this tutorial: https://hub.virtamate.com/resources/a-guide-to-updating-vars-and-plugins.27059/
Which gives a couple of hints on why assetbundles could fail. One being having the same var of two different versions. Look at the Fix the dreaded invalid assetbundle error section.
When an assetbundle fails, more or less, the whole assetbundle pipeline fails. So unless you hard reset, pretty much all plugins relying on assetbundles will stop working... hence why you had the issue with VAMA afterwards.
Use the methods in the tutorial, it should fix your issue which is most likely due to versions : )
I appreciate you elaborating on VA, I am indeed very much confused hence everything I said is undoubtedly conjecture.I think you're confusing a couple of things. VA has zero connection whatsoever to assetbundles. It's a simple way of loading multiple audio files in one go... there is absolutely no relationship with the main library loaded as an assetbundle and your potential custom VA files.
The VA system then saves a list of paths to the audio files, which again is not tied to assetbundles.
The whole assetbundle errors both "invalid" or "already loaded" are quite similar. The scene you're working with is simply trying to load either a similar bundle or two different versions. Also note that any plugin using assetbundle will produce the error. So maybe you're thinking that VAMM triggers that, when in fact it's another plugin... which will block/crash the whole assetbundle system for any other plugin.
Send your scene json, or it's unlikely I can do much about it.
I've provided help for years about the assetbundle system... you can trust me when I say that you most likely have missed something and there's 99.9% chance you're mixing several similar bundle in the scene triggering the bug. I work on a daily basis with VAMM1, VAMM2, VAMAtmosphere or VAMStory, and I never ever have any problem with that... this is probably one of the aspect of the plugins that is/was extensively tested over the years.
Also consider any other plugins from creators who could rely on my assetbundles from older versions and could trigger the same behavior.