On mac OS
I've tried switching from Javascript to legacy and neither works.
I've tried using the automator before even rigging my own shapes. It won't work.
Essentially the walk cycle layer appears but nothing else changes.
I've followed the instructions on both videos and site documentation...nothing seems to work. Is it broken on the latest AE release?
Am I fool to download it so soon?
This forum has been permanently closed and archived; you can still access all content but can't post anymore.
Of course, you can still join us in other places!
To get support and talk about RxLaboratory and with the team, come here: https://rainboxlab.org/support/
Of course, you can still join us in other places!
To get support and talk about RxLaboratory and with the team, come here: https://rainboxlab.org/support/
Walk Cycle Automator not working AE 16.1.1 Build 4
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
That's strange, it should work properly.
Can you send me an aep as it is just before you try to apply the walk cycle?
Can you send me an aep as it is just before you try to apply the walk cycle?
-
Penrose
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
So, I think I figured it out.
I thought at first it had something to do with Legacy vs Javascript. It does not, apparently. The problem seems to be that I have to have the controllers as shape layers and best quality. That was the one thing, after a lot of tweaking, that I adjusted that would either make it or break it. Is this normal or a bug?
Here's a video of me documenting the working/not working process:
https://vimeo.com/331307527
and I've attached an AE file for you that has the rig before walk cycle. Not sure how this will work on your end depending on your controller scheme? I'm assuming it won't because I already made the rig with the draft/nulls
I thought at first it had something to do with Legacy vs Javascript. It does not, apparently. The problem seems to be that I have to have the controllers as shape layers and best quality. That was the one thing, after a lot of tweaking, that I adjusted that would either make it or break it. Is this normal or a bug?
Here's a video of me documenting the working/not working process:
https://vimeo.com/331307527
and I've attached an AE file for you that has the rig before walk cycle. Not sure how this will work on your end depending on your controller scheme? I'm assuming it won't because I already made the rig with the draft/nulls
-
Penrose
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
So, I think I've discovered another problem. After applying the walk cycle the hands controller are connected to the hand but they are not connected to the walk cycle. If you move the hand controller the hand layer will follow but it's not connected to the arm. Essentially for whatever reason all other body parts but the hands are controlled by the walk cycle.
-
Penrose
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
So, for whatever reason I had to reconnect the hand layer back the the S| HAND 2, etc
the walk cycle broke the connection
the walk cycle broke the connection
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
Hi!
Many thanks for the video and the feedback, this is most useful!
I'll have a look at this and fix it for the next update!
Many thanks for the video and the feedback, this is most useful!
I'll have a look at this and fix it for the next update!
-
Penrose
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
You're welcome! And thank you for such an excellent plugin!
-
Penrose
Re: Walk Cycle Automator not working AE 16.1.1 Build 4
Hey there -
I wanted to let you know that I rolled back to AE 16.1.0 (build 204) and low and behold, the update, NOT Javascript had broken your walk cycle.
And the hand issue is no longer a problem. So, yeah...any of your bug fixes are gonna be in the new update.
Have fun!
I too like BETA testing for Adobe!
I wanted to let you know that I rolled back to AE 16.1.0 (build 204) and low and behold, the update, NOT Javascript had broken your walk cycle.
And the hand issue is no longer a problem. So, yeah...any of your bug fixes are gonna be in the new update.
Have fun!
I too like BETA testing for Adobe!