North Pole - Patreon Version
Added 2022-12-20 11:12:50 +0000 UTCMerry Christmas and happy holidays everyone!
Here is a link to my latest scene.
Sharing a little bit of Christmas joy :)
This one has some more pole dancing with lots of scenes & poses to get you into the Christmas spirit.
I just wanted to thank everyone for their support this year. Your contributions have kept me going and allowed me to keep doing what I love.
In the new year, I'm planning on creating a new more refined theme template. I want to focus on a bit more quality over quantity. I think I'll shortlist it to 9 scenes/positions to super polish. (Let me know if you have any requests). The main reason is that I want to try to streamline aspects of the scene creation so I can focus more on the stories and looks.
I'll also probably invest in another base station to see if I can refine the mocap even more.
Thanks again for your support, looking forward to an exciting year ahead!
...who know's maybe we'll be using VAM 2 by this time next year!
Comments
Hi HippyHigh, hmm, not sure. I think mega zips it for the download, so maybe it's an issue there. I'll do a test today.
XRWizard
2023-01-02 23:13:13 +0000 UTCwhy does everything i download say its corrupted
HippyHigh
2023-01-02 18:25:55 +0000 UTC1) Not talking about UIButtons pointing to specific morphs - I'm talking about Buttons that trigger a LoadPreset action for morph-PRESETS (Or Appearance-presets, or Clothing-Presets - whatever tickles your fancy) 2) Ummmmh ... Ok, I've built you a demo-scene (check your Discord), but the TL;DR is: 1) Create a bunch of presets (Appearance-preset, Morphs-Preset, Clothing ...) with generic names (Custom01.vap, Custom02.vap, ...) in a folder on your local install. Doesn't really matter what appearances - they're meant to be overwritten (Unless you want to give us a specific alternative appearance like "Slim Santa" - in that case, give it a non-generic name & include the preset into the .var during packaging) 2) Create UIButtons (CustomLook01, CustomLook02, etc) that trigger a "LoadPresetWithName" action (atom: PersonUID, Receiver: AppearancePresets, Value: LoadPresetWithName) that points to the paths of those presets ------------ Note: - That's the text-trigger version where you have to enter the filepath in a textfield, NOT "LoadPresetWithPath" (the one where you click on the Button & then the filemanager opens). - The filepaths are relative to Custom/Atom/Person/Appearance for app-presets. ------------ 3) Save scene. 4) Copy the preset-folder somewhere out of your install & create a .zip archive "Presets.zip" with the appropriate folderstructure (eg Custom/Atom/Person/Appearance/XRWizard_Presets/...). Again: Don't worry about morphs or skins or whatever: Those presets are dummies, they're meant to be overwritten. The only thing that matters is that a bunch of file exists with the correct paths. 5) Package the .var - VaM won't care about the resources (morphs, skins etc) the presets need. For VaM, the text-trigger is just a string that's going to be sent to the filemanager once the button is pushed. VaM doesn't care whether the trigger points to something real or not - it's the user's job to take care of that. And we will. Later ... 6) Create download link for the .var AND the "presets.zip" We (your subscribers) then download the .var into our AddonPackages folder & unzip the presets.zip into our Vam-Root, so the "broken" triggers/UIButtons are "whole" again. Now the UIButtons in scene-json file in the .var will point to "Custom/Atom/Person/Appearance/XRWizard_Presets/..." (local resource on OUR install) rather than "SELF:/Custom/Atom/Person/Appearance/XRWizard_Presets/... (resource in your .var). And that means we can overwrite the presets with our own custom (local) presets AND load those via Button-Push when we run the scene from the .var - without modifying the .var itself, or saving a modified version of the scene or whatever. P.S.: If it's just one (or two, or three) morph, you could also create a UIButton that directly sets a value for individual morphs (Person > Geometry > morph: morphname), but in that case, it's probably better to package that morph into the .var (ie not "external"). Much to complicated otherwise.
CaseEP
2022-12-21 01:48:38 +0000 UTCHi Case, Thanks for the comments Ok, I'll add a button to zero the morph (skinny santa) Re Morphs How do you reference external morphs without packing them? Any details on how to do this?
XRWizard
2022-12-20 23:28:54 +0000 UTCMod Request: Option/Button to make Santa slimmer. I generally don't care much about the male appearance - but since I play in POV-VR, I prefer being able to see my Avatar's dongle. P.S.: Suggest adding alternative morph/appearance-preset(s) as a separate .zip with ingame UIButton(s) pointing to "Custom/Atom/Person/Morphs/XRW_Custom_Male_01(-10)" (and the same for female). That technique has the additional benefit of allowing the user to modify appearance/morph "semi-permanently" without having to save the whole scene locally - we just overwrite your presets, rather than the scene. P.P.S.: This doesn't mean you have to actually create 10 Alt-looks - they can be 10 "dummy" appearance/morph/whatever-presets. The important thing is having the UIButtons & having them point to an existing local file. P.P.S.: The idea is SlamT's, not mine. And TGC uses the same setup for clothing-presets.
CaseEP
2022-12-20 14:29:16 +0000 UTCYay! New XRW scene! P.S.: Should I be worried that I read "Messy Christmas" initially?
CaseEP
2022-12-20 14:19:07 +0000 UTC"I think I'll shortlist it to 9 scenes/positions to super polish. (Let me know if you have any requests)." "We need Cowgirl. LOTS of Cowgirl ..."
CaseEP
2022-12-20 14:17:27 +0000 UTC
