Collection Mod Unity Virt-A-Mate Mod Assets: Clothing,Environments,Objects,Scenes,Looks,ect.

5.00 star(s) 5 Votes
Status
Not open for further replies.
Dec 15, 2020
94
492
Cheers everybody,
anyone of you awesome guys happens to have any of these vars?

cotyounoyume.ExpressionBlushingAndTearsFullVer.3
KdollMASTA.KDoll_Mk2.latest
LarrysArms.BlackWidowsOutfit.latest
MK_47.model_Sisters_of_night.latest
Oeshii.Saya_.latest
ReignMocap.ReignMocapBjSitting.latest
ReignMocap.ReignMocapImmersiveDoggy.1
RenVR.(VAR)_Lexi_(REN).latest
Sharr.Two_Draenei.1
vecterror.BrAnJeX.latest
vecterror.EliOls.latest
vecterror.irenethedream2_0.latest
vecterror.KaPe_bla.latest
Vince.Nightie_V-A-C.latest
xinxiu.xinxiushuxiian2.1
Zman.Z_Basic_Lingerie_Set.latest

Thank you for any help!

LOVE, PEACE and shall all your desires be grant
About "KdollMASTA.KDoll_Mk2.latest". I've been looking for it for a while too, since only remake is available on hub\his patreon. I found "KdollMASTA.K_Idol_mk2.5.var" in some archive posted in here before, and fixed meta file in the var requesting that one, and it's seems to work.


Link for remake version if U want to try using her instead, she seems pretty much the same as "2.5" plus new textures.


About "xinxiu.xinxiushuxiian2.1". I've never found it, I heard it's some kind of wind plugin. Should be safe to just remove it from dependecies
 
Dec 15, 2020
94
492
Universens Road Trip parts 1-2. This one was tricky, found out my earlier vaccum's runs decided to delete base female genital normals oO So i included them in here [in different dir so U won't get punished that way like i did]. Fixed the wrong refference for stockings textures. Weirdly enough 1st part was bug free except broken AshAuryn morphs


Oh, this one replaces files: "UniversenS.START.12.var" [well it was a dir not a real var file tho], and "Universens.RoadTrip.1.var"

Gonna edit post after i clean up other scenes. I'm going to post only originally broken ones or multi-parts released 1 by one.

/Update1/
That's was the most bugged thing i saw so far. I have enough of his works for today.
Replaces - ClubLauren-Volume-1+2

 
Last edited:

The_Butcher

Newbie
Aug 28, 2018
70
165
Universens Road Trip parts 1-2. This one was tricky, found out my earlier vaccum's runs decided to delete base female genital normals oO So i included them in here [in different dir so U won't get punished that way like i did]. Fixed the wrong refference for stockings textures. Weirdly enough 1st part was bug free except broken AshAuryn morphs


Oh, this one replaces files: "UniversenS.START.12.var" [well it was a dir not a real var file tho], and "Universens.RoadTrip.1.var"

Gonna edit post after i clean up other scenes. I'm going to post only originally broken ones or multi-parts released 1 by one.
Glad someone else also is trimming the fat off these vars. I notice Vacuum is great at relinking many ref in json files but not smart at deleting. It doesn't use checksum just filename, date and size. I use Varbsorb first to delete dupes since it uses either MD5 or SHA-1 for creating hash of files. I forgot which one was in the code. But varbsorb will not link var ref points correctly so vacuum steps in the relink to other vars with correct syntax. Since varbsorb deleted all the correct dupes, vacuum will not delete anything after. Sometimes if creator was lazy or old vacs, they didn't change to unique file names like"faceD.png". Most male textures use png and females use jpg but vacuum has no idea what is for male or female so it grabs whatever it finds first. Remedy is remove all male resources and then run vacuum and it should link to correct resources for female for example. Like I said before in other posts, many variables to consider.
 

The_Butcher

Newbie
Aug 28, 2018
70
165
He/she said that Dec. 10th will be the deadline for submitting VARs to him/her. Maybe he/she has taken the profile private so that nobody is bothering him/her with questions and new content during finalizing the project? Maybe it takes longer than expected.

EDIT: just noticed that the posts are all deleted, profile is still there and active. Hopefully just because he/she wants to clean up the thread before release :oops:

