does the 'rendering quality' bar for Iray in the rendering editor actually do anything?

ToobisToobis Posts: 990

If you don't know where I mean I mean here (in pic). It doesn't seem to matter what number I put in whether its 100 or 3000 the quality of the render remains the same when done. Is there something I'm doing wrong or maybe its not supposed to work for me for some reason.

Feedback greatly appreciated. Try to be simple if you can lol.

Comments

  • nicsttnicstt Posts: 11,715

    Yes.

    I presume you want the longer answer: it will increase the render time - usually resulting in a 'better' image.

  • ToobisToobis Posts: 990
    nicstt said:

    Yes.

    I presume you want the longer answer: it will increase the render time - usually resulting in a 'better' image.

    umm ok...  but it doesn't?! I mean it takes longer but no improvement. Is this common for most people or?!?!

  • RafmerRafmer Posts: 564

    From the Iray programmer's manual:

    Convergence quality estimate

    At some point the progressive rendering will have reached a quality where subsequent frames will not have any visible effect on the rendering quality anymore. At this point rendering may stop. This can be based on a convergence quality estimate that can be computed in the non-interactive rendering mode. This estimate can be controlled with the following parameters: a quality parameter that determines when a pixel is considered converged, and an overall converged pixel ratio.

    The following attributes on the mi::neuraylib::IOptions class, shown here with their default settings, control the convergence quality estimate:

    bool progressive_rendering_quality_enabled = true

    The convergence quality estimate is only available in the non-interactive render mode and can, in addition, be enabled and disabled with this attribute. If disabled, rendering will not stop based on the convergence quality and no progress messages will be issued for the current convergence quality.

    mi::Float32 progressive_rendering_quality = 1

    A convergence estimate for a pixel has to reach a certain threshold before a pixel is considered converged. This attribute is a relative quality factor for this threshold. A higher quality setting asks for better converged pixels, which means a longer rendering time. Render times will change roughly linearly with the given value, i.e., doubling the quality roughly doubles the render time.

    mi::Float32 progressive_rendering_converged_pixel_ratio = 0.95

    If the progressive rendering quality is enabled, this attribute specifies a threshold that controls the stopping criterion for progressive rendering. As soon as the ratio of converged pixels of the entire image is above this given threshold, Iray Photoreal returns the final result for forthcoming render requests. Additionally, the render call will return 1 in this case indicating to the application that further render calls will have no more effect. Note that setting this attribute to a value larger than the default of 0.95 can lead to extremely long render times.

    The convergence quality estimate has some computational cost. It is only computed after some initial number of samples to ensure a reasonably meaningful estimate. Furthermore, the estimate is only updated from time to time.

  • fastbike1fastbike1 Posts: 4,078

     Your specific results are highly dependent on your hardware, your scene makeup, your lighting, and your render settings. 

    Toobis said:
    nicstt said:

    Yes.

    I presume you want the longer answer: it will increase the render time - usually resulting in a 'better' image.

    umm ok...  but it doesn't?! I mean it takes longer but no improvement. Is this common for most people or?!?!

     

  • TheKDTheKD Posts: 2,711

    Yeah, if there is not enough light bouncing around the scene, no ammount of iterations is gonna clean up the grain. If the scene is well lit, it should just keep getting cleaner and cleaner(less noise)

  • nemesis10nemesis10 Posts: 3,790

    If you don't know where I mean I mean here (in pic). It doesn't seem to matter what number I put in whether its 100 or 3000 the quality of the render remains the same when done. Is there something I'm doing wrong or maybe its not supposed to work for me for some reason.

    Toobis said:

    Feedback greatly appreciated. Try to be simple if you can lol.

    My guess is what you want to be looking at is Daz Studio > Filtering> Pixel Filter> change from Gaussian to Mitchel and change the value from 1.5 to 1.  This tells Daz Studio to make your image sharper.   Then you can increase convergence time (rendering quality)to get to the quality you want.  

  • TheKDTheKD Posts: 2,711
    edited March 2020

    Oh, another thing I thought of.... It could be the time limit, or max samples stopping the render. If you want only quality to control the render stop, turn max time to 0, and crank max samles up by a few zeros. Click on the gear on the right of the max samples box, add a few 0's to the max section, then max the slider out again.

    Post edited by TheKD on
  • SpottedKittySpottedKitty Posts: 7,232
    Toobis said:

    It doesn't seem to matter what number I put in whether its 100 or 3000 the quality of the render remains the same when done.

    If that's the sort of values you're putting in, that might be your problem. I usually only change the value to 2 or 4 — that and changing the Converged Ratio value to something above 99% (but must be below 100%) usually gives me a nice crisp render. The default values of Quality at 1 and Converged at 95% are a compromise between render quality and render time.

    Also, note that unfeasibly large Quality values will also give you unfeasibly long render times.

Sign In or Register to comment.