-
layers disappear in final render (not ram-preview)
Hi all, hoping to tap in to others experience and past frustrations here.
I’ve got a semi heavy comp here. 45 layers or so, two lights, cam parented to null.
It’s a map with streats and a city wall drawn out around it during the corse of the animation. All layers are 3D apart from a background layer. The null drags the camera in towards the centre of the map in two movements. And during both movements separate layers disappear. The first time a 3d pre-comp of a stroke fades out and then fades in again when the cam motion is over. the pre comp is not collapsed. there is no fade inside the pre-comp, all the switches are on best quality, no motion blur etc. i’ve checked everything i can possibly think of, and the layer is on top in z-space, i.e. it doesn’t slip in under another layer during the camera movement. there is no animation on it what so ever apart from teh write-on effect which puts it into place to begin with. And the crazy thing is that the layer only disappears duing final render. It’s there in RAM previews all the time. The second disappearing layer happens during the next camera movement, all details similar to above, however this layer just flicks out at the start of the cam movement and then filcks back in again. Again, it looks all fine during the RAM preview, not a a hint of a flicker or anything. This problem won’t leave me alone and is driving me crazy!Sorry for longwinded explanation, but there it is… Hoping for some advice, thanks in advance! /d 🙂
I’m on a dualG5 AE6.5. 4gig ram. plenty of space on the drive.
-
10 Replies
-
Off the top of my head … are you RAM previewing something other than the Active Camera? Because AE can only render the Active Camera, not one of the custom or ortho views.
Steve
-
thanks, no i know.. 🙂 i’ve made that mistake before, but not this time. to many double checks down the line already. i’m def rendering the active camera view, same as would render out in final render.
thanks for your quick reply! doing a workarea test render now excluding layers one by one to track it down.
any other thoughts, don’t hesitate with obvious tips, i’m desperate…. /d
-
Hmm …
Do you have the advanced renderer on for the comp? (comp settings)
Have you tried soloing the offending layers, then making other layers visible one by one? Might be faster than switching off one by one. 🙂Let us know,
Steve -
thanks! good point, i’ve been doing test renders for a while now, so hopefully i’ll track it down quicker by your described method. 🙂
as for the advanced 3d render setting – i’ve got that ON, …however what about the: “preserve resolution when nested” setting? could that have something to do with it, or what does it do??? it’s not checked at the moment, nor is the one one above; regarding frame rate in nested comps. i’ve never really tampered with these checkboxes… should I?
/d
-
Mmm … I’d say that they don’t relate to your issue, one way or the other.
Can you send me the project? No footage is necessary. Send it to ads at reidroberts dot calm.
Steve
-
Thank for the offer Steve, believe it or not I’ve managed go get it to work with all layers on, but only small “work-area” test renders so far. I’ll continue and experiment. Maybe the whole thing is to big to actually process in which case I can pre-comp and split it up on several renders. Sounds weird, but could AE start making choices of what layers to focus on if render get’s too busy? sounds like quantum mechanics to me… 🙂
Thanks for all the help, and moral support and I might take you up on the offer and drop the proj if i still can’t make it work, but at the moment i’m on an up, and there is no greater feeling than a successful session of problemsolving! 🙂
thanks again, d
-
I ran into this just recently. I’m guessing you may be in a similar situation.
In my case, I had 3D layers with a 2D layer underneath AND on top. The RAM preview looked fine but wouldn’t render the 3D layers. If you precomp your 3D layers so that it’s now 2D you should be fine.
This is discussed in the help directory…something to do with the “priority of 3D rendering”.
-
hmmm, that rings a bell… funny thing is that i’ve made both problematic instances work in small full res test renders (not in a full time render though)
thing is,,,, all my layers in this comp are 3D, however one of the offending layers is a i have pre-comp of two 2d layers i wonder if that could have something to do with it, based on where that pre comp is placed in the main comp…
i will check this right away… thanks for the promt! /d 🙂
-
Have you checked that in your Render Settings>Effects: it says Current Settings. This drove me mad once.
-
I’ve had similar problems before, and I believe it was caused by a pre-comp that was a different frame rate than my final comp — I had one set to 29.97 and the other to 30 fps.
Karim Zouak
Reply to this Discussion! Login or Sign Up