Just guessing here, but it wouldn't surprise me.
1 rule - one does not speak off project mayhem...lol seriously it is a smart move. Best to let it be forgotten and give torrent a chance to grow. If they are smart, they would give torrent to small trusted few to create a strong hive cluster then release to public. Having 10-20 seeds at launch, obfuscates original uploader better. Best way would be to release torrent on another platform and let that leak torrent here not by user posting.
 
  • Like
Reactions: Nick197801
Dec 15, 2020
94
492
Well, my point is just to make stuff error-free and easier to load up next not linked scene, reducing file sizes is just an addition. I'm not using vaarbsorb, for var dupes i just use error log from VAM. About textures named "FaceD" etc... It's not a "lazy way", there is some logic behind. It's for "Mass import" option inside VAM, so U can import all textures in one click.

I gotta go for a while so maybe someone will be able to help. I'm struggling with LFE light plugin atm, it can't find textures inside var. I tried adding them in ways:
"Light Texture" :"Custom/Atom/InvisibleLight/Textures/spiral.png"
"Light Texture" :"SELF:/Custom/Atom/InvisibleLight/Textures/spiral.png"
"Light Texture" :"Universens.ClubLauren_vol1_2.1.var:/Custom/Atom/InvisibleLight/Textures/spiral.png"
They're added in meta file as a full folder, didn't tried to add 1-by-1 yet.
error:
You don't have permission to view the spoiler content. Log in or register now.

Found the correct way.
"Light Texture" : "Universens.ClubLauren_vol1_2.1:/Custom/Atom/InvisibleLight/Textures/spiral.png"
without 'var' at the end QQ
 
Last edited:

_Wolf_

Member
Sep 25, 2017
170
323
Or it may be due to the fact that VAM doesn't utilize all CPU cores?
View attachment 942774


3 atoms, GPU use at 44%, soft body physics ON, and the framerate is tanking (RTX 2060 here).
What everyone needs to know and remember is that the current "unity" build VaM is currently on doesnt allow for the best multicore cpu threading or physic threading to the cpu's. This is not a "performance" issue caused by Mesh, but the version of unity which in 2.0 he will be using the latest build so that 2 years of unity tweaks and updates he can take full advantage of (yes his build is old, Ark still uses an old old ass engine build because upgrading breaks things or wipes them out to force you to re-make it from scratch). And yes, I agree it would be nice to have GPU based physics calculations, but I also understand his reasoning as to not doing that as it will split the user base where some get the better for having product "A" vs "B". Doing so would have had him re-do most if not all his current physic threading and calculations optimizations which would have put features and functions on the back burner, which I prefer to have content & functionality over some optimizations tweaks. Just work with what you got till 2.0 where his basically having to rebuild all of VaM under the new version, then complain that updated tech isn't performing well.
 

Sgrodolo

Member
Sep 1, 2017
261
418
Not my links again, but that's what I found in this thread before:






Thanks everyone for sharing!!!! :love:
Everything apart from the Becky look in the mega is already in the megapack
 
  • Like
Reactions: Nick197801

azel1221

Newbie
Apr 13, 2019
97
200
What everyone needs to know and remember is that the current "unity" build VaM is currently on doesnt allow for the best multicore cpu threading or physic threading to the cpu's. This is not a "performance" issue caused by Mesh, but the version of unity which in 2.0 he will be using the latest build so that 2 years of unity tweaks and updates he can take full advantage of (yes his build is old, Ark still uses an old old ass engine build because upgrading breaks things or wipes them out to force you to re-make it from scratch). And yes, I agree it would be nice to have GPU based physics calculations, but I also understand his reasoning as to not doing that as it will split the user base where some get the better for having product "A" vs "B". Doing so would have had him re-do most if not all his current physic threading and calculations optimizations which would have put features and functions on the back burner, which I prefer to have content & functionality over some optimizations tweaks. Just work with what you got till 2.0 where his basically having to rebuild all of VaM under the new version, then complain that updated tech isn't performing well.
Of the market that likely represents 99% of VAM's user base, . Targeting parity here is like targeting Linux or Windows Phone. He's catering to an extreme minority for nonsensical reasons. No one with any sense is buying AMD GPU's for VR in the first place, Nvidia has a whole suite of exclusive VR features and typically runs circles around AMD in VR performance. There is no good guy in this hardware race, both of these companies are slimey and greedy as fuck run by a colluding Niece and Uncle.
 
Status
Not open for further replies.
5.00 star(s) 5 Votes