[Adam Trachtenberg]

No, I can’t think of any other way to do it, short of cropping the frames that need to be smaller.

But NET is actually quite simple to set up and you don’t even have to use it across multiple machines if you don’t want to. The host machine can also be a client machine.

[Adam Trachtenberg]

Pretty easy, fortunately. Just check the “tangential” box in the emitter’s properties. 🙂

[Adam Trachtenberg]

Well … wow … there is an incredible lot of new stuff since v8, it’s hard to know where to start.

Modeling:

* ngon support, meaning support for polygons with more than four sides. Now you can knife through quads without creating all manner of unintended triangles;

* improved knife tool: supports loop cutting, path cutting, etc.

* soft selections;

* brush tool;

* multi-object editing;

* etc.!

Timeline/Animation:

* all animatable parameters can be keyframed by Ctrl-clicking on the small circle next to the parameter name in the Attributes Manager;

* timeline completely rewrittin in v10 and improved in v11,
Suggest you read the entire manual section on this;

* new joint system and constraints;

* completely new morph system;

* morph deformer;

* completely new NLA system;

* cache tag;

Interface:

* collapsible managers;

* layer manager;

* full-screen mode;

* completely rewritten asset browser;

* scripting capability and script manager;

* etc.

Materials:

* BodyPaint 3D now part of base package;

* subpolygon displacement;

* ambient occlusion;

* texture baking;

Rendering:

* general speedup;

* completely new GI engine — faster, better quality;

* save render settings to presets;

And I’m sure a whole lot more I’m forgetting.

Existing Mocca tutorials can still be used with the old bone system, but I would suggest switching to the new joint system. The old tuts will only be helpful in terms of broad concepts. Given all the new stuff it might be a good idea to subscribe to Cineversity….

[Adam Trachtenberg]

I would save the file under three names with the appropriate render settings and use NET render to batch them.

[Adam Trachtenberg]

Hi Brian,

I haven’t tried it yet, but it looks to me like Remotion’s PhyFluids plugins would be ideal. https://www.remotion4d.net/index_main_2.0.html

There’s a 14 day demo so you can check it out for yourself.

[Adam Trachtenberg]

The flickering is caused by too-low samples in the AO, but you have to really jack them up to avoid flickering altogether. I would advise baking the AO if it isn’t affected by the animation. You might also be able to render out a separate AO pass and apply a little blur in post.

[Adam Trachtenberg]

It’s possible to do by animating the Scale spline along with End Growth, but kind of tricky if you need the exact same end shape all the way through.

If you have MoGraph you can use the spline wrap. Key is to select End Mode>Clamp in the spline wrap properties. That won’t give you a 100% same taper the whole way either, but it’s closer to what you want than a regular sweep.

[Adam Trachtenberg]

Just use File>Open or Merge.

Cinema’s native .obj importer doesn’t keep track of materials, but there’s a free plugin call Riptide that can do that and has many more i/o options.

[Adam Trachtenberg]

I would start by making the booleans editable. They can be a little finicky at times.

[Adam Trachtenberg]

Any changes you make will automatically be saved in a file called “shortcuttable.res” which resides in your Cinema prefs directory. If you want to restore defaults you just have to move, delete, or rename that file.