• 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.
XXXmas gift

Scenes XXXmas gift

Download [15.86 MB]
Thank you for your reply. I checked the Hexenv88.Christmas_prop_pack.1 var, and I think the key issue might be that this var doesn’t contain a file named hexenv88_christmas_props.assetbundle, but instead has hexenv88_christmas_prop_pack.assetbundle.
https://hub.virtamate.com/resources/christmas-prop-pack-in-var-format-requested.13305/
That is odd, I've seen creators remove and release vars under the same name instead of properly updating to a version 2 of the var which is what I'm guessing happened here. So then anyone using it as a reference has no idea something is broken and the var system can't point to a specific older version being used. This also circumvents people getting the usual alerts when a resource they've downloaded has been updated. I believe that is what happened here. I'll have to update scene to use the "updated" var of the same name.

Top is one I just grabbed off hub and bottom is the one I had in my install. Same var, different content. Thanks for bringing it to my attention. I'm pretty surprised it hasn't been brought up before as unless someone had downloaded hexen's older version back in 2021 everyone should have been having this same issue. :eek:

1760837900144.png
 
That is odd, I've seen creators remove and release vars under the same name instead of properly updating to a version 2 of the var which is what I'm guessing happened here. So then anyone using it as a reference has no idea something is broken and the var system can't point to a specific older version being used. This also circumvents people getting the usual alerts when a resource they've downloaded has been updated. I believe that is what happened here. I'll have to update scene to use the "updated" var of the same name.

Top is one I just grabbed off hub and bottom is the one I had in my install. Same var, different content. Thanks for bringing it to my attention. I'm pretty surprised it hasn't been brought up before as unless someone had downloaded hexen's older version back in 2021 everyone should have been having this same issue. :eek:

View attachment 534428
Got it, that explains everything! Thanks a lot for checking and planning to update the scene — happy to help spot the issue.☺️
 
Damarmau updated XXXmas gift with a new update entry:

updated tree assetbundle to current hub hosted version.

Main change was updating the scene to use the current hub hosted version of the @Hexenv88 prop pack as it must have been updated without getting an updated var number and with different content inside under the same exact var name so vam thinks you have the dependency but the paths don't match and assets won't load up.

If you weren't having issues with the props you could in theory skip this update as there aren't any new animations this time.

This update will...

Read the rest of this update entry...
 

Similar threads

D
Replies
0
Views
321
Deleted member 37205
D
Back
Top Bottom