• Hi Guest!

    We are extremely excited to announce the release of our first Beta1.1 and the first release of our Public AddonKit!
    To participate in the Beta, a subscription to the Entertainer or Creator Tier is required. For access to the Public AddonKit you must be a Creator tier member. Once subscribed, download instructions can be found here.

    Click here for information and guides regarding the VaM2 beta. Join our Discord server for more announcements and community discussion about VaM2.
  • Hi Guest!

    VaM2 Resource Categories have now been added to the Hub! For information on posting VaM2 resources and details about VaM2 related changes to our Community Forums, please see our official announcement here.

VaM 1.x V2s Universal Morph Collection is gone, all of my VARs are no longer Hub Hosted!

Threads regarding the original VaM 1.x

Mhunter047

Active member
Joined
Feb 26, 2022
Messages
80
Reactions
173
V2s Universal Morph Collection is gone, and this is really hosing up a lot of my scenes as far as sharing them. The morphs contained in there have spread to so many poses and Via5's CUE has also referenced to it. I am not even sure how to remove that reference.

I have cleared this reference from some of my scenes and reposted them. One of them I cannot find the Morphs in any pose, but it seems to get activated by CUE. I removed the Morph package from my VAM install and reopened the scene. CUE was now calling for a different version of the same morphs and worked fine. I saved the scene and went into package builder to try and create a new VAR. It came back as BROKEN - MISSING PACKAGE! So, it seems that CUE is referencing this MORPH package in the background and needs to be redirected to a different one.

If I cannot get this reference cleared from my VARs without rebuilding all of the scenes from scratch, then I think I am out of the scene sharing business! Any ideas on how to clear this?
 
I had this problem with some of my scenes. I went through and swapped those morphs out for ones that did the same thing. My scene with Leatherface had 29 pages of morphs I dialed out! I can't find the info, but I was told that the V2 morph collection had been removed by the mods. There's a morph pack by Mr. Cadillac that has most of the same ones.
 
Upvote 0
I had this problem with some of my scenes. I went through and swapped those morphs out for ones that did the same thing. My scene with Leatherface had 29 pages of morphs I dialed out! I can't find the info, but I was told that the V2 morph collection had been removed by the mods. There's a morph pack by Mr. Cadillac that has most of the same ones.
I looked into the Mr.Cadillac morphs, I have those in my "Add Ons" folder, but they don't show up in the Hub with a search. So... they won't help me to get back to Hub hosted. I also searched under TheCreator, his new name and no luck. All of these disappearing VAR packages are a real pain for creators., as if it was easy to create clean files before!
 
Upvote 0
I think most of the morphs I switched to were in the Spacedog.Import_Reloaded_Lite and kemenate.Morphs packs. Yes, it was a pain.
 
Upvote 0
I think most of the morphs I switched to were in the Spacedog.Import_Reloaded_Lite and kemenate.Morphs packs. Yes, it was a pain.
Well, I figured out the problem and fixed it.... with a lot of pain. There were some morphs that had snuck in at some point and they were showing as Spacedog's morphs. Which I was fine with as I was using some of those anyway. But... in the background for some reason, the Packaging system was calling for the Universal Morphs. I figured this out as this time I removed all of the above from my Add Ons folder and they showed up as "Broken File Missing" when I tried to package it, and it showed to be Universal Morphs. So... I removed all of those odd Spacedog Morphs and PRESTO!! it is repaired. Not so much Presto though.... it was a pain as I have about 60 positions in this scene. Isn't this fun! Actually, it must be to some degree because I could have just walked away, but I hate failing!

Thanks for the assistance and even just letting me vent!
 
Upvote 0
Part of the problem is that Vam 1.x allows multiple morphs of the same name in different packages. Vam sometimes seems like a big random number generator. I think sometimes it uses the one from the wrong var, or it's too easy to use the wrong one when you create the scene. That's where you can get package issues when one var is NLA. In my case, it required searching the morph list for the name of one I wanted to swap, unchecking the bad one, and checking the box on the good one. A few hours later, I had a clean package and a hub-hosted var, SMH. I think I read that Vam 2.x will fix this, we'll see.
 
Upvote 0
v2UniversalMorph collection contains a large amount of commercial morphs from Daz. We cannot, at this point, completely reverse the dissemination of the morph pack, but we do not allow its distribution on the Hub. We were not aware that the file was still hosted, and was probably removed due to an unrelated resource of Vecterror's being removed.
 
Upvote 0
v2UniversalMorph collection contains a large amount of commercial morphs from Daz. We cannot, at this point, completely reverse the dissemination of the morph pack, but we do not allow its distribution on the Hub. We were not aware that the file was still hosted, and was probably removed due to an unrelated resource of Vecterror's being removed.

v2UniversalMorph collection contains a large amount of commercial morphs from Daz. We cannot, at this point, completely reverse the dissemination of the morph pack, but we do not allow its distribution on the Hub. We were not aware that the file was still hosted, and was probably removed due to an unrelated resource of Vecterror's being removed.
I completely understand the need to stay in compliance with licensing requirements. But it is a pain to fix things when a refenced package goes away, no reflection on you all though. I imagine keeping things in compliance for the Hub is a pain too! Thanks for all that you all do, and have a great day!
 
Upvote 0
I completely understand the need to stay in compliance with licensing requirements. But it is a pain to fix things when a refenced package goes away, no reflection on you all though. I imagine keeping things in compliance for the Hub is a pain too! Thanks for all that you all do, and have a great day!
Totally understand. This is why we haven't gone as far as to create any blacklists of files or creators. Once it's out there it's out there, after all. It just may not be able to be hosted on the Hub. When possible, we'll try to help direct you to an alternative.
 
Upvote 0
Back
Top Bottom