Every time the artwork is regenerated at 200% I get an error saying can't rename file. See the attached error log.

Is there any way to sanitize this file without starting over?

at this point I think it's fixed - what I did was

1) I pushed all behaviors from the puppets to default
2) I exported the puppets
3) I created a new project and imported all the puppets
4) imported the offending project
5) swapped the offending scene's puppets for the newly imported puppets
6) deleted the old puppets and did a save-as.
7) on opening up the newly saved-as project no more error.

I did build the project in the beta version of Ch, so perhaps something got corrupted. I occurred at the time when I was bumping up the ai render res. I bumped it to 400% and realized that was WAY too laggy, and so I bumped it back down to 200%. However perhaps I was not patient enough or something. I ended up with files that couldn't be "renamed" how shown in the log.

Anyway... this feels like a bug. But I can't exactly repeat it. If you guys want the file, I'm happy to share by uploading.

There are so many "Bad" takes, and when I delete a take the TAKE file is not removed. I can't delete the takes, because there is no east way I can find to determine if they are used or not.

For many reasons, it would be great to be able to export a Scene with all, but only, the assets that are required for that scene. PERFECT for archival purposes. Much like a puppet file, but a scene. Same goes for a project file! I don't want a copy of all the junk files that are no longer used. I want ONLY used/included files.

I'm new to Adobe and just started to use Character Animator. And I love it. But I can't find a way you can have a live backgroud in Character Animator. So I gues you can't do it. By live backgroud I mean you could set the desktop as background so you can have a caracter that can explain whats on the screen. I have two screens and want to make a video for my students where the puppets shows and explain what I'm showing on the other screen. If you could import the desktop live, or if you could have an another webcam as background you could use OBS or Menycam with virutal cam. With an extra webcam as live background you could also point to a geen screen and record the puppet with a real person at the same time. Without making two records that you mix togheter in Premier. It's easyer to record it live at the same time, than mix two videos afterwords. It's hard to get the puppet to point on the right place.

Over time, it appears that fps drops lower and lower with use of replays. I have puppets with several triggered replays. With each triggered replay the fps gets lower and lower. This happens regardless of whether or not I am streaming using OBS or whether I am just working in Character Animator alone. Eventually the fps gets down to close to single digits and the only way to remedy the situation is to exit and restart Character Animator. I have monitored CPU and RAM usage and those numbers are no where close to being suspected of being the cause. A few searches in the forums suggested a few others have discovered this issue as well, but as of yet have not found the cause or a solution.

Am I not familiar enough with Character Animator or what, but here's my problem:

I have a little experience in After Effects before. There is a thing called "parenting"

It means I can parent layer "b" to another layer "a", and hence everytime layer a is moved layer b will follow that layer a movement. However I cannot find such option in Character Animator. A layer can only parent to its own group, and cannot parent to another layer outside its group. For example say a hair in the back of the head group and body group.

It looks like this:

• Character/Puppet

-- Head group

-- Body group

-- Hair

Won't it be very helpful if we can parent the hair into the head group instead of the entire character?

That way the hair will move everytime the head moves?

And this can apply to arms and torso. I have puppets that consist of two set of arm groups. Namely the back and front arm group. The front arm group is used when the hands of the character needs to be in front of the face.

It looks like this:

• Character/Puppet

-- Front arm group

-- Head group

-- Back arm group

-- Body group

And this are only a scarce of cases. Many things can be achieved if we just have this option.

I have thought about the magnet option, but the problem with magnet is the layer needs to be independent to work effectively. Many times I can't make a layer independent for reasons.

Thanks for reading!
Hopefully you can understand what I am trying to deliver...

If I have a puppet rigged like OKSamurai's Yoga girl, and I want some draggers to be "hold in place" like the arms and feet, but I want the torso dragger to be "return to rest" then I would need a local Dragger Behavior for the independent leg layer.

But when I do that, if Ground detection is enabled, then the heel/dragger moves fine, but the toe remains pinned to the ground.

This works fine when there's only one global dragger behavior, but no matter where I put a second one, the toe information is lost.

Nesting local dragger behaviors in the arm layers works fine though, it's just the ground detection info that isn't passed through the second dragger behavior.

Is this fixable?

Thanks!