2.6 - Batch Renderer no longer waits for auto-exposure to render

  • I have exterior and interior views with different exposure needs on a favorited set for batch rendering. With the new upgrade, the batch renderer just picks whatever the first exposure setting is and applies to all, rather than auto-exposing each image if the auto exposure has been checked.

  • I have exterior and interior views with different exposure needs on a favorited set for batch rendering. With the new upgrade, the batch renderer just picks whatever the first exposure setting is and applies to all, rather than auto-exposing each image if the auto exposure has been checked.

    We're checking it out currently - getting back to you once I have some news. :)

  • mattendler and Pieter , as of yet I've not been able to reproduce this problem - if anyone could share a screen-recording of this behavior, then that would also be fantastic for further troubleshooting purposes. Would that be possible?

  • We're seeing it on Revit, not sure whether that matters? Graphics card is a 1060 or 1070


    I'll try to do a screen recording, but it might be tricky because or machine is already strained doing the renders :)

  • I experienced this, it was a model when the batch render consisted of a few exterior scenes and then interior.

    The problem occurred when the 1st interior scene were being rendered.

    If I was to guess I’d say that Enscape delays xx ms to allow the auto exposure to ‘settle’ and then it starts rendering the image, if there’s a big shift in exposure (external view to interior view) between batched scenes then the delay isn’t long enough and the render starts before the exposure has settled.

    I’ll test the model again tomorrow and if it happens again I’ll do a feedback and link to this post.

    If I manually (F11) render the scene it worked perfectly but this is of course initiated after the scene’s exposure has settled.

  • Further recordings / feedback from you guys would still be great - as of yet I've still not been able to reproduce this problem I'm afraid. :/

  • Any chance you're testing this with a 1080 or 2080? Have you tried it on a large model using a modest card (1070 or 1060) in Revit?


    I'll try to record asap but it's been busy lately.

  • Demian Gutberlet I'm still suffering from this issue. I'm using a 1080 Ti. Revit 2019.2. What else do you need?

    I'm so sorry to hear about this - a brief screen recording would be great, using any software of your choice.. as mentioned, as of yet, I'm unable to reproduce this myself but will try once more. Thank you also in advance!

  • Hi! Any resolution on this issue? I discovered a similar problem during my Enscape trial. A single rendered image would be fine, but the exposures for batch rendered images were unusable and inconsistent. Interior renders were really dark, almost black, while exterior renders were over exposed and blown out. None of the batch rendered images matched what was shown in real time. The workaround I found was to mess around with the exposure settings for the different view types, but this was cumbersome and didn't really get ideal results. I've been emailing with support but haven't heard back since mid December when they were planning to check the issue with the developers. I was planning to buy a floating license, but I don't want to be committed to a full year of the software if this issue isn't resolved, as batch rendering is a must for my workflow.

  • Hi! Any resolution on this issue? I discovered a similar problem during my Enscape trial. A single rendered image would be fine, but the exposures for batch rendered images were unusable and inconsistent. Interior renders were really dark, almost black, while exterior renders were over exposed and blown out. None of the batch rendered images matched what was shown in real time. The workaround I found was to mess around with the exposure settings for the different view types, but this was cumbersome and didn't really get ideal results. I've been emailing with support but haven't heard back since mid December when they were planning to check the issue with the developers. I was planning to buy a floating license, but I don't want to be committed to a full year of the software if this issue isn't resolved, as batch rendering is a must for my workflow.

    Welcome to our forum - I am sorry to hear that you also experience this issue.


    You probably haven't received a reply just yet because many of our developers were in holiday over the past days, but I'm very sure that you get some feedback from our support team and/or from the devs very soon (if you haven't already). :) Please also gladly forward me your e-mail address by sending me a personal message in this forum. This way I can also check the status of the ticket at hand of yours.