[John Hammond]

Ah right,

I don’t know, but I think it’s to do with Advanced Render module – which may or may not have shipped with your C4D depending on what package you bought.

Good luck

[John Hammond]

Hi,

I am starting out learning Xpresso.

I don’t know the answer to your question but this might help.

CSTools (https://sugarfilmproduction.com/CSTools.zip) is a free pack of presets and expresso set ups. Really useful by the way, lots of people seem to use the tools, I have used the camera rigs a lot.

Anyway, there’s a preset called CS SpringNull which is a pre made set up for the ‘bounce, decay’ behaviour you mentioned. It works with position and rotation.

You just parent your object to it and it works. The documentation that comes with the download explains everything you need to know.

Anyway, maybe by looking at the Xpresso it will give you some hints as to how to set it up yourself.

If you figure it out please post – I can set it up in AE, but like you can’t figure it out in Xpresso just yet. I’m working on a project right now, and for now CS Tools is proving real handy.

John

[John Hammond]

You need to apply a material or texture to it to stop it from just being grey.

Double click in the materials manager (at the bottom left by default, or click Window/materials).

A new material will be created. You can double click it to access all the controls, like to add a texture by loading an image file in the colour channel… for example.

To apply the material to your Sky, just drag it from the materials manager onto the Sky object in the Object manager (over on the right).

[John Hammond]

Ah ha, got it.

Use the Compositing Tag.

[John Hammond]

I see,

I have 3.5 Gig of RAM, but I most likely had photoshop, after effects and bridge open at the same as C4D, so I’ll try it again with less programs open and see how it goes.

Good to know there is no limit on image size.

Thanks
John

[John Hammond]

awesome, thanks,
John

[John Hammond]

good stuff. Thanks for the expressions idea, that solves the issue of having to travel up and down different compositions when animating a single character.

[John Hammond]

Perfect,

thanks

[John Hammond]

“This message usually comes up to me when I´m trying to preview a comp and the timeline indicator is at the last frame (and I have the preview set to from current time). ”

..ahaa that makes sense. If it happens to me again that’ll be the first thing I check.

[John Hammond]

I had the same error once, and so did my colleague, repeatedly on one project. I think I fixed it using the ‘cough, ahem’ method as mentioned above.

I don’t know what causes it.. I definitely had more than 2 frames that I was trying to RAM preview.

Purge clears your RAM preview and caches and such.

I feel like the error message you mentioned might be some kind of bug, possibly related to rendering big or complex scenes.