far canal!!! yep -- reproducible here. Brilliant detective work!

yeah! impressive. well done. I love the storyline idea. Great logline potential in that closing narrative - "Salvation is at the end of the world!"

Tiny observation -- maybe rebalance the voice / music from about 1:00 onwards (where the music crescendos).

slowtiger wrote: ↑Thu May 22, 2025 9:50 am You can keep any bone invisible by making it a shy bone (and reverse that, of course). This is useful f you have a rig with many small bones cluttering your view.

I think that just hides the bone, not the parenting arrows? (same as hiding coloured bones).

if I understand you correctly - you have a SB action that can turn off the visibility of the target layer (i.e. the layer of which hand r2 is a reference copy).

That's most probably going to cause the reference copy to follow the target's visibility.

Above the hand r2 layer is a group (with a broken reference icon). It's not clear from the image if that is a switch layer, but if it is, then it's likely that hand r2 is not the active child. If that isn't it then: * The timeline shows a keyframe in layer visibility - check that is not set to "...

I don't think this will be possible without a change to some core Moho functionality. the workspace pan/zoom/orbit tools all use functions built into a MohoView object (e.g. MohoView:PanMoved(where) ) and these seem to take as their input a pixel location on screen (i.e. where the mouse is). None ha...

In the video, there's a tiny and distorted version of the arm to the (screen) left of the character as you point out around the 0:17 mark. This is likely caused by a combination of two issues. The first is that the reference copy is corrupt - it includes unnecessary duplicates of child layers (as no...

without seeing the actual file, my guess is that the actions that use both or either of the target and reference are the source of the issue. I thought I put a link in the post. You can't click on the link? the link in the OP is to an mp4 video not to the moho file. Sharing the .moho is the same pr...

without seeing the actual file, my guess is that the actions that use both or either of the target and reference are the source of the issue.

turn off "full speed start" in the particles tab of the particle layer settings

actions Turn Torso and USR / USR 2 both try to manipulate the same points -- Moho can't resolve the conflicting motion / curvature commands.

That's a reasonable workaround - but two abutting shapes shouldn't (IMO) create that sort of artefact. Issue reported.

Nice sequence. I like it. Well done. The EULA is here: https://manual.lostmarble.com/app/page/1zRdEFjHJV3vq1yZr7eOz8rDZo-AHLOE1KcKuqXk_At8?p=1UxA8Gi5DttJku9AmFlSpO0gJw4U9flX3 . I can't find anything in it that says you have to credit Lost Marble (or, indeed, the creators of the assets that are inclu...

select the layer you want to move.
put the playhead where you want it to start - move it or type the frame number in the frame box.
Animation > Set Layer Start Time

Well, we indeed have some kind of spatial interpolation control by using bezier type of keyframes for point translation, I'm not saying it'd be practical for solving complex situations (and I doubt a scripting solution would be feasible?) ... Wes (and I) have done various experiments with bezier ke...