Darby Edelen
Forum Replies Created
-
I don’t think it’s a problem with your UVs or at least your UVs aren’t the only problem.
Look at what Adam suggested again. Your Photoshop texture does not appear to be seamless. To test this you can use the Other > Offset filter to offset the image horizontally using ‘Wrap Around’ and you should see an obvious seam in the image. You can fix this seam manually once your texture is offset.
If I were a betting man I’d place a wager that you blurred your swish with the edges cropped in the Photoshop file.
Darby Edelen
-
Perhaps the problem is in R14? Seems unlikely but possible.
Darby Edelen
-
Just realized that I made an incorrect statement in the previous post. You should be able to get from 59.94 frames per second to 59.94 fields per second and have each field represent a different instant in time (it should look “interlaced”).
However, depending on the application you’re using to create the interlaced file you may want to choose a 29.97 interlaced output rather than 59.94 interlaced. Both After Effects and Adobe Media Encoder work that way. You first select the 29.97 frame rate (not the field rate 59.94 as reported in 1080i 59.94) and then define whether the output should be progressive or interlaced.
Darby Edelen
-
This generally is a result of Keylight’s despill doing a bad job. Try changing the view to Intermediate Result rather than Final Result and then despilling by some other means if necessary.
Here’s a post where I describe how I like to despill:
https://forums.creativecow.net/readpost/2/1027628
Darby Edelen
-
When going from 59.94 progressive to 59.94 interlaced, what is your expectation? Mine is that you’ll end up with a single frame across two fields. This means it will still look progressive. The only way in which it might be different than progressive is if the format you transcoded to includes some flags/metadata about interlacing and fields.
Darby Edelen
-
I second that. I think you want the Jiggle deformer.
Darby Edelen
-
I rendered using the settings in the file you posted as-is, which I believe was set to output frames 48-100.
I noticed that the image you posted looks like it has some textures that may not have come through in the project file you posted. If that’s the only difference between the files perhaps that’s a place to start?
I’m working with Cinema 4D R13.061 on Mac OS 10.7.5.
Darby Edelen
-
[Todd Kopriva] “Why wouldn’t you just have the layer parented to a single item and have the parent layer’s animation change as needed?”
Or parent your parent to another parent. 🙂
Darby Edelen
-
Can you give some more information about what it is you’re trying to achieve?
The shader effector is only capable of changing the internal color value of the clones. The multishader is capable of reading the internal color value or index ratio of clones and choosing a corresponding texture based on that value.
You generally wouldn’t want to try to modify the internal color of the clones with a shader that varies depending on the internal color of those clones… unexpected results are to be expected 🙂
Darby Edelen
-
I didn’t see any problems rendering your scene here. Have you made any progress finding a solution?
Darby Edelen