Recent content by faaipdeoiad

Love the update! The spray dynamics overall are a big improvement, but I'm having trouble getting the same sort of sticky/drippy feel out it that I used to. Even with the bounce at 0 and dampen at 1, it seems to flow much more freely. Is there a trick to it that I just haven't discovered yet...

Not a direct answer to your question, but if you're gearing up to work on this again, my wish list would be: - A trigger that fires on start and stop (especially stop). Sounds like you're already working on this for individual bursts, but it would be great for timeline animation syncing to get...

Just in case it's helpful: I took a look at Stopper's CUAClothing plugin and fixed the naming collision issue in a local copy of SkinVertexLink: // ... public class SkinVertexLink : MVRScript { // ... // TODO: this could probably use some cleanup; _dazMesh, _dazDynamic, and //...

This is incredible, thank you! This might just be me, but in the demo scene, if you uncheck Global Sky is sRGB in the SkyMagic settings for both CUAs and then turn the GI Master Intensity up to ~0.25, I think the lighting looks a little more natural on the VaM-world stuff. (I also turned the GI...

Fucking legend. Any way I could convince you to add a feature to bake the atom's root scale into the combined morphs? (So that a new atom with the combined morphs and scale=1 is the same size as the original atom with scale<1)

When I start the scene, Timeline throws a few errors: !> Timeline: Atom 'P Evelyn' does not have a param 'geometry/morph: boobcup' !> Timeline: The storable float 'geometry boobcup' has been removed. Remove it from Timeline to silence this error. !> Timeline: Atom 'P Evelyn' does not have a...

This is incredible, thank you! I am having an issue though. It seems to get confused when there are multiple clothing items with this plugin added as a Stopper clothing plugin. I'm trying to use this to manage three piercings (from Qdaro's pack), but when I add the third plugin instance, the...

Ah, yeah, that probably explains it, I was testing with the male and very short bursts. There is the built-in attack/decay feature to adjust the envelope (at least for male), but you're probably out of luck if you're wanting something more fine-grained than that

Hmm, it worked for me just now in a test. I started it at 1 and ramped up to 3 over 10 seconds (just to make the change really obvious). A few things to check... - "At Low Load, Reduce Velocity To..." - If this is <1, velocity will ramp down over time - "Boost Velocity when Aiming Upwards" -...

It's a little bit of a hassle compared to just animating some float params or whatever, but what I usually do when I want something like this is make a preset for the initial state, clone it, and adjust whatever parameters I want for the final state. Then in a trigger, you can execute this...

The drippy/runny particles are the "spray." You can adjust how visible they are with the "Start/End Material Mix" sliders on the Spray 1 tab (1 is more transparent, 0 is more opaque). You can also adjust their physics properties on the Spray 2 tab if they're just bouncing too much or moving too...

Actually, just looking at the JSON I can tell they're using the older (pre-v9) format, which might be where your issues are coming from. I would try starting over from one of the default presets or one of the ones I uploaded above, it's usually easier than trying to convert a preset from before...

Sorry, I completely forgot about this! A, B and C are variations of whatever I used in the screenshots above. Probably not exactly the same, but should be pretty similar. The other two are what I use as a base most of the time. I usually end up adjusting the material colors, velocity and load...

I don't know if it'll help with the "huge polygons" issue, but I'll upload some of my presets in a bit. But the short answer is "lots of fiddling."

Unrelated: I'm testing a new scene idea that uses a custom Unity environment with lots of baked lights in the background and a few mixed lights in the foreground. It's working really well, because the runtime shadows blend right in with the scene bake. But currently SF is ignoring any lights...