1. How to Trigger Buttons to Check/Adjust other Buttons/Sliders
On the Get Her Pregnant scene I have a button to choose Get Her Pregnant and originally wanted it to include a combination of options selected like Pregnant, Milk Squirting, etc. in that category. But the challenge I have is I don't know how to make it where when you click that button, it then will check the boxes on the menu or make the adjustments to the menu. What ends up happening is it will turn those on but leave them unchecked so it can get confusing and you have to toggle it on off to keep up with your settings. So I just left it on a generic Pregnancy Morph and let the user choose those additional options but I'd rather have it where it choose everything at once.
3. Dependency Issues/Clear Cache Option
When I created White Apartment Harem I tried out a lot of different models, outfits and music to see what I was planning to go with. When I went to package the VAR to upload it to the hub it listed a lot of dependencies for things I am not using in the scene. I tested out a futa option and thought about adding it to the scene but haven't, yet it shows a lot of futa related dependencies and the only thing I can think of is it is coming from rotating them through buttons or in the scene to try it out. If you look at the scene it says I am using around 200 dependencies but there are things that I am not using. After spending a few days trying to sort out some things and searching the meta.json and using notepad plus with json viewer and really trying to figure out what is going on, I see that there are some VAMStory Actions that seem to stay around after them are removed from the buttons. Even songs removed from a scene still show up in the meta.json after test packaging it and reviewing it before upload to the hub. If it's a user related error it may be related to switching modes between button and button toggle, or possibly a button that had the data on it but was converted to a spacer instead and maybe switching it didn't clear it out. This is probably the biggest challenge I have right now with using the plugin as it happened on other scenes as well initially. So I guess I am just trying to understand is it a user error, I dig through and don't find it and even removed a lot of spacers when I switched everything to sections without spacers but the dependencies are still there. When I get around to it I want to make a lite version with base models and see if I can get rid of them all or track down if it's really that high or if it's somehow coming from the buttons not clearing or updating the meta.json data.
1. The first challenge can actually be accomplished using the existing VAMStory feature. Moreover, if your triggers are well-planned, you can even use VAMStory as a central controller to achieve complex front-end interactions and back-end processing, just like a telephone switchboard.
You only need to create three triggers to achieve this, and it doesn't necessarily have to be executed manually through a button. It can be any form of trigger, such as Timeline. For example, in your UI, there is a toggle box that turns on the light when checked and turns it off when unchecked. However, you also have a Timeline animation that might turn off the light during the animation. In this case, you would want the corresponding toggle box in the UI to be unchecked as well. To achieve this, you only need to set the light on/off triggers within the toggle box's own triggers. Then, when you want to switch the light, you can use the following three trigger items to execute it:
Trigger 1: Specify the target object to be changed. In this example, it is the second checkbox in the second row, i.e., B1.
Trigger 2: Specify the action to be executed, which in this case refers to the checked/unchecked state of B1.
Trigger 3: Reset the specified object based on the execution result. This step is essential; otherwise, the previous two steps will not be fully executed.
This method applies to all UI types provided by VAMStory except for the button. I have created a demo for you; perhaps interacting with the demo will give you a more intuitive idea.
6.6 KB file on MEGA
mega.nz
This demo is a bit more complex, but the principle is the same. When you press B, B1 will be checked while A1 and C1 will be unchecked. The same applies to A and C. It's like a simple logic gate or gateway.
3. This issue is unrelated to VAMStory itself; it is about cleaning, finalizing the scene, and correctly packaging it. However, I have a suggestion for you: you can try using this checker tool made by @AshAuryn.
VAR Inspector - Other -
VAR INSPECTOR CC-BY-NC-ND What is it: Var Inspector is a desktop application written in Python which will scan the save files and presets in your var and tell you where the dependencies are located How does it work: Var Inspector creates a...
hub.virtamate.com
You can give it a try, and if you encounter any issues, you can continue the discussion in that tool's dedicated thread. I'm happy to provide any assistance I can.
Hope that helps.
Last edited: