Loading...
> >

I may abandon IRay and revert to 3DL, however...

12346»

Comments

  • kyoto kidkyoto kid Posts: 42,391

    ..ahh yes the dreaded 3DL "Optimisation Pass".  Yeah I get that too at times, but again usually only once a session and then only on the first render attempt or when I make massive changes to a scene.   It can be a real pain in a big scene. but afterwards the rendering process itself is still much quicker than Iray on the CPU.

  • laststandlaststand Posts: 866
    kyoto kid said:

    ..ahh yes the dreaded 3DL "Optimisation Pass".  Yeah I get that too at times, but again usually only once a session and then only on the first render attempt or when I make massive changes to a scene.   It can be a real pain in a big scene. but afterwards the rendering process itself is still much quicker than Iray on the CPU.

    I start with a 100K figure. I add hair - I mean stranded hair - do we call it fiber hair? and the file is suddenly 20M (?). It renders quickly enough, but if I so much as rotate the figure, requiring the workspace to be repainted, DAZ stops in its tracks.  Give it another command before this repainting is completed, and you might just find the program closing down. According to that thread I linked to, DAZ is coded to use only a single CPU core for this "preparing" activity, regardless of what resources are available.  Gramma will not be hurried.  There's just no way around it. 

    It is what it is.

  • kyoto kidkyoto kid Posts: 42,391

    ...what particular hair?

  • laststandlaststand Posts: 866
    kyoto kid said:

    ...what particular hair?

    Well, this is sobering.

    Add G2M             file size 57K

    Add fit-to Whiskers Beard Strays              file size now 9.3M

    Add fit-to Whiskers Moustache Strays                   file size now 11.4M

    Add fit-to Mathius Hair file size now 19.6M

    For comparison....

    Add G3M             file size now 21K

    Add Whiskers Beard Strays          file size now 33K

    Add Whiskers Moustache Strays                               file size now 43K

    Add Mathius Hair             file size now 99K

    ............................

    I had no idea Fit To did this.

  • kyoto kidkyoto kid Posts: 42,391
    edited February 2018

    ...so in the second example, you simple manually fit/parented everything?

    Post edited by kyoto kid on
  • laststandlaststand Posts: 866
    kyoto kid said:

    ...so in the second example, you simple manually fit/parented everything?

    In the second example I applied the hair and let it fit itself without any manual interaction. No Fit To dialog was presented, no manual interaction was needed, since the hair was made for the G3 figure to begin with.

    The 20M file size didn't interfere with rendering per se', only with DS preparing. The VRAM usage was well within the 1070's ability.

    I've never looked at file sizes this closely before, since I've never prepared to render before, not seriously. It's an eye-opener.  Thanks for asking me about this.  I thought it was normal.

  • PadonePadone Posts: 4,308

    The iray initialization time is mainly for texture compression. It's similar to what 3DL does for mipmapping. To speed it up you can resize textures and/or disable compression in the render settings.

  • TaozTaoz Posts: 10,344
    Rottenham said:
    kyoto kid said:

    ..ahh yes the dreaded 3DL "Optimisation Pass".  Yeah I get that too at times, but again usually only once a session and then only on the first render attempt or when I make massive changes to a scene.   It can be a real pain in a big scene. but afterwards the rendering process itself is still much quicker than Iray on the CPU.

    I start with a 100K figure. I add hair - I mean stranded hair - do we call it fiber hair? and the file is suddenly 20M (?). It renders quickly enough, but if I so much as rotate the figure, requiring the workspace to be repainted, DAZ stops in its tracks.  Give it another command before this repainting is completed, and you might just find the program closing down. According to that thread I linked to, DAZ is coded to use only a single CPU core for this "preparing" activity, regardless of what resources are available.  Gramma will not be hurried.  There's just no way around it. 

    It is what it is.

    I don't have this problem after "preparing" has finished, even huge scenes that use close to all my RAM and VRAM spin pretty fast around without crashing DS.

    If it says "Not responding" it doesn't necessarily mean it's crashed (though it may in som cases), it just means that a thread is running for longer than 5 seconds without notifying Windows, which it expects. This is quite common for single thread operations, you may call it bad programming because you can't see if it's crashed or not, but otherwise it's causing no problems as such.

  • laststandlaststand Posts: 866
    Taoz said:
    Rottenham said:
    kyoto kid said:

    ..ahh yes the dreaded 3DL "Optimisation Pass".  Yeah I get that too at times, but again usually only once a session and then only on the first render attempt or when I make massive changes to a scene.   It can be a real pain in a big scene. but afterwards the rendering process itself is still much quicker than Iray on the CPU.

    I start with a 100K figure. I add hair - I mean stranded hair - do we call it fiber hair? and the file is suddenly 20M (?). It renders quickly enough, but if I so much as rotate the figure, requiring the workspace to be repainted, DAZ stops in its tracks.  Give it another command before this repainting is completed, and you might just find the program closing down. According to that thread I linked to, DAZ is coded to use only a single CPU core for this "preparing" activity, regardless of what resources are available.  Gramma will not be hurried.  There's just no way around it. 

    It is what it is.

    I don't have this problem after "preparing" has finished, even huge scenes that use close to all my RAM and VRAM spin pretty fast around without crashing DS.

    If it says "Not responding" it doesn't necessarily mean it's crashed (though it may in som cases), it just means that a thread is running for longer than 5 seconds without notifying Windows, which it expects. This is quite common for single thread operations, you may call it bad programming because you can't see if it's crashed or not, but otherwise it's causing no problems as such.

    I don't have this problem now either, since I stopped using autofit on hair. smiley

    I don't come to this forum to criticize the way DAZ is coded. I accept the program for what it is. The trick is often to actually find out what it is. This forum is possibly the most valuable of the learning tools available to us. Besides which, since I'm not a programmer and do not aspire to be, I can't really critique the work of others (except from a UI perspective). I am currently learning to pay close attention to that tiny string of status text that sometimes appears at the bottom of the workspace.

    I've had a chance to do a fast evaluation of IBL Master. It's a sophisticated lighting control interface, implemented professionally. For that, I like it. I don't feel that it puts me in a position to choose freely between 3DL and iRay, though, as I thought it might.  kk mentioned something about some new shader tool that is in the works, I'll be keeping an eye out for that. Meanwhile I'll stick with iRay.

     

Sign In or Register to comment.