Adam Trachtenberg
Forum Replies Created
-
The Measure and Construction tool is pretty limited, but there’s a sort of workaround for using it for things like Booleans. What you can do is put the Boolean inside a null with a correction deformer, and then measure from your other object to the correction deformer. This works because the deformer creates actual points/edges/polygons for your Booleans and other parametric objects.
What won’t work is moving the Boolean a fixed distance or angle using the M&C tool’s numerical input, since this will only move the deformer and not the Boolean.
-
The RAM preview concept doesn’t apply as in AE because the frames have to be rendered before they can be loaded into RAM and played back into their full glory. But there are a number of things you can do to get a quicker preview:
1. Render at lower resolution;
2. OpenGL preview (in render settings, set engine to OGL);
3. Turn off cpu-intensive options like anti-aliasing, GI, area shadows, blurry effects, etc.;
4. Reduce your render LOD. -
Adam Trachtenberg
February 25, 2014 at 2:23 pm in reply to: How do you reset all 4 viewports to default- R15I think you’ll have to manually change them back by going into each viewport’s Cameras menu and selecting the appropriate perspective.
-
Have you tried using clips of real fire in AE? I don’t know how you can get more realistic than that. I think Video Copilot sells some collections of alpha-mapped fire footage.
I don’t think it’s possible to do a great job with fire in Cinema without plugins (Turbulence4D, Effex).
-
The GI preset you’ve chosen is designed for camera animation, meaning that the only thing that should be moving in the scene is the camera. It’s assuming that the samples will remain the same from one frame for the next as long as the camera angle doesn’t change too drastically. Since you have object animation, the samples aren’t matching up properly when the cloth object moves and deforms.
-
The only thing that should be moving from the Syntheyes scene is the camera, no?
My guess is that the issue is caused by the scale of the imported scene. Check to make sure that the collision radius in project settins>dynamics is close to the size of the dynamic pieces.
-
You should be able to fix it in Cinema using the “align normals” command, but if the object also has a normals tag that could mess things up. If it does I would try deleting the normals tag and see how it looks. You may also have to adjust the settings in the phong tag.
-
Yes, it’s better to use a random effector, setting the random mode to “sorted”.
-
Maxon generally recommends against using WIFI for Team Render because there’s just too much data moving back and forth and the slow WIFI connection is a bottleneck.
-
And your GI settings?
I would try the exterior HDR preset to start. Increasing “color refinement” in the irradiance cache tab will improve the shadow quality, which should help. You might also add ambient occlusion to help ground the car.