Home Creators Posts Import Register Favorites Logout

Poll

What version of VaM are you using?

  • 1.22 286
  • 1.21 6
  • 1.20 7
  • 1.19 0
  • Other 2
  • 2023-11-30
  • —2024-08-11
  • 301 votes
{'title': 'What version of VaM are you using?', 'choices': [{'text': '1.22', 'votes': 286}, {'text': '1.21', 'votes': 6}, {'text': '1.20', 'votes': 7}, {'text': '1.19', 'votes': 0}, {'text': 'Other', 'votes': 2}], 'closes_at': datetime.datetime(2024, 8, 11, 21, 1, 6, tzinfo=datetime.timezone.utc), 'created_at': datetime.datetime(2023, 11, 30, 8, 38, 26, tzinfo=datetime.timezone.utc), 'description': None, 'allow_multiple': False, 'total_votes': 301}

Content

Some plugins are not compatible with all versions of VaM, so I would like to know what you guys are using. Please take a moment to select your option. Thanks!(Please note that I only need to know the first 3 numbers, the rest isn't needed.)

Files

Comments

CuddleMocap

GUYS! If you are on 1.21, you can update to 1.22 without buying a new key! In my opinion, 1.22 is far superior, so you should definitely update!!

Bilbo

1.22 is buggy for me in VR using a G2, that is why I stick with 1.21.0.4. The edit menu shell flashes on like a censorship flag with Via.5.cue female orgasm lol! Maybe a plugin glitch, but I need my fave plugins cos I don't have the talent like you have CM lol. May have to have 2 installations if 1.22 is that much better.

mdhut

Do you guys have a tips to improve loading time ? Even with VAM install on a NVMe SSD, it takes time to load VAM and load any scene. My AddonPackages folder has 500 GB of data.

CuddleMocap

Oh dang, yea that's probably a plugin problem. Might want to contact the creator on the Hub. But I do think 2 installations is a good idea anyway! I still have my original 1.20 on a different drive. XD

CuddleMocap

I have seen some people claim that they were able to reduce load times by consolidating all their VARs into a single huge package, but that's quite the process! My recommendation is to have a lightweight installation for playing the game, and a big installation for experimenting with resources. Do a new install and copy your favorite scenes into it. Then auto-download all the dependencies for just those scenes. I think that's a great start.

Jyubei

I've never thought of having older versions, so that's interesting. Been using 1.22 ever since it was updated to that. I believe most (if not all) of your scenes will work best with the newest version, right?

CuddleMocap

Before releasing a scene, I always test it on version 1.20.77.9 to see if it still works. That is the version I was using when I started making content. Back then, Meshed claimed it was going to be the final update for the game, and it stayed that way for almost 2 whole years. So I give people a bit of leniency when they say they never updated past that version. The first time I had an issue with 1.20 was with Witch's Seduction. The skirt won't undress on old versions. Now I'm looking at using newer plugins that require 1.22.

mdhut

Thank both of you. I use a similar tool (VaM Thin Twin). It works great when there is very very few files. However, due to the number of looks that are great, I finally encounter the same issue despite having less files.

MSpeck01

I'm using 1.20.77.9 also. I've spent a lot of money and time with scenes that will only run on 1.20.77.9. That's why I've not upgraded to a newer version. Also Vam Story will not work on my version.

CuddleMocap

Yea, I've been experimenting with VamStory to make an alternate UI and I don't want people to be left behind. Send me a list of a few scenes that don't work with newer versions of VaM, I'll look to see if I can figure out a solution. It's usually the other way around, haha. Also, you could do what I do: Have both 1.20.77.9 and 1.22.0.3 installed in different folders, and use the old version for older content.

MR

I must be using the newest version because that scene *really* worked for me. :)

b b

Ya know , I don't even remember exactly why I didn't like 1.21 / 1.22 , I just remember after trying them I went back to 120.779

b b

Not entirely related to VaM versions , and this may be obvious to some people but not others : Make yourself a "Final-Version of Vam" install with all your favorite scenes and looks that you have tested and are sure you will always want. Then make a secondary install to test and try new scenes. As we all know VaM installs can become unwieldy and messy and performance will suffer eventually. Then every so often update your "Final-Version of VaM" with the scenes and looks you have decided you want to definitely keep.

CuddleMocap

When 1.21 came out, it broke a bunch of scenes and plugins, so I noped my way out of that one real quick. I did the same as you and went back to "old faithful" 1.20.77.9. But version 1.22.0.3 is amazing. It's stable and has tons of awesome new features for creators. I would definitely recommend creating a second install to try it out!

b b

Ah that must of been it. Noted , I'll give 1.22.0.3 a try , thanks.

b b

1.22.0.3 has been going great. I've made it my main build since all my old scenes work fine on it. And yeah there's some nice new features in it. More so for creators , but primarily as a user I'm liking the "lock active clothes" function. I have some scenes where they would like to disappear. There is also some better plug ins for handling CUAs.