Skip to main content
B
bennettes58638900
Participating Frequently
November 24, 2018
Question

element 3d render issue

  • November 24, 2018
  • 3 replies
  • 6641 views

Hi all,

  I've been trying to find out why my video render is coming out with such a weird error.  Hours looking at forums so far, and no luck.  I have a fairly simple scene that is doing just fine in the preview window at quarter and third resolution settings.  However, when I send it to Media Encoder, to render to h.264 in 1080p (which is the comp res), the encoder is generating random frames of my mask layers that i used to extrude the element object, and nothing else.  This is also what happens in the preview window when I set the resolution to full.  To hopefully narrow this down: I don't have any layers toggled on as guide layers, and these layers aren't even live until 00:02:00, they're hidden, and they're showing up in the output in the first few frames.  It seems like the encoder is just freaking out and giving up or something - the encoding should take a lot more time, and once it gets to the complex scene, it just stalls on a frame for a minute, then squirts out a bunch of errant frames and finishes in no time.

My computer is a late 2012 macbook pro, fully loaded, with a Nvidia GeForce GT 650M with 1gb of VRAM.  I don't know if that's it, but I also updated the CUDA driver, as well as reinstalled Element 3D and After Effects.  Same issue after all that.  Additionally, I tried encoding to different settings and resolutions, with no difference.  I know I don't have a lot of VRAM compared to newer machines, but I've rendered much more complex things on this before.

rendering at quarter resolution.

why...?

      This topic has been closed for replies.

      3 replies

      OussK
      OussK
      Adobe Expert
      November 26, 2018

      Elements 3d render only on GPU, and it's related directly to texture size and as you mention you have some texture, shader  and bump map, so may your texture are very hight resolution and this block your GPU from reading the full resolution because your small VRAM,

      so try to remove the texture and do a render test, or try to scale down this texture at least.

      Mo Moolla
      Mo Moolla
      Brainiac
      November 26, 2018

      Agreed turn down the texture settings

      B
      bennettes58638900Author
      Participating Frequently
      November 26, 2018

      Here are the layers I'm using - not many, although the "SM" model has multiple extruded parts, and a plane with a stone shader and bump.  The two other E3D shapes (car and ball) are somewhat complex imported .obj files.  The two precomps are just the toy car, the ball, and two spot lights.  Again, the whole thing renders and plays in 1/4 res, just with the UFO's popping in and out.

      B
      bennettes58638900Author
      Participating Frequently
      November 26, 2018

      Oh, and you can disregard the "piece" layers, those are just lossless renders from directly from AE I'm using in place, but I just rendered and put those in.

      R
      Rick Gerard
      Adobe Expert
      November 24, 2018

      Element 3D does not use CUDA acceleration, neither does the AME. You are using Classic 3D so there should be no problem.  As long as you purge everything you should bet a clean render.

      I have no idea what is going on in the comp at 11 or 24 seconds because the only thing in the screenshot is an audio layer and a nested comp. What is going on in the nested comp (pre-comp)? Check the modified properties of the layers giving you problems (press UU) and if you can not figure it out then post a screenshot that shows us what is going on in those layers.

      If you are only having problems with the frames in the nested comp try adding Pre-comp 2 to the render cue, pick the Lossless with Alpha preset and render and replace in your project.

      The first rule I have with complex scenes is to make each shot a separate comp and simplify as much as I can. If the render is going to take more than a few seconds a frame I render an image sequence because it is a lot easier to fix. Really complex comps are almost never sent to the AME directly to render an MP4 for distribution because complex composites can take a very long time to render and seriously tax the AME and AE running in the background. I almost never assemble a sequence in AE using nested comps as separate shots because it's just a lot easier to handle the rest of the post process in an NLE.

      I hope these suggestions help. If there is nothing wrong in Pre-comp 2 rendering and replacing should fix the problem.

      B
      bennettes58638900Author
      Participating Frequently
      November 25, 2018

      Hi Rick,

        First of all, you frequently answer these and generally speaking, I've found your advice to be sage, on point, and generally is trying to shed light on best practices.  For this I thank you.  What I found when I rendered small pieces is that, like you said, I could try to see what is happening in each frame when this occurs.  I don't think I know what the cause is, but for some reason, if I altered the positions of the objects a negligible amount, they'd show up in the frames.  Would you have any idea why this is?  Could I be doing something better?  I have preview mode on, but I have objects that will look crappy unless I'm bumping up supersampling a notch.  Again, thanks so much.

      Bennette

      Andrew Yoole
      Andrew Yoole
      Adobe Expert
      November 25, 2018

      I mean, the objects were there just like they should be, and on seemingly random frames, just disappear and come right back two frames later.  No keyframes, nothing special about those frames.


      Simply re-iterating Rick's advice, for clarity:

      Clear your cache before rendering.

      Render from the Render Queue, rather than in AME.

      Does this fix the problem?

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices