645 posts 1 stop solution of all Motion Graphics Needs
  • Elite Author
  • Author Level 8
  • Trendsetter
  • Top Monthly Author
+9 more
StrokeVorkz
says

How do you render for preview, direct flv?, try full resolution png or jpg seq and then go for flv from the rendered seq

428 posts
  • Trendsetter
  • Weekly Top Seller
  • Affiliate Level 2
  • Author Level 5
+6 more
bilalmarri
says

fixed :) the ramp effect in the background was causing the problem. i don’t know why but removing it did the trick for me. thanks for the help guys

5327 posts
  • Elite Author
  • Moderator
  • Weekly Top Seller
  • Top Monthly Author
+13 more
felt_tips
Moderator
says

the point at which the images are being lost. flicks in fact, instead of glitch. those are unintentional still checking whats wrong there..

It could be that cache is not being cleared on certain frames. Although this is a problem more common to CS6 with its global caching, it can also happen in CS5 .5. I’ve a feeling that Trapcode Particular might have something to do with it, but don’t quote me on that.

I doubt very much that it was the Ramp effect, but removing the Ramp effect, will have invalidated the cache, allowing the frames to render properly. You could also have tried very slightly changing the parameters of the Ramp effect. I expect this would have had the same effect.

Possibly, purging RAM and emptying the disk cache might solve the problem too.

428 posts
  • Trendsetter
  • Weekly Top Seller
  • Affiliate Level 2
  • Author Level 5
+6 more
bilalmarri
says

i tried changing the values of the ramp effect. in the end the only thing was working by removing the ramp effect. but it could be the cache also. i am just happy that its fine now :)

531 posts
  • Weekly Top Seller
  • Featured Author
  • Featured Item
  • Most Wanted Winner
+7 more
DoubleX
says

I met similar glitch a couple of times, basically everytime I was creating a new 3D project. It was always caused by 3D layers and their aligment in the 3D space. If you use 3D layers and have some camera movement, this glitch may appear when these layers have the same Z-position, so they are overlaying themselves. Moving every layer in the z-space (few pixels are enough) always solved the problem.

428 posts
  • Trendsetter
  • Weekly Top Seller
  • Affiliate Level 2
  • Author Level 5
+6 more
bilalmarri
says

infact the layers had the same z position :)

5327 posts
  • Elite Author
  • Moderator
  • Weekly Top Seller
  • Top Monthly Author
+13 more
felt_tips
Moderator
says

That would make sense. There are small rounding errors in Ae 3D (actually, there are sometimes some quite big ones …. known bug).

But if you put things at the same position in 3D space, it’s anyone’s guess which one’s going to appear in front.

531 posts
  • Weekly Top Seller
  • Featured Author
  • Featured Item
  • Most Wanted Winner
+7 more
DoubleX
says

But if you put things at the same position in 3D space, it’s anyone’s guess which one’s going to appear in front.
Well, the one on the top in timeline should be the one in front (same way as in 2D composition), but any movement against the camera causes these artifacts.

infact the layers had the same z position :)
Then try to move every single one a little bit and let us know! :)
5327 posts
  • Elite Author
  • Moderator
  • Weekly Top Seller
  • Top Monthly Author
+13 more
felt_tips
Moderator
says

Well, the one on the top in timeline should be the one in front (same way as in 2D composition), but any movement against the camera causes these artifacts.
That’s what I mean… anyone’s guess. :-)

I’ve found a few bugs in complicated 3D scenes where layers that are several pixels closer to the camera are being rendered behind layers that are several pixels further away.

You could always force the issue by putting a little 2D “breaker” layer between the two 3D ones. It’s not always possible, of course, but in many situations it’s a useful trick.

by
by
by
by
by
by