[Mylenium]

I think the best way to approach this would be a combo of MoGraph and Thinking Particles – place the cloned daisies with MoGraph on a text object, then link them to TP forces to make them “explode”. At any ratre it’s not going to be as easy as using the ExplosionFX object.

Mylenium

[Pour Myl

[Mylenium]

[Victoria Ellis] ”
However, I have just discovered that if you save the effect on the adjustment layer (a curves one in this case) as a .ACV file, and then in PS make a new adj. layer and load a preset, it works, although the colour of the PS file is slightly different to the AE file”

That’s inevitable, as you are working in different color spaces and calculations are slightly different, even if you set color profile usage to “none” in both apps.

Mylenium

[Pour Myl

[Mylenium]

Mask out the area of the text that is supposed to “steam”. Put it in a pre-comp. Enable the 3D switch and use the pre-comp as a layer or layer grid emitter. For the smoke, use custom particles. The particle shape yould be a blurred hollow circle with a low opacity. This creates more opaque areas where they overlap, but the smoke is mainly transparent and looks whispy. modulate the motion using Wind and turbulence. Make the vertical movement driven by a negative Gravity setting, not Velocity. if you particles become to fast, add Air Resistance.

Mylenium

[Pour Myl

[Mylenium]

Not sure, but usually notebooks have shared memory aand you should be able to allocate more of your RAM to the graphics. This should solve your problem, as the error only means that the video buffer is too small to cram in the entire image (for HD stuff, the default on most notebooks 64 MB is barely sufficient for a single layer).

Mylenium

[Pour Myl

[Mylenium]

No, it is not a bug nor illogical. Font properties are stored in the source text keyframes. They are simply not accessible by expressions or scripts. If they were, it would have to be something like

sourceText.fontFace

or

sourceText[fontFace,fontWeight,fontSize]

Mylenium

[Pour Myl

[Mylenium]

No, it is not a bug nor illogical. Font properties are stored in the source text keyframes. They are simply not accessible by expressions or scripts. If they were, it would have to be something like

sourceText.fontFace

or

sourceText[fontFace,fontWeight,fontSize]

Mylenium

[Pour Myl

[Mylenium]

[Chris Smith] “I know, man. But don’t yell! Geesh :)”

*lol* You really don’t know when I yell. Trust me, you wouldn’t like to see it.

[Chris Smith] “If there was ever an RTFM question on this planet, this thread was it and you showed grace and patience. I wouldn’t have.”

Me and being graceful… *giggle*

Mylenium

[Pour Myl

[Mylenium]

Yupp, DiTools is just nice and I’m sure PhyTools are also (should I ever get them to work properly) ;o).

Mylenium

[Pour Myl

[Mylenium]

[Andy Stokes] “I tried dropping an NTSC sq pix comp (720×540) into the non-square (720×486) and see that I need to manually scale to 90%. Is this the correct method?”

Dunno what’s going on, but should work without scaling. I’m no NTSC expert, though, as usually we do not do native NTSC projects, we are just converting footage on an as-needed basis.

[Andy Stokes] “29.97fps ?? I’m aware there’s something called drop-frame and non-drop frame, but have never needed to deal with it. In C4D should I set my render frame rate to 30fps or the arbitrary 29.97fps. Anything to watch out for on import ?”

I wouldn’t bother with non-drop. This is more or less a minor technicality not really relevant for 3D and compositing work. Just render out 30 fps/ 60 fps and you’ll be fine.

Mylenium

[Pour Myl

[Mylenium]

Works fine here. Dunno what could be the problem.

Mylenium

[Pour Myl