Loading...
> >

New Iray render engine. Too good to be true?

2456789

Comments

  • hphoenixhphoenix Posts: 1,335
    pkappetein said:

    I'll try that when i get home..  it  does render but seemed very slow.

    Think I had the latest driver, but i'll double check

    nVidia released several driver updates over the last few months.  If you haven't updated your drivers in the last 3-4 months, you don't have the newer drivers.  I believe Iray 2016.3 requires 372.x or higher drivers to run CUDA 8 (which is needed.)  Without that, Iray won't even recognize most cards, and will drop to CPU rendering.

     

     

  • nonesuch00nonesuch00 Posts: 18,714

    The iRay Renderer is massively increased in speed although for an 5 years 2nd Gen i5 (2 cores with 4 'virtual cores total') I wouldn't see it's fast enough to use in Preview mode.

    The DAZ Public Beta Version is 4.9.3.166 which I just downloaded but oddly that was the same Public Beta Version I had yesterday before the download (via DIM).

    The new one seems to have introduced a couple of artifacts though. It could have something to do with the M4 to G3 UV Geografting product from Cayman Studio though. It can affect certain objects that use iRay materials.  When you use the UberiRay Shader converter on the Slosh Jumper when it is being worn by a figure that has the M4 to G3M UV Geografts applied it falls to apply the iRay conversion to the jumper and the jumper has artifacts. The same is not true if you apply the iRay Uber shader conversion to the jumper worn by the G3M figure that has not had the Cayman Studio M4 to G3M geografts applied.

    Something to note on this newest Public Beta is that although the problem of the Uber iRay material converter preset failing to convert the Slosh G2M jumper worn on a G3M was already a problem, these visible material artifacts were not preset. I managed to manually convert the jumper surfaces to iRay by manually copy and pasting the surface settings from the trousers but that did not rid the jumper of the artifacts.

    So, this is something to take note of if you use a lot of these different Geograft and UV conversions products, which I know alot of you do

    Your left - G3M fitted with G2M Slosh jumper and jumper converted to Uber iRay surface settings

    Your right - G3M with Cayman Studio M4 to G3M UV Geografts with G2M Slosh jumper and jumper converted to Uber iRay surface settings via a copy of the trousers surface settings after conversion with the Uber iRay Surface Settings preset as the Uber iRay Surface Settings preset fails to convert the jumper. Note the white surface artifacts on the jumper.

     

    a.png
    974 x 288 - 188K
  • fastbike1fastbike1 Posts: 4,078

    @nonesuch00   4.9.3.166 is now the Release version. No longer Beta.

  • nonesuch00nonesuch00 Posts: 18,714
    edited January 2017
    fastbike1 said:

    @nonesuch00   4.9.3.166 is now the Release version. No longer Beta.

    Oh, OK. Well then the Cayman Studio M4 to G3M geografting product or D|S 4.9.3.166 release or both have bugs.

    thanks.

    Post edited by nonesuch00 on
  • nonesuch00nonesuch00 Posts: 18,714
    edited January 2017

    OK, well I'm managed to divide the earlier troubles in two.

    1. The Uber Iray Surfaces Preset not applying to the G2M Slosh Jumper only happened when the jumper was worn by a G3M with the M4 to G3M Geographs applied.

    2. The iRay surfaces artifacts on the Slosh G2M jumper happens when I chose the Michael 4 UV sets (part of the Cayman Studio M4 to G3M product) or it happens once again on a 2nd imported G3M model when I use Slosh's G3 UV Swap product even without the Cayman Studios product applied.

    So 1. I don't know if it's a DAZ Studio bug or a external product bug, but 2. I am pretty sure is a DAZ Studio 4.9.3.166 bug although I need to try something other then the Slosh G2M Naval Jumper and change UVs I suppose.

    Well maybe not a bug but the way auto-fit is working has changed.

    Post edited by nonesuch00 on
  • pkappeteinpkappetein Posts: 506
    hphoenix said:
    pkappetein said:

    I'll try that when i get home..  it  does render but seemed very slow.

    Think I had the latest driver, but i'll double check

    nVidia released several driver updates over the last few months.  If you haven't updated your drivers in the last 3-4 months, you don't have the newer drivers.  I believe Iray 2016.3 requires 372.x or higher drivers to run CUDA 8 (which is needed.)  Without that, Iray won't even recognize most cards, and will drop to CPU rendering.

     

     

    Think the driver is maybe 2 months old..  I know it takes Iray, since I see it processing the Iray and i can see the image.  See something like  V1.2  .... and the total memory of the video card  8Gb etc.  

    I had both items checked.  (first I had  only the GPU card checked)  but the GPU is faster than the CPU one.  but  it seems slow as when i look with others that takes

    45 seconds for a few minutes.

    When I started loading a basic scene, and started,  after 5 minutes it was at 0% and 12-15 cycles done.

    I would inmagine that it can be done a lot faster.

     

  • SpottedKittySpottedKitty Posts: 7,232
    nonesuch00 said:
    The DAZ Public Beta Version is 4.9.3.166 which I just downloaded but oddly that was the same Public Beta Version I had yesterday before the download (via DIM).

    That's been normal for the last several D|S versions — when there's a new release full version, the beta is updated to the same version. Note that this isn't always the last released beta version, there's frequently a few little (or not so little) things that need last-minute attention.

  • nonesuch00nonesuch00 Posts: 18,714
    SpottedKitty said:
    nonesuch00 said:
    The DAZ Public Beta Version is 4.9.3.166 which I just downloaded but oddly that was the same Public Beta Version I had yesterday before the download (via DIM).

    That's been normal for the last several D|S versions — when there's a new release full version, the beta is updated to the same version. Note that this isn't always the last released beta version, there's frequently a few little (or not so little) things that need last-minute attention.

    Thanks. I am very happy with 4.9.3.166 except the slight changes I had to adjust to with autofit.

  • TottallouTottallou Posts: 555
    pkappetein said:
    hphoenix said:
    pkappetein said:

    I'll try that when i get home..  it  does render but seemed very slow.

    Think I had the latest driver, but i'll double check

    nVidia released several driver updates over the last few months.  If you haven't updated your drivers in the last 3-4 months, you don't have the newer drivers.  I believe Iray 2016.3 requires 372.x or higher drivers to run CUDA 8 (which is needed.)  Without that, Iray won't even recognize most cards, and will drop to CPU rendering.

     

     

    Think the driver is maybe 2 months old..  I know it takes Iray, since I see it processing the Iray and i can see the image.  See something like  V1.2  .... and the total memory of the video card  8Gb etc.  

    I had both items checked.  (first I had  only the GPU card checked)  but the GPU is faster than the CPU one.  but  it seems slow as when i look with others that takes

    45 seconds for a few minutes.

    When I started loading a basic scene, and started,  after 5 minutes it was at 0% and 12-15 cycles done.

    I would inmagine that it can be done a lot faster.

     

    I use Nvidia Drivers 376.33 (release date 13th December) & have had no problems with a GTX1080

    If you think you have the correct drivers try testing the benchmark scene

    http://www.daz3d.com/forums/discussion/53771/iray-starter-scene-post-your-benchmarks

     

     

     

  • hphoenixhphoenix Posts: 1,335
    pkappetein said:
    hphoenix said:
    pkappetein said:

    I'll try that when i get home..  it  does render but seemed very slow.

    Think I had the latest driver, but i'll double check

    nVidia released several driver updates over the last few months.  If you haven't updated your drivers in the last 3-4 months, you don't have the newer drivers.  I believe Iray 2016.3 requires 372.x or higher drivers to run CUDA 8 (which is needed.)  Without that, Iray won't even recognize most cards, and will drop to CPU rendering.

     

     

    Think the driver is maybe 2 months old..  I know it takes Iray, since I see it processing the Iray and i can see the image.  See something like  V1.2  .... and the total memory of the video card  8Gb etc.  

    I had both items checked.  (first I had  only the GPU card checked)  but the GPU is faster than the CPU one.  but  it seems slow as when i look with others that takes

    45 seconds for a few minutes.

    When I started loading a basic scene, and started,  after 5 minutes it was at 0% and 12-15 cycles done.

    I would inmagine that it can be done a lot faster.

     

    In addition to using the benchmark scene @Totallou mentioned, also check the log file after the render starts (you'll have to cancel the render, but wait until you see iterations being completed.)  Toward the bottom, it should show whether any Iray devices were found or are being used.  It'll also say if it dropped to CPU.

     

  • TooncesToonces Posts: 919

    I agree. Probably dropped to CPU. 

    If you use windows, download GPUZ. It will show you if your graphics card(s) are being used. Log file in Daz will also tell you. Actually even the little render window tells you so long as you've expanded the mini log window inside it. It shows how much it's attempting to load into each card and then you may see a line about CPU (whenever I see this line, I know it's doing a CPU render).

  • pkappeteinpkappetein Posts: 506

    ok installed the latest drivers and started a scene, and waited for a bit  after 5 min. it was still 0%  but this is what's showing

     

    2017-01-05 17:17:39.977 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating geometry.
    2017-01-05 17:17:44.429 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using built-in ray tracing (1.0.0).
    2017-01-05 17:17:44.429 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Importing geometry.
    2017-01-05 17:17:44.478 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Geometry import (1 object with 273k triangles, 1 instance yielding 273k triangles) took 0.060047
    2017-01-05 17:17:44.478 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating materials.
    2017-01-05 17:17:44.494 Iray INFO - module:category(MATCNV:RENDER):   1.0   MATCNV rend info : found 383 textures, 0 lambdas (0 unique)
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Emitter geometry import (5 light sources with 1644 triangles, 1 instance) took 0.00s
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating environment.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lens.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lights.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating object flags.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating caustic portals.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating decals.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Allocating 1 layer frame buffer
    2017-01-05 17:17:44.532 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, architectural sampler disabled, caustic sampler disabled
    2017-01-05 17:17:44.532 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.
    2017-01-05 17:17:44.579 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 1 device(s):
    2017-01-05 17:17:44.579 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CUDA device 0 (GeForce GTX 1070)
    2017-01-05 17:17:44.579 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...
    2017-01-05 17:17:44.579 Iray VERBOSE - module:category(IRAY:RENDER):   1.3   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
    2017-01-05 17:17:44.874 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.7   IRAY   rend warn : RTKernel: please check the input geometry (degenerated/inefficient RT hierarchy)
    2017-01-05 17:17:44.880 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Geometry memory consumption: 7.91974 MiB (device 0), 0 B (host)
    2017-01-05 17:18:01.892 Iray INFO - module:category(IRAY:RENDER):   1.7   IRAY   rend info : Initializing light hierarchy.
    2017-01-05 17:18:01.892 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Texture memory consumption: 4.56567 GiB (device 0)
    2017-01-05 17:18:01.923 Iray INFO - module:category(IRAY:RENDER):   1.7   IRAY   rend info : Light hierarchy initialization took 0.03s
    2017-01-05 17:18:01.923 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Lights memory consumption: 284.957 KiB (device 0)
    2017-01-05 17:18:02.324 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Material measurement memory consumption: 0 B (GPU)
    2017-01-05 17:18:02.325 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Materials memory consumption: 269.707 KiB (GPU)
    2017-01-05 17:18:02.506 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Scene processed in 17.921s
    2017-01-05 17:18:02.512 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 84.3755 MiB for frame buffer
    2017-01-05 17:18:02.559 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 1.65625 GiB of work space (2048k active samples in 0.058s)
    2017-01-05 17:18:02.559 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Used for display, optimizing for interactive usage (performance could be sacrificed)
    2017-01-05 17:18:04.441 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : Allocating 1 layer frame buffer
    2017-01-05 17:18:04.541 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00001 iterations after 19.956s.
    2017-01-05 17:18:06.218 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00002 iterations after 21.633s.
    2017-01-05 17:18:07.931 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00003 iterations after 23.345s.
    2017-01-05 17:18:09.675 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00004 iterations after 25.090s.
    2017-01-05 17:18:11.364 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00005 iterations after 26.794s.
    2017-01-05 17:18:13.093 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00006 iterations after 28.508s.
    2017-01-05 17:18:14.835 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00007 iterations after 30.265s.
    2017-01-05 17:18:16.537 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00008 iterations after 31.951s.
    2017-01-05 17:18:18.273 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00009 iterations after 33.687s.
    2017-01-05 17:18:20.050 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00010 iterations after 35.465s.
    2017-01-05 17:18:21.738 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00011 iterations after 37.153s.
    2017-01-05 17:18:25.127 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00013 iterations after 40.542s.
    2017-01-05 17:18:28.472 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00015 iterations after 43.887s.
    2017-01-05 17:18:31.880 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00017 iterations after 47.294s.
    2017-01-05 17:18:35.210 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00019 iterations after 50.625s.
    2017-01-05 17:18:40.301 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00022 iterations after 55.724s.
    2017-01-05 17:18:45.302 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00025 iterations after 60.716s.
    2017-01-05 17:18:50.358 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00028 iterations after 65.779s.
    2017-01-05 17:18:55.514 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00031 iterations after 70.928s.
    2017-01-05 17:19:02.080 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00035 iterations after 77.495s.
    2017-01-05 17:19:08.739 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00039 iterations after 84.154s.
    2017-01-05 17:19:17.011 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00044 iterations after 92.426s.
    2017-01-05 17:19:25.301 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00049 iterations after 100.716s.
    2017-01-05 17:19:35.224 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00055 iterations after 110.639s.
    2017-01-05 17:19:45.325 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00061 iterations after 120.740s.
    2017-01-05 17:19:56.822 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00068 iterations after 132.243s.
    2017-01-05 17:20:08.407 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00075 iterations after 143.822s.
    2017-01-05 17:20:21.727 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00083 iterations after 157.142s.
    2017-01-05 17:20:36.771 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00092 iterations after 172.186s.
    2017-01-05 17:20:53.273 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00102 iterations after 188.689s.
    2017-01-05 17:21:11.546 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00113 iterations after 206.961s.
    2017-01-05 17:21:31.548 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00125 iterations after 226.963s.
    2017-01-05 17:21:52.956 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00138 iterations after 248.371s.

  • pkappeteinpkappetein Posts: 506

    tried running that octane benchmark, but it's telling me that there is no supported GPU found

     

  • mcorrmcorr Posts: 1,104

    Want to upgrade to 4.9.3 and am wondering if my Nvidia 660ti will run on it with the drivers I've been using for 4.9 on my MAC (not Windows) ... or if absolutely must install new drivers, or a new CUDA version, some of which (like the newest, I think) only run on OS 10.10, or 10.11 and higher, which would be a problem because I am running on 10.8.3.

  • AlienRendersAlienRenders Posts: 794

    I find that it is faster, but beware the convergence. 95% convergence is rather grainy now compared to the previous version. I'm now upping the convergence to 99% where I would never do this on the older version.

     

  • pkappeteinpkappetein Posts: 506
    edited January 2017

    I did the program from here with the test scene: http://www.daz3d.com/forums/discussion/53771/iray-starter-scene-post-your-benchmarks/p14

    and got this

     

    Did the example file and these are my results

    Asus Laptop Windows 10  with 64 Gb.   Nvidia 1070 with 8 Gb card

    GPU
    Total Rendering Time: 4 minutes 57.58 seconds

    GPU+OptiX (Whatever that it)
    Total Rendering Time: 3 minutes 2.40 seconds

    No idea if that's good, and no idea what the OptiX is

     

    Post edited by pkappetein on
  • nonesuch00nonesuch00 Posts: 18,714
    pkappetein said:

    ok installed the latest drivers and started a scene, and waited for a bit  after 5 min. it was still 0%  but this is what's showing

     

    2017-01-05 17:17:39.977 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating geometry.
    2017-01-05 17:17:44.429 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using built-in ray tracing (1.0.0).
    2017-01-05 17:17:44.429 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Importing geometry.
    2017-01-05 17:17:44.478 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Geometry import (1 object with 273k triangles, 1 instance yielding 273k triangles) took 0.060047
    2017-01-05 17:17:44.478 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating materials.
    2017-01-05 17:17:44.494 Iray INFO - module:category(MATCNV:RENDER):   1.0   MATCNV rend info : found 383 textures, 0 lambdas (0 unique)
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Emitter geometry import (5 light sources with 1644 triangles, 1 instance) took 0.00s
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating environment.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lens.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating lights.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating object flags.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating caustic portals.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Updating decals.
    2017-01-05 17:17:44.509 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Allocating 1 layer frame buffer
    2017-01-05 17:17:44.532 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Using batch scheduling, architectural sampler disabled, caustic sampler disabled
    2017-01-05 17:17:44.532 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.
    2017-01-05 17:17:44.579 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 1 device(s):
    2017-01-05 17:17:44.579 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CUDA device 0 (GeForce GTX 1070)
    2017-01-05 17:17:44.579 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...
    2017-01-05 17:17:44.579 Iray VERBOSE - module:category(IRAY:RENDER):   1.3   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
    2017-01-05 17:17:44.874 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.7   IRAY   rend warn : RTKernel: please check the input geometry (degenerated/inefficient RT hierarchy)
    2017-01-05 17:17:44.880 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Geometry memory consumption: 7.91974 MiB (device 0), 0 B (host)
    2017-01-05 17:18:01.892 Iray INFO - module:category(IRAY:RENDER):   1.7   IRAY   rend info : Initializing light hierarchy.
    2017-01-05 17:18:01.892 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Texture memory consumption: 4.56567 GiB (device 0)
    2017-01-05 17:18:01.923 Iray INFO - module:category(IRAY:RENDER):   1.7   IRAY   rend info : Light hierarchy initialization took 0.03s
    2017-01-05 17:18:01.923 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Lights memory consumption: 284.957 KiB (device 0)
    2017-01-05 17:18:02.324 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Material measurement memory consumption: 0 B (GPU)
    2017-01-05 17:18:02.325 Iray VERBOSE - module:category(IRAY:RENDER):   1.7   IRAY   rend stat : Materials memory consumption: 269.707 KiB (GPU)
    2017-01-05 17:18:02.506 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Scene processed in 17.921s
    2017-01-05 17:18:02.512 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 84.3755 MiB for frame buffer
    2017-01-05 17:18:02.559 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Allocated 1.65625 GiB of work space (2048k active samples in 0.058s)
    2017-01-05 17:18:02.559 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : CUDA device 0 (GeForce GTX 1070): Used for display, optimizing for interactive usage (performance could be sacrificed)
    2017-01-05 17:18:04.441 Iray INFO - module:category(IRAY:RENDER):   1.3   IRAY   rend info : Allocating 1 layer frame buffer
    2017-01-05 17:18:04.541 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00001 iterations after 19.956s.
    2017-01-05 17:18:06.218 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00002 iterations after 21.633s.
    2017-01-05 17:18:07.931 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00003 iterations after 23.345s.
    2017-01-05 17:18:09.675 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00004 iterations after 25.090s.
    2017-01-05 17:18:11.364 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00005 iterations after 26.794s.
    2017-01-05 17:18:13.093 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00006 iterations after 28.508s.
    2017-01-05 17:18:14.835 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00007 iterations after 30.265s.
    2017-01-05 17:18:16.537 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00008 iterations after 31.951s.
    2017-01-05 17:18:18.273 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00009 iterations after 33.687s.
    2017-01-05 17:18:20.050 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00010 iterations after 35.465s.
    2017-01-05 17:18:21.738 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00011 iterations after 37.153s.
    2017-01-05 17:18:25.127 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00013 iterations after 40.542s.
    2017-01-05 17:18:28.472 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00015 iterations after 43.887s.
    2017-01-05 17:18:31.880 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00017 iterations after 47.294s.
    2017-01-05 17:18:35.210 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00019 iterations after 50.625s.
    2017-01-05 17:18:40.301 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00022 iterations after 55.724s.
    2017-01-05 17:18:45.302 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00025 iterations after 60.716s.
    2017-01-05 17:18:50.358 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00028 iterations after 65.779s.
    2017-01-05 17:18:55.514 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00031 iterations after 70.928s.
    2017-01-05 17:19:02.080 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00035 iterations after 77.495s.
    2017-01-05 17:19:08.739 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00039 iterations after 84.154s.
    2017-01-05 17:19:17.011 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00044 iterations after 92.426s.
    2017-01-05 17:19:25.301 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00049 iterations after 100.716s.
    2017-01-05 17:19:35.224 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00055 iterations after 110.639s.
    2017-01-05 17:19:45.325 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00061 iterations after 120.740s.
    2017-01-05 17:19:56.822 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00068 iterations after 132.243s.
    2017-01-05 17:20:08.407 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00075 iterations after 143.822s.
    2017-01-05 17:20:21.727 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00083 iterations after 157.142s.
    2017-01-05 17:20:36.771 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00092 iterations after 172.186s.
    2017-01-05 17:20:53.273 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00102 iterations after 188.689s.
    2017-01-05 17:21:11.546 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00113 iterations after 206.961s.
    2017-01-05 17:21:31.548 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00125 iterations after 226.963s.
    2017-01-05 17:21:52.956 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Received update to 00138 iterations after 248.371s.

    I have only an integrated Intel GPU and when I see messages like those I know D|S has gotten into a funk and you should save your scene, exit D|S, and restart D|S, and restart your render and then it should work (usually).

  • pkappeteinpkappetein Posts: 506

    Hmm tried another scene, and it failed, and switched to CPU mode ... Why ???

    it said out of memory...    will it render CPU  if the scene is too big ??  thought it will do piece by piece..
    if I have scenes more then 8 Gb, then your pretty much  SOL...   wth.

    2017-01-05 20:16:48.354 Iray VERBOSE - module:category(IRAY:RENDER):   1.5   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
    2017-01-05 20:16:48.603 Iray VERBOSE - module:category(IRAY:RENDER):   1.9   IRAY   rend stat : Geometry memory consumption: 1.18875 GiB (device 0), 0 B (host)
    2017-01-05 20:16:48.887 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.9   IRAY   rend error: OptiX Prime error (Device rtpModelUpdate TL): Unknown error (Function "_rtpModelUpdate" caught exception: Encountered a CUDA error: cudaMalloc(&ptr, size) returned (2): out of memory, [15466617])
    2017-01-05 20:16:48.887 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.5   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): Scene setup failed
    2017-01-05 20:16:48.887 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.5   IRAY   rend error: CUDA device 0 (GeForce GTX 1070): Device failed while rendering
    2017-01-05 20:16:48.903 WARNING: dzneuraymgr.cpp(307): Iray WARNING - module:category(IRAY:RENDER):   1.5   IRAY   rend warn : All available GPUs failed.
    2017-01-05 20:16:48.903 Iray INFO - module:category(IRAY:RENDER):   1.5   IRAY   rend info : Falling back to CPU rendering.

  • mjc1016mjc1016 Posts: 15,001

    No, if the scene can't fit in the card's memory then it drops to CPU mode...it's always been that way.

    But looking at that log snippet...nearly 2 GB in just geometry...yeah, there's a good chance it's going to be much larger than 8 GB, once you add in textures.

  • marblemarble Posts: 7,500

    Try GPU-Z (google if you don't have it - it is a free utility). It will tell you if you are exceeding your VRAM and also whether your GPU is processing the data or not.

  • kyoto kidkyoto kid Posts: 41,838
    edited January 2017

    ..OK a bit confused here.

    Looked at the DIM and in the Installed tab it shows the 4.9 General Release Build is installed, however I never installed the the 4.9 General Release Build, only the a couple of the betas so I could continue running 4.8.0.59 in parallel without overwriting it as there were turned out to be some issues with the 4.9 General release.  The latest beta I have is 4.9.3.117. 

    So why then is the DIM showing 4.9 as the general build and 4.9.3.166 as the beta in the Installed tab instead of 4.0.59 and 4.9.3.117 respectively which are the actual versions installed?

    Also in performing a comparative render test for CPU mode, it would offer better analysis if the same scene were rendered on the same system under the same OS in say 4.8 and then the 4.9.3.166 beta (also I thought a beta and general release couldn't share the same version number, it would have to be something like .166 for the Beta and .167 for the General). 

    Yeah, I'm a bit skeptical, especially when updating means overwriting the existing version.

    Post edited by kyoto kid on
  • TooncesToonces Posts: 919

    I noticed you had this error in your log file "OptiX Prime error."

    I see that too when I do animations or multiple back-to-back renders. I think it's a memory leak in the software. The solution for me is to restart Daz (or flush memory) and disable OptiX Prime, as advised in this thread:

    http://www.daz3d.com/forums/discussion/110626/iray-intermittently-stops-utilizing-video-card-s

    Note if I'm doing low memory renders or single renders separated by time, I usually keep Optix enabled since it's faster.

     

  • pkappeteinpkappetein Posts: 506

    Thank you..   Let me try that one out.

     

  • pkappeteinpkappetein Posts: 506

    that worked...  rendering took 18 min, vs 45 and 15% done  .

    Guess I know now for next time

  • marblemarble Posts: 7,500
    havsm said:

    I noticed you had this error in your log file "OptiX Prime error."

    I see that too when I do animations or multiple back-to-back renders. I think it's a memory leak in the software. The solution for me is to restart Daz (or flush memory) and disable OptiX Prime, as advised in this thread:

    http://www.daz3d.com/forums/discussion/110626/iray-intermittently-stops-utilizing-video-card-s

    Note if I'm doing low memory renders or single renders separated by time, I usually keep Optix enabled since it's faster.

     

    Yeah, now you mention it, I had that too. Somehow the memory doesn't clear between renders. Or maybe it was not closing render windows which gradually used up all the VRAM? On the other hand, it is useful to have the Iray preview on in the little sidebar viewport (can't remember what it is called as I don't have my PC with me). Something to do with the pre-loading of the scene into VRAM which takes some time but only needs to be done once as long as you don't exit the scene.

    I wish I had my computer so I could remind myself but I remember saving some time that way.

  • mjc1016mjc1016 Posts: 15,001

    As long as the render window is still open, the scene will be held in memory...because you can RESUME the render. 

    When animating, render directly to a file.

  • HavosHavos Posts: 5,573

    I remember with the previous version, if you exceeded the GPU VRAM and it dropped into CPU, all subsequent renders were CPU only, even if you modified the scene. When I loaded a new scene this was still the case. Only restarting DS would again allow it to use the GPU for rendering. I have not yet seen if the newer version has fixed this.

  • MusicplayerMusicplayer Posts: 515

    I am still using Studio 4.8 and have always noticed that using the preview window in Iray mode uses memory that it then holds, and so is not there for the final render. To get over this I would run a memory clear utility before starting my render. Other times I would save the scene when render ready, and then restart Daz Studio. I did raise the point a couple of times in the beta forum when 4.8 was being tested. I was sure there was a memory leak, but my concerns were never answered. If this was never fixed, it could possibly still be a problem. Just a thought.

    smiley

  • ChoholeChohole Posts: 33,604
    kyoto kid said:

    ..OK a bit confused here.

    Looked at the DIM and in the Installed tab it shows the 4.9 General Release Build is installed, however I never installed the the 4.9 General Release Build, only the a couple of the betas so I could continue running 4.8.0.59 in parallel without overwriting it as there were turned out to be some issues with the 4.9 General release.  The latest beta I have is 4.9.3.117. 

    So why then is the DIM showing 4.9 as the general build and 4.9.3.166 as the beta in the Installed tab instead of 4.0.59 and 4.9.3.117 respectively which are the actual versions installed?

    Also in performing a comparative render test for CPU mode, it would offer better analysis if the same scene were rendered on the same system under the same OS in say 4.8 and then the 4.9.3.166 beta (also I thought a beta and general release couldn't share the same version number, it would have to be something like .166 for the Beta and .167 for the General). 

    Yeah, I'm a bit skeptical, especially when updating means overwriting the existing version.

    There is only one name for a given package in Install Manager. When connected, the name of the package is coming from the server. When working offline, the name of the package comes from the data on the local machine.
     

  • BendinggrassBendinggrass Posts: 1,380

    So to sumarize for my understanding, there is an update for DS4.9, and it includes a new iRay render engine which can now use the new Pascal video cards.

    Is that correct?

    Thanks.

     

Sign In or Register to comment.