RunFaps
TGC69
TGC69 patreon

Clothing Presets Idea

🕑 Added 2023-06-26 00:12:54 +0000 UTC

Comments

TGC

Hey Case! Once again thanks a lot for such an elaborated response <3 I did not come to check out your suggestion yet, since the time until end of month was running out, so I stayed with my workaround for now. Yes from what I understand you understood my problem :D Basically yes all the clothes I used in presets have to be loaded at the beginning, otherwise the triggers for undressing and stuff become empty. Or the clothes can be loaded after loading, but then all the triggers have to be refreshed/triggered with those clothes on. Then they go from empty to "full" again. This is the way I went for to make it automated. And yepp I am using the "toggle" option you stated in 2) for that method. Also I did not mention it, but this was exactly how "onion" method worked aswell :D Its actually funny how similar our brains work here and there lol The solutions you suggested under 3) sound very interesting indeed. I have not checked those plugins yet and will definitely do so in the coming days! Would be super nice if I can manage to make the scene "lighter" aswell this way! Much thanks again Case!

CaseEP

"If there is a better way you know of, how to make the clothing triggers persistent after saving and reloading, please tell, cause my solution seems a little bit clunky." It DOES seem clunky ... but I currently have no better idea? Actually ... I'm not sure I fully understand the problem? Soooh ... you want to have different selectable clothing presets, but also you want the undress animations during the poledance to work? And somehow you need the clothes to be actively loaded into the scene, bcs otherwise, some of the triggers in some LogicBricks break during saving? Off-the-cuff ideas: 1) There's two methods for (merge-)loading presets: MergeLoadPresetWithPath and MergeLoadPresetWithName. The latter stores the filepath + name as a STRING. Might be more robust than the other option. (MacGruber once told me that strings are the most reliable method of passing information between triggers/plugins - basically the reason he based his selectchoice and statemachine bricks on that method.) 2) IIRC, there's also two (three?) different ways for toggling individual clothes - you can load the clothing item (by path or name), but you can also "activate" it. Afaics, that's the same as loading a clothing item and then manually unchecking it in the clothing tab. Note that the clothing item needs to be loaded once before toggling (and the user needs to have Ram-optimization for presets disabled) Maybe an idea for your "onion" strategy? 3) IIRC, there might be some plugin-based solutions worth looking at - atani has what they call "clothing quickloads" (just check atani's scene templates on the Hub). 3ii) Also, there's hazmhox' VamStory plugin - the main advantage over LogicBricks is that it unifies a lot (not all!) of the LogicBricks functionality into one single plugin loaded onto one single atom - so there's a lot less of the "weak spots" (that can break during scene loads) which you get if you have your scene-control logic distributed over 100 plugins on 30 atoms. Basically "One SUPERBRICK instead of 50 smaller bricks = less brittleness" Not to mention that it simplifes UI menu-creation A LOT - IMO, you might want to consider using VamStory for that reason alone.


More Creators