I did this test animation to see how well my time-warping scripts worked on the SLS rig I bloged about in the previous post.
So far, I’m rather satisfied. Now onto the actual animation…
By the way, play the animation at full-screen, it’s in 720p! ZOMG! SO MANY PIXELZ!
I’m working on one of my personal projects and wanted to share with you a demo of a car rig I did for the project.
Oh, yeah, by the way, it’s gonna be a very original and one of a kind car spots.
The rig sports a few basic features:
- Automatic wheel rotation system based on traveled distance on individual wheels level
- Manual suspension system
- Manual rotation of the front wheels, incl. automatic steering wheel secondary rotation
- Manual rear wheel spinning system for burn-out animations and sliding
- Secondary system for car sliding at the front and at the rear for drifting types of animation
- Manual body reaction to acceleration
Nothing too fancy, but it’ll get the job done and didn’t take too long to rig. Here’s the preview:
As you might know there has been a significant change in the latest Shotgun API that’s somehow transparent to the CPython users, but presents a rather significant roadblock for IronPython users (including our duberPython bridge, that is based on the IronPython engine).
First, let’s discuss what’s changed in the API so dramatically that it breaks IronPython compatibility. It’s the introduction of a JSON formatting that requires a few specific CPython libraries that are not available in IronPython. The effect it has on CPython users is a faster data transfer to/from Shotgun, but other than that, the API looks to be unchanged from a user point of view. You still keep calling the same methods and you’re getting back the same objects. From IronPython point of view, you’ll hit a roadblock as there are a few modifications you’ll have to make to the Shotgun modules in order to make them run in IPy without issues.