Skip to main content
ericc19576445
Known Participant
April 22, 2017
Question

Not responding (all versions so far)

  • April 22, 2017
  • 23 replies
  • 1889 views

Preparing Scene mode always causes CH to become non-responsive ("not responding") for extended periods of time. I'm assuming this is because of rendering, but it doesn't seem that the software isnt maxing out on cpu or ram. Is this normal?

    This topic is closed to new replies. Start a new post to keep the conversation going.

    23 replies

    DanTull
    Adobe Employee
    Adobe Employee
    May 22, 2017

    It just got fixed internally and is a fairly small and localized fix.

    There's not another planned release for a while, though.

    Dan Tull

    DanTull
    Adobe Employee
    Adobe Employee
    April 24, 2017

    The compilation process for complex scenes (like our Getting Started project, which is precompiled to make it open more quickly) can take an extended period, aren't as parallel as they could be (like, for example, video encoding which can scale to many cores), and should really have some kind of cancelable/progress UI but they currently do not.

    Launching directly into aa large scene from an earlier version can be particularly taxing since it also does a project format upgrade which tends to invalidate prior cached renderings of the scene requiring them to be regenerated.

    So it is normal, but agreed that it is definitely not ideal.

    Dan Tull

    ericc19576445
    Known Participant
    April 24, 2017

    It takes a long time to process under any circumstance, though.

    For example, if I already compiled the scene, go back into my puppet and add 1 handle and then go back to the scene to see the result. It takes the same amount of time and says not responding. About 10 mins on average. I can officially say I've spent more hours waiting for compiling than actually working. Not an exaggeration. It kills all momentum in workflow. It legitimately seems like it's recompiling the entire scene every time.

    I7 quadcore 3.5ghz 16 gb ram. No other programs in process. Also looks like CH won't use more than 20% cpu and 8gb ram eventhough I have plenty of cpu and ram left over.

    DanTull
    Adobe Employee
    Adobe Employee
    April 24, 2017

    Oh, that does sounds really strange.

    Usually the first hit is way worse for most scenes I have encountered because Ch can re-use a lot of the rendering it did in a prior pass and invalidate only those parts impacted by the change that was made.

    I'll get in touch with information on where/how to send the project and hopefully I can figure out why this is behaving so badly.

    Dan Tull