- Joined
- Jun 1, 2020
- Messages
- 2,846
- Solutions
- 99
- Reactions
Ella?
She's available in Stasis Lab, as an appearance preset, her and her clone (which is a variation with a different skin).
Plugins + Scripts VAMStory
- Thread starter hazmhox
- Start date
Ella?
She's available in Stasis Lab, as an appearance preset, her and her clone (which is a variation with a different skin).
- Joined
- Nov 8, 2024
- Messages
- 150
- Reactions
Hi Hazmhox,
Will you consider compatibility between new and old versions?
I've setup several of my UI framework with Vamstory Custom Action, but every time when there's update, I have to totally rebuild them with the latest version if I want to use the latest VAMSTORY.
I'm frustrated.
Will you consider compatibility between new and old versions?
I've setup several of my UI framework with Vamstory Custom Action, but every time when there's update, I have to totally rebuild them with the latest version if I want to use the latest VAMSTORY.
I'm frustrated.
- Joined
- Jun 1, 2020
- Messages
- 2,846
- Solutions
- 99
- Reactions
There is zero breaking update since Custom exists.. and overall I ensure I'm always keeping legacy compatibility. You can test the demo provided in HZMDemos, it's a legacy demo made at the first release and it works : )
How are you updating VAMS?
Thanks so so so muchElla?
She's available in Stasis Lab, as an appearance preset, her and her clone (which is a variation with a different skin).
- Joined
- Nov 8, 2024
- Messages
- 150
- Reactions
Oh sorry, I think my description made confusion. I didn't mean the compatibility between VaM versions and VAMSTORY versions, but I mean the versions VAMSTORY itself.
For example, I've built a UI with Custom Action in VAMSTORY v40 and saved it as am Empty Atom preset. And then later, when I am using VAMSTORY v41 in my another scene, there will be compatibility problem when I try to load the Empty Atom preset with Custom Action that is in VAMSTORY v40.
- Joined
- Jun 1, 2020
- Messages
- 2,846
- Solutions
- 99
- Reactions
No no, I litterally understood what you meant. And yes, when I'm talking about legacy content I'm talking about the VAMS version itself.
This was kind of obvious as VAM does not get updated and only VAMS does
You still did not answer my question, how do you update VAMS?
What is a compatibility issue? You give me no information, error message, screenshot of problem etc...
(I'm pretty sure I know what your problem is but I can't be sure if you don't give me a bit of details)
- Joined
- Nov 8, 2024
- Messages
- 150
- Reactions
My way of updating VAMS is only via in-game Hub, and I won't delete any legacy version after I download the latest one.No no, I litterally understood what you meant. And yes, when I'm talking about legacy content I'm talking about the VAMS version itself.
This was kind of obvious as VAM does not get updated and only VAMS does
You still did not answer my question, how do you update VAMS?
What is a compatibility issue? You give me no information, error message, screenshot of problem etc...
(I'm pretty sure I know what your problem is but I can't be sure if you don't give me a bit of details)
I will show you what my issue is in below example:
First, I created an VAMStory in VAMS v43
After then, it fails to load a preset which is a VAMSTORY Action in VAMS v39, and the error log is as below:
So I have to build a new UI by using VAMS Action which must be in VAMS v43.
Likewise, if I loaded this preset which is a VAMST Action in VAMS v39 first, after then I can't create the VAMSTORY in VAMS v43, error Log as below.
I could only create the VAMSTORY in the same version (v39) as same as the first loaded VAMS Action.
So, the compatibility problem I mentioned is about VAMS components are not compatible if they're in different versions of VAMS.