CINEVERSITY

    Maxon Logo
    • Login
    • Search
    • Recent
    • Popular
    • Users
    • Groups

    Parented objects render a "frame behind" where they're supposed to be

    Question & Answers
    2
    4
    45
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Balakay612
      Balakay612 last edited by

      Hi there.

      I have 8 spheres parented to 8 nulls. When I move the nulls, sometimes the position of the spheres doesn't update in the Redshift Render view unless I reset the render; that'd be fine, I could live with it, but when I to the actual render, the spheres are offset as though they're getting old position information from a frame ago. I have no idea why this is happening! Here's a render to illustrate the issue (hopefully it helps); I'd appreciate any help! Thank you!!

      parented_sphere_glitch2.jpg

      1 Reply Last reply Reply Quote
      • Dr. Sassi
        Dr. Sassi last edited by Dr. Sassi

        Hi Balakay612,

        When you see that and press the "a" key, are the spheres in place? Or if you cache a simulation first.
        If so, it is presumably a Priority problem.

        Please always share the file reduced to the problem. An image tells me very little, especially when cropped and nothing else is shared.

        In the past two decades of doing this, it has shown that long-winded questions or suggestion lists can be avoided when a file in instead of anything else is avaialble.
        The c4D format can be directly attached to the forum (<1MB). Cloud services are limited for security reasons to Dropbox, Wetransfer, Google, Apple, and Adobe. Upload the file to them, uncompressed, and share here the full URL, no HTML wrapper, etc.

        Thank you.

        The two main priority problems come from
        • Unorganized Object manager (top to bottom is the typically flow)
        • Priority settings are left on default or set to something that causes the problem.

        There are certainly more ways to get a delay. I'm happy to look into it.

        Cheers

        Dr. Sassi Sassmannshausen Ph.D.
        Senior Trainer, Maxon Master Trainer, L&D - Strategist
        Cinema 4D mentor since 2004, Member of VES, DCS.

        1 Reply Last reply Reply Quote
        • Balakay612
          Balakay612 last edited by

          Thank you for your response! It seems to have been an organizational issue: once I rearranged the offending elements (placing the grouped Nulls at the top), my test renders were corrected.

          And you're right about a photo not being terribly helpful: I'll provide scene files for future issues. Thanks again!

          1 Reply Last reply Reply Quote
          • Dr. Sassi
            Dr. Sassi last edited by

            Thank you very much, Balakay612!

            Yes, first of all, thanks for providing an image, and for understanding that the variety of the sources creating the problem can be rather large. Not that I know all the answers, who does (?), but I'm aware that each problem has that individual mix.

            I try to avoid exposing you to a guessing marathon, which can go on forever with no results, perhaps.

            My best wishes for your project

            Dr. Sassi Sassmannshausen Ph.D.
            Senior Trainer, Maxon Master Trainer, L&D - Strategist
            Cinema 4D mentor since 2004, Member of VES, DCS.

            1 Reply Last reply Reply Quote
            • First post
              Last post