Search results for query: *

From my humble non-clothing creator view, here is one observation about the reset pose in VAM: When you do the "reset pose", the character does go into the default t-pose for a fraction of a second, but then the pose gets altered when the physics kick in on the character control nodes. So, to...

Search/filter for a custom morph called "MCH". It is included in the VAR. Other then that, I just used buildin morphs to pose the genitals.

zoidberg updated MaleChastity2 with a new update entry: added a cage-cap to the existing set Read the rest of this update entry...

(CUAs in sceenshot were colourized using the Blazedust colorscale plugin).

zoidberg submitted a new resource: MaleChastity2 - you can't go flatter then that Read more about this resource...

When you load different clothes (the change of character model does not matter), it will load the clothes at the default shader "Render Qeue" setting, which is 2400. But it needs to be 2424 for the trick to work, so you need to change it. To do so, select the character root, go to the clothing...

Ah, yes the script is just for VAM exported OBJs, the G2 OBJs from DAZ are a bit messy (see this message and the following from Sally Whitemane https://hub.virtamate.com/threads/blender-templates-to-convert-objs-exported-from-vam-into-objs-that-use-udim.27583/post-137583)

Just grabed a portable version of Blender 4.0.2 and tried it, it worked for me. Could not find any model that I exported from VAM to set up my script/macro ,did export all models available in the "skin-selection" of VAM back then, but no of the models is named Genesis2Female. Is it a custom skin...

You need to put the textures into the same folder and name them all the same but with a diffrerent (pre-)suffix: filename.udim_tile_number.png. E.g. Base_female.1001.png, Base_female.1002.png, ... etc. , with the texture content fitting the UV layout, so the torso texure needs to be *.1001.png...

Sorry, this was just a still image/pose scene, never animated. And it seems I either deleted it or never saved it in the first place (can't find it).

Hi there. Here's a somewhat newer version of the scene. Enjoy ! https://mega.nz/folder/5oRCXQKJ#2vePEC6LwTAWLGWdimlzqQ

Did you also set the parent of the chastity CUA to the Person atom ?

My non-coder/scripter take on this problem is: it is set to "none" after reload because the node it should be connected to has not been spawned yet at that time. Maybe reworking the plugin into a scene or session plugin could fix that problem (if those plugin types actually allways load first)...

I tried some dog (the golden retriever from the ZRSX animals var), and with the default settings it explodes when loading the XPS and then the CUA controllers. But leaving the "add auto collider" and "convex colliders" off in the XPS loader and loading the CUAcontrollers on the XPS/armature...

Not sure if it helps, but there is a XPS/XNA import/export for Blender available at https://github.com/johnzero7/XNALaraMesh/releases . Note that it does not work with Blender v4.x, you need to have the 3.6 LTS (I grabbed the portable version...

Did you try to enable "Freeze Motion/Sound" before loading the scene, and disabling it again after the scene loaded ? Maybe some physics need their time to shake out. Think I had similar problems with just animating penetration with molmark's wobbly cocks CUA, did delay the timeline animation...

hmm. just tried with the recent version of timeline and cuacontrollers, and it works just fine. Did use assetname(Clone)/Armature to spawn in the controllers, and loaded the timeline instance on CustomUnityAsset#Controllers/control/Plugins. I guess this makes sure that timeline is is...

I have no experience with the eosin vr render plugin, but I think my CUA works in VR in general. So, my guess would be that the problem might be the reflection probe versions of the assets included in the assetbundle. maybe try to make sure that you're only the version that uses the boring grey...

Just tried the UDIM conversion UVs, and they look fine: BUT, when loading the exported OBJ back into DAZ in morphloader pro .... So, it looks like you can't have both, UDIMs and compatibility with DAZ morphs ... :(