Search results for query: *

Yes, the update has been made a while ago, a great improvement! I don't know if that has improved the packaging quality of paid content, but it certainly allows users to make better choices

ZRSX updated Character Transparency with a new update entry: Meta.json fix Read the rest of this update entry...

Changelog New in 1.3: - Change in the credits of the meta.json file, where a character sequence unexpectedly caused dependency errors with VAR manager(s?) Some more details Yeah, nothing has changed. Sorry for those expecting exciting new features or complex bug fixes.

Following what atani said, I'll go a step further: try reset the custom look(s) you're using to default VAM looks. Because custom looks could often be a dependency cascade (morphs, textures, hairs, clothing... and even unnecessary plugins and assets if they've been been packaged with a demo...

There is an option within XPSLoader plugin to flip all textures. You should try to toggle that.

Yes, those assets all have collision.

Yep, those devices were made before discovering this bug. I'd have to redo them with "Parent atom" (and Timeline for the saving issue), but I have no time for this at the moment... Maybe one day! ;)

Way easier than figuring out how this plugin works! Here are some guides: https://hub.virtamate.com/resources/how-to-create-a-var-file.5565/ or if you prefer a video: Video guide by JustLooking ForNothin And then please read this to make clean packages...

Nice idea! The plugin I built upon had Render Queue sliders, but I removed them for the sake of simplicity (ease of use and lighter UI). Having a toggle would avoid those issues and bring back the control over the render queues. The only issue remaining is the number of triggers it adds...

If you ever decide to go for this, you've got my permission. Even though you don't really it, as it's not really "my" plugin but rather a collaborative work already.

Thanks for looking into this! I'll try it out as soon as I have some time for VAM (rare commodity those days) I don't know the reason of many things in this code, I built up on an existing plugin, very useful but quite wonky. I guess it was quickly made and never packaged; that can explain why...

Point 1 is a bug, and it's been already reported here: https://hub.virtamate.com/threads/1-20-77-9-packagemanager-latest-referenceversion.12141/ As for the 2nd point, it will be indeed easier to have a "Download dependencies" button quickly and easily accessible. But I fear that it would have...

This issue was already in the initial plugin; I have no idea of how to fix it or if it's even fixable. So the answer is no, unless somebody can point towards a possible solution.

Just passing by to say that you can do it without the CUA. That'll change your steps 2 & 6. Use the "WindowCamera" atom instead and turn the Camera on. Big plus with this: you can use the "Show Camera View in HUD", so you don't even need to move around in your scene to see the camera screen...

Yes indeed: when semi-transparent, the skin will hide the back of the clothing. There is something called the "render queue". Simply put, this is a value that tells in which order each material should be displayed. This is available in the material tabs of atoms with editable materials. All...

ZRSX submitted a new resource: Animal dildos - Dildos with non-human shapes Read more about this resource...

Yes, this is normal. The "Genitals" area for males includes the pubic region. This plugin cannot remove a part of designated areas (this is inherited from VAM, which itself inherits it from DAZ G2F model). If you want full transparency on a custom area, you should take a look at this plugin...

Hi! If you're up for some reading, I've made a guide that should cover your need: https://hub.virtamate.com/resources/how-to-package-like-a-pro-a-guide-on-proper-var-building.8212/

ZRSX updated Character Transparency with a new update entry: Name fix Read the rest of this update entry...