Recent content by anomalous822

Alternatively just move the postmagic var out of addonpackages for VR-only users. Personally I've never run into any problems running a bunch of those tiny utility scripts in my default session plugins, but knowing VaM I can certainly imagine carelessly piling on a bunch causing all kinds of...

Actually had some time to play around with the scene, and I have to say very nice work! Performance is surprisingly solid even with 5 heavy JackyCracky looks loaded. Nice variety of positions, alignment is working very well, VR passenger is configured just right (MUCH appreciated). I do have a...

Super late to the party here, but that's just PostMagic, which isn't compatible with VR and causes the "double vision" problem.. JayJayWon has an awesome free plugin called DisablePostMagic which will automatically nuke it during scene loading so you don't have to worry about it. Just add it to...

Just for the future, package naming convention is that you should increment the version number rather than change the package name when releasing an update. Messing with the naming and trying to add your own separate versioning just creates confusion. Which is newer...

I'm not sure what's up with this piece of clothing in particular, but for me when loading in VR it literally tanks my framerate by 90%. First time I loaded it was in a scene and the lag was so bad I had to fully restart VAM because I couldn't even deselect the clothing from the menu.

Best advice for avoiding dependency nightmares: create a separate stripped down VaM install to use as a dedicated packaging environment. Load only the exact dependency vars you need for the scene. Each of the vars that were mentioned are only in the list because a single morph is being used...