Daz Studio Pro BETA - version 4.9.3.166! Release Candidate 5 (*UPDATED*)

1171820222329

Comments

  • Ki-JenKi-Jen Posts: 64
    Yes :)  You would just need to specify your current content directories in Content Directory Manager if you are not using the deault ones.

    Got it - I installed the Beta last night and had a play around with it. It actually seemed to pick up my current directories without me having to point it in the right direction.

    Render times are great now, though; testing small ~15 minute renders with the GTX980 (I don't do the more hardcore "entire weekend" renders :P), the difference is anywhere from 5 minutes off to cut in half. Longer renders (1hr+) with multiple figures are anywhere from 15% to 40% chopped off the total time. Great stuff!

    I'm using the same combination of 1080 and 980 and have similar results. About 40% speedup. There's a trap, though. My 980 has less memory (3 GB) compared to the 1080 (6 GB). I rendered complex szenes and got longer render times, as expected. I checked the log and the reason was, that the 980 wasn't used at all, because the scene needs more than the 3 GB memory, the 980 has.

  • kyoto kidkyoto kid Posts: 41,213
    edited November 2016

    ..the 1080 has 8 GB and the 980 4 GB.  Unless you are running in Windows 10 which reserves a portion of GPU VRAM.

    Post edited by kyoto kid on
  • nicsttnicstt Posts: 11,715

    It's software, it takes as long as it takes, and it will always have bugs. The nature of the beast.

  • Ki-JenKi-Jen Posts: 64
    edited November 2016
    kyoto kid said:

    ..the 1080 has 8 GB and the 980 4 GB.  Unless you are running in Windows 10 which reserves a portion of GPU VRAM.

    You are right. It's 8 and 4 GB. This is, what the Studio log says (using Windows 7, not that smartphone OS called Windows 10 smiley):

    2016-11-17 19:14:35.981 NVidia Iray GPUs:
    2016-11-17 19:14:35.981     GPU: 1 - GeForce GTX 1080
    2016-11-17 19:14:35.981     Memory Size: 7.9 GB
    2016-11-17 19:14:35.981     Clock Rate: 1885500 KH
    2016-11-17 19:14:35.981     Multi Processor Count: 20
    2016-11-17 19:14:35.981     CUDA Compute Capability: 6.1
    2016-11-17 19:14:35.981     GPU: 2 - GeForce GTX 980
    2016-11-17 19:14:35.981     Memory Size: 3.9 GB
    2016-11-17 19:14:35.981     Clock Rate: 1291000 KH
    2016-11-17 19:14:35.981     Multi Processor Count: 16
    2016-11-17 19:14:35.981     CUDA Compute Capability: 5.2

    Anyway, the 980 has less memory compared to the 1080. Here's a log showing, what happened to me with a larger scene:

    2016-11-17 19:42:46.378 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.4   IRAY   rend error: Unable to allocate 67108864 bytes from 3035136 bytes of available device memory
    2016-11-17 19:42:46.378 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 980): Scene setup failed
    2016-11-17 19:42:46.378 WARNING: dzneuraymgr.cpp(307): Iray ERROR - module:category(IRAY:RENDER):   1.3   IRAY   rend error: CUDA device 1 (GeForce GTX 980): Device failed while rendering

    As a result, the 1080 did the job alone. On the other hand, without the 1080, Iray would fall back to CPU mode. So 1080 alone is still better.

    Post edited by Ki-Jen on
  • MasterstrokeMasterstroke Posts: 2,033
    edited November 2016

    I have this problem with the latest beta: every thing seems to be semi-transperant, no matter what material settings are used and some polygons are desplayed wrong. The cube is the default DS cube with an iray rock mat applied. Rendered with a nvidea 1070 gtx. ------

    after a little bit more investigation it seems like OptixPrime Acceleration is causing this issue especially when using athmospheric effects like DA real world lightning.

    DS19-11-2016_01.jpg
    1162 x 1059 - 368K
    DS19-11-2016_02.jpg
    637 x 1007 - 235K
    DS19-11-2016_03.jpg
    1920 x 1200 - 696K
    Post edited by Masterstroke on
  • I have this problem with the latest beta: every thing seems to be semi-transperant, no matter what material settings are used and some polygons are desplayed wrong. The cube is the default DS cube with an iray rock mat applied. Rendered with a nvidea 1070 gtx. ------

    after a little bit more investigation it seems like OptixPrime Acceleration is causing this issue especially when using athmospheric effects like DA real world lightning.

    Please report his, especially if you can give a recipe to trigger it.

  • joelmarkleejoelmarklee Posts: 19
    edited November 2016
    kyoto kid said:

    ..the 1080 has 8 GB and the 980 4 GB.  Unless you are running in Windows 10 which reserves a portion of GPU VRAM.

    Running on Windows 10, here:

    2016-11-13 21:12:39.838 NVidia Iray GPUs:
    2016-11-13 21:12:39.838     GPU: 1 - GeForce GTX 1070
    2016-11-13 21:12:39.838     Memory Size: 7.9 GB
    2016-11-13 21:12:39.838     Clock Rate: 1683000 KH
    2016-11-13 21:12:39.838     Multi Processor Count: 15
    2016-11-13 21:12:39.838     Cuda Version: 6.1

    Additionally, GPU-X reports only 147 MB of my VRAM to be in use at boot time.  

    Post edited by joelmarklee on
  • hzrhzr Posts: 207

    So, will you continue to only work on iray and your encyption integration or actually improve the workflow tools in the application again at some point? Because I cant see any reason why I should install 4.9 at all. It offers nothing substantial over 4.7 or 4.8 at this point and you have been messing with 4.9 for well over a year by now. This is absolutely frustrating as a user, when there are broken things that have been broken since g3 was released and they do not seem to get any attention from you at all.

  • nicsttnicstt Posts: 11,715
    edited November 2016
    hzr said:

    So, will you continue to only work on iray and your encyption integration or actually improve the workflow tools in the application again at some point? Because I cant see any reason why I should install 4.9 at all. It offers nothing substantial over 4.7 or 4.8 at this point and you have been messing with 4.9 for well over a year by now. This is absolutely frustrating as a user, when there are broken things that have been broken since g3 was released and they do not seem to get any attention from you at all.

    +1

    Although the IRAY improvements are welcome.

    Post edited by nicstt on
  • Was it 4.8 or 4.9 that added the ability to remove deltas from a morph, and to restrict which areas of a mesh are affected by a moprh on importing? It's hard to keep track of what was added when, though the change log will tell you, but there have been feature enhacements beyond the headline features (Iray, then Connect).

  • mjc1016mjc1016 Posts: 15,001

    Was it 4.8 or 4.9 that added the ability to remove deltas from a morph, and to restrict which areas of a mesh are affected by a moprh on importing? It's hard to keep track of what was added when, though the change log will tell you, but there have been feature enhacements beyond the headline features (Iray, then Connect).

    And a bunch of fixes...again, detailed in the changelog.

  • So the Iray Draw view does not work any more.... It just makes daz crash with "Not Responding"... If I untick my GPU in the advanced settings it comes right up. But when enabled it just stops.

  • So the Iray Draw view does not work any more.... It just makes daz crash with "Not Responding"... If I untick my GPU in the advanced settings it comes right up. But when enabled it just stops.

    The latest builds have a higher minimum driver requirement, with luck all you need to do is update the nVidia GPU driver.

  • nonesuch00nonesuch00 Posts: 18,302

    I have when I render a scene where a high light reflection, eg green anodized aluminum (Mech4D 2nd iRay Shader set) scaled up 45 times as a car surface reflect off of characters (sans Top Coat map & Top Coat Weight at 2.0) near the car after several render starts & stops the rendering process will corrupt and the surfaces receiving the reflectioned light will have giant pixelated renders, but only if it's human skin surfaces receiving the reflected light and it happens more often the more shiny the light donating surface reflection is, while the rest of the rendered image will render normally. Seems as if there must be a cache of some sort that isn't getting initialized to null.

  • So the Iray Draw view does not work any more.... It just makes daz crash with "Not Responding"... If I untick my GPU in the advanced settings it comes right up. But when enabled it just stops.

    The latest builds have a higher minimum driver requirement, with luck all you need to do is update the nVidia GPU driver.

    Thats what I thought it was, updated. Still crashes :|

  • mjc1016mjc1016 Posts: 15,001

    So the Iray Draw view does not work any more.... It just makes daz crash with "Not Responding"... If I untick my GPU in the advanced settings it comes right up. But when enabled it just stops.

    The latest builds have a higher minimum driver requirement, with luck all you need to do is update the nVidia GPU driver.

    Thats what I thought it was, updated. Still crashes :|

    What are your specs...system, video card, etc? 

  • joksfreyjoksfrey Posts: 10
    edited November 2016

    I'm sure this is just an amateur mistake and problem, but after updating to the new beta I have completely lost all iray rendering options. Hoping this is an easy fix and I'm just overlooking something very basic... I've updated because I couldn't get the general release to use my gtx 1070 for rendering.

    Post edited by joksfrey on
  • What do you mean "lost all Iray rendering options"?

  • There's no longer an option to interactively render with Iray in the Viewport, also no option to render with Iray in the dropdown menu in Render settings. It's like the engine isn't being recognized. I noticed the problem right after updating to the new beta...

     

  • Click on Help - About Installed Plugins and see if NVIDIA Iray Renderer is listed about halfway down.

  • Yeah, I'm not seeing it. If no one else is having this problem, I wonder what's up with my install. Iray should be integrated into DAZ.

  • It is the 64 bit version of DAZ Studio you are running? Did you have DS running when installing the beta? Uninstall the beta and reinstall, making sure no instance of DS is running.

  • nicsttnicstt Posts: 11,715

    what version of nvidia drivers are you using?

  • I running the 64 bit version and I don't think it was running at the time. Suspecting my problem might be with the way that I installed. Originally I loaded Studio 4.9 from a standalone installer, never had any issues but iray wouldn't use my gpu. I soon realized that I couldn't use my gtx 1070 to render unless I had the beta.

    The problem is the desktop I'm trying to get setup is at a location with very little internet connectivity, hence the standalone installer originally. It doesn't seem like there is a way to manually install the BETA this way, so I copied and pasted all the contents over to the DAZStudio4 directory. That's when the problems started. The beta is 32-bit and even tho I've replaced the transferred folder's contents with the original backup copy I created, still no Iray plugin?

    I'd love to do a fresh install from a standalone installer, will have to find it again...

  • The beta is 32-bit and even tho I've replaced the transferred folder's contents with the original backup copy I created, still no Iray plugin?

    There is no Iray for the 32 bit.

  • That explains it... Thanks for all your help tho

  • I'm having to download my entire DAZ install on a netbook elsewhere.  Install Manager is only bringing up 32-bit everything in the Netbook install manager. I was expecting the Beta build to be 32-bit by definition. What am I missing?

  • Have got it, am just downloading the 64-bit version of everything instead. Geez

  • For anyone that's having issues with the Nvidia GeForce GPUs, in particilar the newer ones 1060, 1080 etc.  Microsoft has a known issue which is corrupting the performance of the cards and in some cases is also rebooting machines without notification. Nvidia have created a fix with their drivers but will only work on the latest build of Windows 10, assuming that Windows is not stuck in a download update fail loop which is also another issue.  I thought my issues were only related to the Daz when my Adobe software also started crashing; I did some research.  It was hard to fault the hardware as everything was built new and up to spec for some major rendering work.    To update an offline machine was a battle and a half especially with constant Windows update fails but it is now running sweet again.  Don't initially blame the hardware or DAZ, issues are more likely to be a Windows 10/Nvidia compatibility issue.

    ​Working well on Windows 10 Pro build 1607, GXT1060 with driver version 21.21.13.7595.  Quick render attached.
     

     

    set photo.jpg
    1920 x 817 - 889K
  • kyoto kidkyoto kid Posts: 41,213

    ..hopefully that is isolated to W10 and not also happening with W7 or 8.1.

    BTW nice pic.  I like the silver skin on the shuttle, very 1950s.

Sign In or Register to comment.