Loading...
> >

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

1…1819212324…29

Comments

  • brunocesarrrrbrunocesarrrr Posts: 50

    I had a strange issue on beta:

    I put this item http://www.daz3d.com/gcop-for-genesis-2-female-s on a genesis 3 female. Everything just fine untill that I tried to change the scale property of the cap. 

    Instead of increasing, the cap start to deform, like I was changing bend, twist or something. I saved the scene, then I opened it on the non-beta Daz Studio, and it worked fine. Everything else, working great. 

    I just installed a Geforce 1070, the driver is 375.95 released on 11/17/2016. Windows 10 with all upgrades.

    Rendering that usually take about an half hour to be done with Geforce 970, are now taking just 10 minutes.

  • bullsheep12_9ad188242dbullsheep12_9ad188242d Posts: 3
    mjc1016 said:
    bullsheep12_9ad188242d said:
    Richard Haseltine said:
    bullsheep12_9ad188242d said:

    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? 

    i5 4690k, GTX 1080, 16g DDR3, Win10 Pro.     It was working well for a while...It still renders just fine. So I don't know. Beta I guess.

  • SimonJMSimonJM Posts: 5,997
    kyoto kid said:

    ..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.

    +1 on that ... my new 'monster' (which was DOA crying) computer is W7 as I was/am not going to touch W10 with a 10' bargepole!  It might go to W8, if I can be botehred to seek out, and buy, a install disk.

  • takezo_3001takezo_3001 Posts: 1,997
    edited November 2016

     

    brunocesarrrr said:

     had a strange issue on beta:

    I put this item http://www.daz3d.com/gcop-for-genesis-2-female-s on a genesis 3 female. Everything just fine untill that I tried to change the scale property of the cap. 

    Instead of increasing, the cap start to deform, like I was changing bend, twist or something. I saved the scene, then I opened it on the non-beta Daz Studio, and it worked fine. Everything else, working great. 

    I just installed a Geforce 1070, the driver is 375.95 released on 11/17/2016. Windows 10 with all upgrades.

    Rendering that usually take about an half hour to be done with Geforce 970, are now taking just 10 minutes.

    Yep, had the same problem, as it's a lot of the conforming hair especially with resized characters as well as the auto-fit issue, not to mention the UI problems as I cannot "Snap" elements into place without setting my system's resolution well past the recommended limits, which you can only do once before having to fire up Daz again!

    Post edited by takezo_3001 on
  • RAMWolffRAMWolff Posts: 10,231

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

  • namffuaknamffuak Posts: 4,176
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    Well - given that the current beta still doesn't recognize older nvdia gpus on Macs, and crashes on older AMD cpus, AND the change log indicates DAZ is trying the 2016.3 Iray beta, which nvdia says should not be used for production -- I think the ball is in nvdia's court and DAZ is just as curious as we are.

  • josephlemons69_4db0991b45josephlemons69_4db0991b45 Posts: 423
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    Really Hoping by Christmas, that would be a nice gift under the tree :D 

  • takezo_3001takezo_3001 Posts: 1,997
    namffuak said:
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    Well - given that the current beta still doesn't recognize older nvdia gpus on Macs, and crashes on older AMD cpus, AND the change log indicates DAZ is trying the 2016.3 Iray beta, which nvdia says should not be used for production -- I think the ball is in nvdia's court and DAZ is just as curious as we are.

    Thanks for that bit of info, guess the ball is in their court then...Still, I'm glad that I'm able to finally use my GPU for use in Iray, as it was actually one of the main reasons for my switch to NVidia over AMD in the first place!

  • PavoPavo Posts: 2
    edited December 2016

    There is a bug with displacement maps in version 4.9.3.128, sometimes they work correctly if you switch to iray in the viewport and sometimes they dont work. It is pretty strange, slight changes of the displacement map values seem to to fix the problem temporarily, until you load the scene again. Perhaps it´s just me, let me know if others ran into problems with displacement maps and the new build.

    Post edited by Pavo on
  • takezo_3001takezo_3001 Posts: 1,997
    Pavo said:

    There is a bug with displacement maps in version 4.9.3.128, sometimes they work correctly if you switch to iray in the viewport and sometimes they dont work. It is pretty strange, slight changes of the displacement map values seem to to fix the problem temporarily, until you load the scene again. Perhaps it´s just me, let me know if others ran into problems with displacement maps and the new build.

    No it's not just you, I'll post some examples in a bit...

     

  • SimonJMSimonJM Posts: 5,997
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    I have my new big, rip-snortin' computer now, so it's ok to reelase the new Daz Studio now, guys ... laugh

  • L'AdairL'Adair Posts: 9,479
    SimonJM said:
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    I have my new big, rip-snortin' computer now, so it's ok to reelase the new Daz Studio now, guys ... laugh

    LOL... get in line!
    wink

    (Announcing my new computer purchase didn't move up the Beta release, with support for Pascal cards, either. But at least it was worth the wait!)

  • SimonJMSimonJM Posts: 5,997
    L'Adair said:
    SimonJM said:
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    I have my new big, rip-snortin' computer now, so it's ok to reelase the new Daz Studio now, guys ... laugh

    LOL... get in line!
    wink

    (Announcing my new computer purchase didn't move up the Beta release, with support for Pascal cards, either. But at least it was worth the wait!)

    *offers popcorn ...* wink

  • PavoPavo Posts: 2
    takezo_3001 said:

    No it's not just you, I'll post some examples in a bit...

     

    Okay, I am going to use an older release then. Did not see it at first, but on page 18 people are referring to this problem also. Seems to be a major bug because I also had problems with diffuse maps, I guess something is messing with the map settings.

  • RAMWolffRAMWolff Posts: 10,231
    SimonJM said:
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    I have my new big, rip-snortin' computer now, so it's ok to reelase the new Daz Studio now, guys ... laugh

    Yea, I've ordered mine, it's in the CyberPower pipe line.  I just wanted to make sure can order it during the Black Friday - Cyber Monday sales cycle to get a discount and free shipping.  Did that so until DS is updated to a general release they can take their time getting my new 'puter ready. 

    Save

  • MalawolfMalawolf Posts: 40

    Looks like Terradome 3 is not working in the beta.  Can see it when loaded but not rendering.  Fix it in After Effects :)

  • DoctorJellybeanDoctorJellybean Posts: 8,662
    Malawolf said:

    Looks like Terradome 3 is not working in the beta.  Can see it when loaded but not rendering.  Fix it in After Effects :)

    The base itself, or an add-on?

  • Richard HaseltineRichard Haseltine Posts: 102,472
    Malawolf said:

    Looks like Terradome 3 is not working in the beta.  Can see it when loaded but not rendering.  Fix it in After Effects :)

    Make sure you have the latest version of Terradome 3, it was updated fairly recently and that update is needed.

  • SimonJMSimonJM Posts: 5,997
    RAMWolff said:
    SimonJM said:
    RAMWolff said:

    Hey guys, coming up on 6 months for this newest release.  Any date yet when your going to wrap this puppy up?

    I have my new big, rip-snortin' computer now, so it's ok to reelase the new Daz Studio now, guys ... laugh

    Yea, I've ordered mine, it's in the CyberPower pipe line.  I just wanted to make sure can order it during the Black Friday - Cyber Monday sales cycle to get a discount and free shipping.  Did that so until DS is updated to a general release they can take their time getting my new 'puter ready. 

    Save

    I even sent it back as not working on arrival to drag out the time before Pascal cards are supportd in the main release, buy the very good guys fixed whatever had wiggled loose during transport and sent it back! ;)

  • alexhcowleyalexhcowley Posts: 2,392

    I've just started rendering on an Nvidia 1080, running under 4.9.3.128 and Windows 8.1.  When I select Optix prime accelleration, the render drops to CPU only.  When I deselect Optix prime, it renders on my 1080 quite happily.  I vaguely recall seeing this mentioned somewhere but I can't find it.  Is this an official problem?

    Cheers,

    Alex.

  • SimonJMSimonJM Posts: 5,997
    alexhcowley said:

    I've just started rendering on an Nvidia 1080, running under 4.9.3.128 and Windows 8.1.  When I select Optix prime accelleration, the render drops to CPU only.  When I deselect Optix prime, it renders on my 1080 quite happily.  I vaguely recall seeing this mentioned somewhere but I can't find it.  Is this an official problem?

    Cheers,

    Alex.

    Like you I recall there being an issue with Iray and CUDA 8 and Optix.  A websdearch using "site:daz3d.com optix 1080£ might find it.

  • TottallouTottallou Posts: 555
    SimonJM said:
    alexhcowley said:

    I've just started rendering on an Nvidia 1080, running under 4.9.3.128 and Windows 8.1.  When I select Optix prime accelleration, the render drops to CPU only.  When I deselect Optix prime, it renders on my 1080 quite happily.  I vaguely recall seeing this mentioned somewhere but I can't find it.  Is this an official problem?

    Cheers,

    Alex.

    Like you I recall there being an issue with Iray and CUDA 8 and Optix.  A websdearch using "site:daz3d.com optix 1080£ might find it.

    I have a GTX 1080 Windows 10 & Optix enabled works just fine & is actually slightly faster than leaving it unchecked.

    It does use a little more GPU memory than leaving it unticked so I guess if you had a huge scene it could cause it to drop to CPU

  • alexhcowleyalexhcowley Posts: 2,392
    Tottallou said:
    SimonJM said:
    alexhcowley said:

    I've just started rendering on an Nvidia 1080, running under 4.9.3.128 and Windows 8.1.  When I select Optix prime accelleration, the render drops to CPU only.  When I deselect Optix prime, it renders on my 1080 quite happily.  I vaguely recall seeing this mentioned somewhere but I can't find it.  Is this an official problem?

    Cheers,

    Alex.

    Like you I recall there being an issue with Iray and CUDA 8 and Optix.  A websdearch using "site:daz3d.com optix 1080£ might find it.

    I have a GTX 1080 Windows 10 & Optix enabled works just fine & is actually slightly faster than leaving it unchecked.

    It does use a little more GPU memory than leaving it unticked so I guess if you had a huge scene it could cause it to drop to CPU

    Thanks, I'll try a smaller scene and see what happens.

    Cheers,

    Alex.

  • alexhcowleyalexhcowley Posts: 2,392

    Another problem, this one is really odd.  I created some scenes on Sunday and saved them. I rendered three of the scenes today with no problems, using Draagonstorm's batch renderer.  When I tried to run a fourth off the render tab, the render ended after only a few seconds and displayed a plain black render.  It makes no difference whether I render to screen or to file. 

    Checking the log file, I get the following contradictory error messsages:

    2016-52-05 18:52:33.695 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2016-52-05 18:52:33.695 Iray Render error: Invalid parameters (NULL pointer).
    2016-52-05 18:52:35.055 Saved image: C:\Users\Alex\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
    2016-52-05 18:52:35.367 Finished Rendering
    2016-52-05 18:52:35.398 Total Rendering Time: 31.18 seconds

    Can anyone cast any light on why the same scene file renders under Draagonstorm's batch renderer but throws a tantrum when rendered directly?  The advanced tab shows a Geforce GTX 1080 selected. I've tried rendering older scenes and the same thing happens.

    Thanks,

    Alex.

     

     

     

    txt
    txt
    Hemlock Folly Render Log.txt
    309K
  • TottallouTottallou Posts: 555
    alexhcowley said:

    Another problem, this one is really odd.  I created some scenes on Sunday and saved them. I rendered three of the scenes today with no problems, using Draagonstorm's batch renderer.  When I tried to run a fourth off the render tab, the render ended after only a few seconds and displayed a plain black render.  It makes no difference whether I render to screen or to file. 

    Checking the log file, I get the following contradictory error messsages:

    2016-52-05 18:52:33.695 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2016-52-05 18:52:33.695 Iray Render error: Invalid parameters (NULL pointer).
    2016-52-05 18:52:35.055 Saved image: C:\Users\Alex\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
    2016-52-05 18:52:35.367 Finished Rendering
    2016-52-05 18:52:35.398 Total Rendering Time: 31.18 seconds

    Can anyone cast any light on why the same scene file renders under Draagonstorm's batch renderer but throws a tantrum when rendered directly?  The advanced tab shows a Geforce GTX 1080 selected. I've tried rendering older scenes and the same thing happens.

    Thanks,

    Alex.

     

     

     

    Are you certain this render is being done in the Beta Version?

    What you describe & the message on your log is the one I would get if I try to render on the 1080 in the normal build

     2016-44-05 18:44:53.226 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : GPU 1 (GeForce GTX 1080) with CUDA compute capability 6.1 cannot be used by iray.

  • alexhcowleyalexhcowley Posts: 2,392
    Tottallou said:
    alexhcowley said:

    Another problem, this one is really odd.  I created some scenes on Sunday and saved them. I rendered three of the scenes today with no problems, using Draagonstorm's batch renderer.  When I tried to run a fourth off the render tab, the render ended after only a few seconds and displayed a plain black render.  It makes no difference whether I render to screen or to file. 

    Checking the log file, I get the following contradictory error messsages:

    2016-52-05 18:52:33.695 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
    2016-52-05 18:52:33.695 Iray Render error: Invalid parameters (NULL pointer).
    2016-52-05 18:52:35.055 Saved image: C:\Users\Alex\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
    2016-52-05 18:52:35.367 Finished Rendering
    2016-52-05 18:52:35.398 Total Rendering Time: 31.18 seconds

    Can anyone cast any light on why the same scene file renders under Draagonstorm's batch renderer but throws a tantrum when rendered directly?  The advanced tab shows a Geforce GTX 1080 selected. I've tried rendering older scenes and the same thing happens.

    Thanks,

    Alex.

     

     

     

    Are you certain this render is being done in the Beta Version?

    What you describe & the message on your log is the one I would get if I try to render on the 1080 in the normal build

     2016-44-05 18:44:53.226 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRAY:RENDER):   1.0   IRAY   rend warn : GPU 1 (GeForce GTX 1080) with CUDA compute capability 6.1 cannot be used by iray.

    Oops! You're absolutely right.  I loaded the duf scene file by clicking on it within Windows Explorer.  After the proverbial long, hard day at the office, I forgot that Windows would load 4.9.2 instead of 4.9.3 Beta.

    Cheers,

    Alex.

  • RodrakRodrak Posts: 81

    We are getting closer... (from change log for version 4.9.3.151):

    Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

  • josephlemons69_4db0991b45josephlemons69_4db0991b45 Posts: 423
    Rodrak said:

    We are getting closer... (from change log for version 4.9.3.151):

    Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

    Does this mean we are close to Release??

  • mjc1016mjc1016 Posts: 15,001
    josephlemons69_4db0991b45 said:
    Rodrak said:

    We are getting closer... (from change log for version 4.9.3.151):

    Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

    Does this mean we are close to Release??

    Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

  • josephlemons69_4db0991b45josephlemons69_4db0991b45 Posts: 423
    mjc1016 said:
    josephlemons69_4db0991b45 said:
    Rodrak said:

    We are getting closer... (from change log for version 4.9.3.151):

    Update to NVIDIA Iray 2016.3 Release Candidate (278300.4305); addresses the AMD SSSE3 ILLEGAL_INSTRUCTION crash; enables support for OS X compute capabilities (still has a dependency on CUDA/driver)

    Does this mean we are close to Release??

    Nope...but maybe closer to another Beta release.  Going from past experience, it will be a couple of weeks, yet...

    Is 4.9 the last release before 5.0?

Sign In or Register to comment.