Jim Scott
Forum Replies Created
-
You’re very welcome. I’m glad I was able to help.
A “pretty basic fix” is always in the eye of the beholder. It’s only “basic” once you know it’s there, and there’s a lot inside C4D to become familiar with. Enjoy the journey.
-
Make whatever adjustments you’d like to the planet’s orientation (H,P,B) in the Freeze Transformation section, and then keyframe the rotation about the Y-axis (H) in the upper Coordinates section.
-
Hi Sandra,
The workings of the various Texture windows and Shader Properties is easily confusing, so I hope this will help. When “Colorizer” is selected in the Texture window of the Color channel it remaps the image or shader which is selected in the Texture window in the Shader Properties (your second and third images) with the colors you define in the Gradient section. You need to pick (where your green arrows are pointing) what it is that you are colorizing – an image, gradient, noise, cel, etc., and then set up the colors that are to be remapped to it in the bottom Gradient section. With nothing selected in that Texture window it simply maps the first color in the gradient (black or red in your examples). When you selected “Cel,” and then back to “Colorizer,” the Cel texture remained as the Texture in the Shader Properties which was then remapped with the colors in the Gradient. To quickly set up a simple gradient on your material just select “Gradient” in the Texture selector of the Color channel, and then adjust the color knots in the Gradient window of the Shader Properties. With “Colorizer” in the Texture window of the Color channel, you could also select “Gradient” in the Texture window of the Shader Properties, which would then remap the colors of the bottom-most Gradient window onto the gradient of the Shader Properties, but that’s just adding an unnecessary step.
By the way, excellent use of images to help clarify your questions.
-
Good deal.
-
Just a heads up…
-
Without seeing your project file, anyone would just be guessing as to the issue you are experiencing.
-
As I said, I don’t remember where I heard about the issue with Rosetta, FCS3, and newer OS installations. I was simply repeating it as a possible explanation for your problems. I am happy to be corrected on this.
Unfortunately, as many have repeated, FCS3 is essentially ancient software that was not designed to run on newer OSs, and as such will often be at least finicky, if not worse. I myself have a FCP7 installation on a disk that was upgraded to Yosemite, and one which will run, but is often unresponsive and unusable. As I also have Premiere Pro I have switched to using it as my main video editor because of my experiences with FCP. I wish I could still use FCP, but unfortunately that hasn’t turned out to be an acceptable experience for me. You mileage may vary.
-
I can’t remember where I ran across this, but apparently because Rosetta is not supported in Mavericks and later, those OSs will not allow installation of FCS3. If you had upgraded your OS on a drive that already had FCS3 installed on it, it would have been available. Whether or not it would work well, or at all, is another story. But since you did a clean install to a non-Rosetta supporting OS, that new OS is preventing installation.
-
In R17 there is an Align Workplane command which will result in the behavior you see with the move tool, but it wouldn’t cause your other issues. Since that command is not available in R13, I don’t know what the culprit is. I assume you have tried quitting and restarting C4D? If not, that and restarting your computer would be a place to start.
-
Post a download of your C4D project file so that we can see your render settings.
