Scenes Tripple Barrel BJ

[Altt]

Altt submitted a new resource:

Tripple Barrel BJ - Tiny redhead takes on 3 big cocks

View attachment 563139

she may be small... but she can take a lot of big cock! watch as she downs 3 cocks and takes load after load in this triple barrel blowjob scene with 28 separate animations that flow fluidly. simply load the scene and enjoy!

View attachment 563138






SPECIAL CREDIT AND THANKS TO THE FOLLOWING CREATORS!

QDARO FOR THE AMAZING LENKA LOOK, VERRY STUNNING I HAD FUN BUILDING APON HER!

GIOVNIYA FOR THE AWESOME LIVING ROOM ENVIREMENT...

Read more about this resource...

 

[SlimerJSpud]

I'm sorry to say, but 179 dependencies for a scene like this is completely out of control. The Sub-dependency list is as long as the direct dependency list. This means you pulled in one thing from somebody else's scene and it pulled in the whole scene. This is called dependency hell. In game, the app only knows how to download everything. Using resources that are not on the hub also means you don't get the benefit of that Hub hosted tag. I'd recommend you look more closely at the resources you use before putting them in a package. The hub has way too many duplicate resources to just click on the first thing you see that looks good. Using a resource that has a lot of dependencies itself causes some of this.

How to package like a pro: a guide on proper VAR building - Guides -

Intro There is a recurring issue with VAR packaging. No one's to blame, really, as there is no guide on how to make a "good" VAR package. I'll try to remedy to that. In short, this guide is for you: If you’re about to post a resource starting...

hub.virtamate.com

 

[Altt]

I'm sorry to say, but 179 dependencies for a scene like this is completely out of control. The Sub-dependency list is as long as the direct dependency list. This means you pulled in one thing from somebody else's scene and it pulled in the whole scene. This is called dependency hell. In game, the app only knows how to download everything. Using resources that are not on the hub also means you don't get the benefit of that Hub hosted tag. I'd recommend you look more closely at the resources you use before putting them in a package. The hub has way too many duplicate resources to just click on the first thing you see that looks good. Using a resource that has a lot of dependencies itself causes some of this.

How to package like a pro: a guide on proper VAR building - Guides -

Intro There is a recurring issue with VAR packaging. No one's to blame, really, as there is no guide on how to make a "good" VAR package. I'll try to remedy to that. In short, this guide is for you: If you’re about to post a resource starting...

hub.virtamate.com

ok ill look into that, wasn't sure why mine were so big compared to others and assumed removing referenced dependency's would change or alter the scene. negligent on my part for not trying, appreciate the feedback I'll get that sorted out!

 

[SlimerJSpud]

Yeah, one of my scenes had a similar problem where the plugin used to make a fireplace flicker was from another scene, not the original author of the plugin. It added about 30 extra dependencies from that other scene till I sorted that out. Good luck!

 

[Case]

ok ill look into that, wasn't sure why mine were so big compared to others and assumed removing referenced dependency's would change or alter the scene. negligent on my part for not trying, appreciate the feedback I'll get that sorted out!

Please do that - I came here to say the same thing as @SlimerJSpud: This looks very interesting, and I'd be happy to give it a positive review, but ~180 dependencies ... that's the bad old days of "cascading dependencies", when people got together to build the guide Spud already showed you. The first rule is that you need to package on a clean installation - every time the packagemanager tells you it's missing a resource, you copy that resource over to your clean installation. Rinse, repeat. There's other things to learn & pay attention to (in the guide!), but everything follows from that first step.

(Take care that you remove ANY references to packages from wolverine333, cgomes etc - those really badly packaged old stuff that tends to hang around like dustbunnies from hell)



P.S.: (OPTIONAL!) If you know how hardlinks work, additional installations hardly cost any diskspace - about 99% of the size of a VaM installation is from the assets in [VaM_ROOT]\Virt-A-Mate Big\VaM_Data\StreamingAssets\... Those can't be changed except by MeshedVR (and afaics, they haven't been changed in years). That means you can use hardlinks to use the assets from one installation for ALL your installations! So what you do is:
0) Get Link Shell Extension & read the manual (https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html). Congrats! Now you can create softlinks and hardlinks from your context menu!
1) Create a new VaM installation.
2) Go to [NEW_VaM_ROOT]\Virt-A-Mate Big\VaM_Data\StreamingAssets\ and delete everything there.
3) Go to [ORIGINAL_VaM_ROOT]\Virt-A-Mate Big\VaM_Data\StreamingAssets\ and mark everthing there.
4) Right-click, select "Pick Link Source"
5) Go back to [NEW_VaM_ROOT]\Virt-A-Mate Big\VaM_Data\StreamingAssets\, Right-Click, select "Insert as >" > "Hard Link", left-click.

Congrats! Now you have two VaM installations for the prize (ie size) of one!

 

[Case]

ok ill look into that, wasn't sure why mine were so big compared to others and assumed removing referenced dependency's would change or alter the scene. negligent on my part for not trying, appreciate the feedback I'll get that sorted out!

Yeah, you have TWO old wolverine packages on your installation:

{
"uid": "Wolverine333.maria2_0_2.latest:/Custom/Atom/Person/Morphs/female/AUTO/Nipple Length.vmi",
"name": "Nipple Length",
"value": "0.1172476"
},
{
"uid": "Wolverine333.MIA.latest:/Custom/Atom/Person/Morphs/female/AUTO/Nipple Length.vmi",
"name": "Nipple Length",
"value": "0.5914176"
},

You see how badly those are packaged? Not only is "Nipple Length" a duplicate of a built in morph, it's referenced TWICE, to two different packages. Move both packages (Wolverine333.MIA .... and Wolverine333.maria ...) from your installation, load the look/scene and save again. If memory serves, all the morphs contained in those wolverine looks should also be contained in other hub-hosted morph packages - if Vam doesn't find them in the wolverine333 packages, it will look in other packages & automatically load from there. Then you save again, and the new references get saved.

If there are any morphs you can't find in other packages, send me a PM.

 

[SlimerJSpud]

Duplicate morphs, hair and clothes are a huge problem. Always try to get the OG version rather than somebody else's repackaged one.