Search results for query: *

Unfortunately reloading isn't a triggerable action by default. Plugins could in theory implement it as a custom triggerable action, but I don't think I've ever seen that

Can you elaborate? What reload option, and what is the receiver?

This is a Timeline question, not a MocapSwitcher question, but here's the Timeline wiki: https://github.com/acidbubbles/vam-timeline/wiki

Unfortunately both animations are loaded to start from the beginning. It'd completely make sense to be able to add some start padding though, I'll make a note of implementing that at some point! For now, I suggest importing the mocaps to timeline and then editing there

Yeah you can put the plugin on both atoms, load mocaps on them independently, and they are both loaded to the overall Scene Animation that plays when you hit play

@too I'm pretty sure I know what it is now. Something is animating bone morphs, i.e. morphs containing "bone formulas" (red cog symbol in the Female Morphs tab). If those bone formulas include movement/rotation on the chest bone (or any bone above it in the DAZ G2 skeleton's hierarchy: Hip >...

Some plugin other than Naturalis might be doing something with them. But I think that's unlikely. Within VAM, it's possible to link to them: I think that's also an unlikely explanation for the issue.

Hi, good basic guide. (y) But restarting or hard resetting VAM is not necessary to get the var to load up - you can also go to Package Manager and click Rescan packages: In addition, to download only the dependencies required by that specific var, it can be more useful to find the var in the...

Download 3.0.7 / 17.var - that's a free release of the same plugin, but with various bug fixes. To understand how versioning works: for example 10.var is plugin version v3.0.0 - that means major version 3, minor version 0 under that major version, and patch version 0 under that minor version...

Old releases are available here: https://hub.virtamate.com/resources/tittymagic.4067/history You can probably use the latest version. VAM will automatically use the latest installed version of a package if the exact version required by the scene is not found. If there's some error on scene...

Seems like a collider issue. If you can send me the scene file, I can investigate further

I mean rPectoral and lPectoral. Those don't have controllers and UI's, but they exist as joints just like chest, rShoulder etc.

Hi, the morph values in Naturalis are driven by the angle of the pectoral joint. If something causes the pectoral joint to not rotate smoothly but warp back and forth like that, it would cause the morphs to also not adjust smoothly. If you suspect it's an issue with the plugin interacting other...

This is likely an issue with too many morphs being loaded in your installation. Naturalis of course adds a few so it contributes, and its morphs get loaded on demand by default, so in theory adding the plugin can be the thing that tips the program over the edge. See...

Great work. Can't wait for saving/loading to work, it can take a long time to figure out good settings. Also is a damper setting possible?

everlaster updated Naturalis (free) with a new update entry: v1.2.5 Read the rest of this update entry...

I can confirm that, plugins are loaded only if Appearance and Physical are both checked. However, I just tested it and plugins are saved if only Appearance is checked - Physical is not required to save, but it is required to load (which makes no sense)!

everlaster updated Preset Loaded Triggers with a new update entry: v1.1.0 Read the rest of this update entry...

No it's not absolutely necessary. Nothing breaks, it's just not using the optimal damper settings (pectoral/glute joint and soft physics joint dampers) for that physics rate. I could hot swap in the new dampers since damper values don't affect the calibration result - I'll put a note on looking...

@RonBurgundy That's good reporting, anchorman. So if you have 5-6 dancers but run at 60Hz physics for example, there's no issue, and if you have fewer people but run a very high physics rate, there's no issue? When it occurs, does the issue go away if the plugin is reloaded? What about when...