Loading...
> >

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

1…910121415…29

Comments

  • kitakoredazkitakoredaz Posts: 3,526

    I nowdays really need to cut off or hide scene poligons which out of camera frame,,

    I got answer from dev team, about interrective mode, thanks^^ .  he suggested if the scene  above my video card RAM, (about my case almost 6GB)

    iray view port may clash often. (though I can render by CPU without prolbem,, then actualy I seems just render by only CPU about these scene,,)

     

    the scene only consist of one Sifi enviroment product,, , and only  two Actor,,   I just set those two in one corner,,, then not think this scene used so many memory,,

     

    and I already have hidden  many part by scene node.. after all, I needed to  tweak geometry editor, then make new selection setting,

    and hide many poligons ,, it seems reduce scene size drastically, then I could use iray view again.. (blend mode finaly wroked too)

    One request is,, when I save scene,, please it keep those hidden setting about geometry editor,, though it keep my new selection group, I almost lost all my work to hidden poligons of the scene.

  • namffuaknamffuak Posts: 4,176
    L'Adair said:
    DoctorJellybean said:

    I installed 375.63 today. It appears to be good.

    namffuak said:
    L'Adair said:
    rbtwhiz said:
    Iray 2016.2, build 272800.6312

    Added and Changed Features

    • General
      • Iray now ships with and is using CUDA 8.0 final. Please note that this requires at least NVIDIA driver 367. It is recommended to use NVIDIA driver 372.XX.

    I'm on the Nvidia site now. Using the option to manually find the drivers for my product, I end up on a page for driver version 375.63, (which includes support for the 1050 cards.) I was able to find 372.54 and 372.70 using their site search funtion. Is v375.63 okay, or should I download one of the v372 drivers?

    For anyone else looking, here are the links:

    Common sense would suggest 375 will be fine. But ya' never know...

    I put 375.63 on my laptop today and it seems to be ok; my main system is running 372.54 with no issues.

    Thank you, both.

    Once upon a time, my DSL connection was considered fast. Tech has improved considerably, but Qwest doesn't seem to think the second largest city in Oregon is big enough to upgrade the equipment. And I'm so not a fan of either cable company available but I may have to break down and switch... 1.5MB is just too slow!
    crying

    Needless to say, I really don't want to have to download more than one driver to find the right one, if I don't have to.

    Would you believe - I'm jealous? The laptop is used to drag files back from wifi hotspots. I'm posting this from home - on a 31.2 Kbit per second dial-up. :-(

  • CrescentCrescent Posts: 329
    RobotHeadArt said:
    namffuak said:
    RobotHeadArt said:
    franz_acker said:
    DoctorJellybean said:
    franz_acker said:

    It also seems I can't change the rendering resolution (nor the aspect ratio)

    You need to change the Dimension Preset from Active Viewport to Custom to enter your own values.

    did it, no change

    I appear to have the same problem.  Change the the ratio, it always renders as if I had Active Viewport selected.

    Also, closing out DS and relaunching it resets the render settings to use Active Viewport, whereas before it would save the ratio and size and restore it on launching.

    I'm not seeing this - do you have a setting on the camera that is overriding the render settings?

    I've run custom, 16 by 9, golden ratio, and square and all have obeyed my pixel size settings within the shape constraints.

    I had been trying to render through Perspective so no camera constraints.  I tried creating a camera, setting it to local dimensions, looked through the camera, render... and still renders as if Active Viewport is selected.  Iray preview in the Viewport does render the correct aspect ratio and inside the Aspect Frame.

    I'm having the same issue with rendering.  It will not let me render any larger than the active viewport, even if I render to disk. I've toggled all sorts of settings, trying to track down the problem.  

  • rbtwhizrbtwhiz Posts: 2,287
    edited October 2016

    It's being looked into, literally, at this very moment.

    -Rob

    Post edited by rbtwhiz on
  • kitakoredazkitakoredaz Posts: 3,526

    Yours who can not render with custom size,  do actually set Camera tab, and set the camera (which you render image)  as Use local dimension on? 

    and if you set multi view port  (eg left= camera1, right = perspective,,) you must need the view window set active (yellow highlighted) untill render.

    DS just render active viewport with the setting of view.  just ask to confirm,,, and may better if it is depend on windows version or mac version,

    I use windows 64 bit ver (this public beta) to test it.  hope if it may help.

    renderaspect.PNG
    1241 x 906 - 761K
  • CrescentCrescent Posts: 329

    I've tried renders with Use Local Dimension On as well as Off, with the Perspective Camera and with a newly created camera, etc.  It works just fine in the public, production version of DS but not with the new Beta.

  • kitakoredazkitakoredaz Posts: 3,526
    edited October 2016

    I see,,,  actually I get same problem about new camera. with new scene.  I have rendered  with only saved scene, then when I tweak camera dimension (already located in the saved scene),it seems worked..   

    but about new camera with new scene,, it just keep active view port Dimension and ratio,, size.   thank you teach  me the problem,, ( I may feel better to wait  daz up-date beta,, ,,)

    Post edited by kitakoredaz on
  • nakamuram002nakamuram002 Posts: 793

    Works with my GTX 1070!!  About 4 times faster than my GTX 660.  I think I'm going to like the new DS UI.

  • hphoenixhphoenix Posts: 1,335
    edited October 2016

    Well, at least you all have a viewport.  Mine's gone black (except for a tiny rectangle at the top left corner of the viewport).  That little rectangle of gray shows movement and the ground plane grid lines, but the rest of the viewport is black.  Changing layout, closing/reopening the viewport, changing render styles, closing scene and adding just a G3F base figure......nothing helps.  Restarted computer multiple times.  Still the same.

    (Core i7, ASUS Maximus Hero Alpha motherboard, 32GB DDR4-3000, ASUS 1080GTX STRIX GPU, Win7Pro 64bit, 4k display over HDMI @ 60Hz)

    I updated to the latest nVidia driver for my 1080 (375.63 I believe?) and all seems well otherwise.  Iray renders fine (and pretty quickly.)  Just that the viewport seems buggy.

    Late here, so I'll try downgrading the driver to a 372.xx version tomorrow evening.

     

    *sighs*  At least I was able to get a first 1080 benchmark out of Iray......(2m40s for the test scene in the other thread)

     

    Post edited by hphoenix on
  • kitakoredazkitakoredaz Posts: 3,526

    I now try to re-produce problem which I saw once,

     then I feel,, the fixed view port ratio  and size about rendered image  seems only happen when I set render setting>gloval as "active viewport" once.

     

    if set it as "active viewport" ,, camera located scene seems keep the active view port setting, not follow eacy local setting even though I set "Use local dimension on"

    and  I retrun render setting as "custom",, but  ds render still keep  the active viewport ratio and size. not follow each local camera setting. 

    but,,, set render setting as "custom", and load new camera,, it seems return individual local setting render,, it is complex though,,,

  • AndySAndyS Posts: 1,438
    edited October 2016

    Hi,

    I still have open bug reports pending since now almost one year. The issue was clearly documented by me.

    --> #209594 (as an extention of #200841)

    It was accepted and sent to nVidia.

    My question:
    When will this issue be solved?

    Post edited by AndyS on
  • RobotHeadArtRobotHeadArt Posts: 917
    kitakoredaz said:

    I now try to re-produce problem which I saw once,

     then I feel,, the fixed view port ratio  and size about rendered image  seems only happen when I set render setting>gloval as "active viewport" once.

     

    if set it as "active viewport" ,, camera located scene seems keep the active view port setting, not follow eacy local setting even though I set "Use local dimension on"

    and  I retrun render setting as "custom",, but  ds render still keep  the active viewport ratio and size. not follow each local camera setting. 

    but,,, set render setting as "custom", and load new camera,, it seems return individual local setting render,, it is complex though,,,

    Yes it looks like loading a camera with local dimensions that had been saved using a previous version of DAZ Studio seems to get the render size/aspect ratio to work again.

  • kitakoredazkitakoredaz Posts: 3,526

     good if it worked for you. smiley

    then,,, I can not still detect when the problem happen clear,, , I feel there should be some conditions to reproduce this problem.

    , but I can confirm I actually saw, when I test as yours mentioned with new scene and new camera. 

     my rendered image with camera setting (local) not work and just retricted by current view size when I tweak render setting, but keep camera local.

    but after I saw it, and test again  with new scene,, I can not re-produce,, it as usuall,, though I need not know detail ^^; it somehow cause me feel creepy to use camera with new beta.

    (but I oftenn see wrong illustion about daz studio,,  then not care much any more ^^;  just hope someone who have this prblem camera return as usuall. 

  • OstadanOstadan Posts: 1,128
    DoctorJellybean said:
    Thomas Windar said:

    Does this mean... Pascal is supported?

     

    Yes. You do need the latest NVIDIA drivers as it uses CUDA 8.

    Apparently the latest NVidia driver for Mac OS X won't do the job. 

  • almahiedraalmahiedra Posts: 1,353

    Toony cam pro ID outlines working perfectly now! Thanks again!

  • MasterstrokeMasterstroke Posts: 2,033
    edited October 2016

    Sorry again, I don't know how to get access to this public build. It just doesn't show in DIM 1.10.64. I can only see a "scene builder public build +beta+" (1kb). Found it. Make sure to have "Software" in the Download filters checked too.

    Post edited by Masterstroke on
  • namffuaknamffuak Posts: 4,176
    Masterstroke said:

    Sorry again, I don't know how to get access to this public build. It just doesn't show in DIM 1.10.64. I can only see a "scene builder public build +beta+" (1kb).

    Have you done a public build before? If not - you'll need to 'purchase' it -- sku 12000 in the store, free.

  • Richard HaseltineRichard Haseltine Posts: 102,464
    Ostadan said:
    DoctorJellybean said:
    Thomas Windar said:

    Does this mean... Pascal is supported?

     

    Yes. You do need the latest NVIDIA drivers as it uses CUDA 8.

    Apparently the latest NVidia driver for Mac OS X won't do the job. 

    I thought that for Mac the CUDA drivers were a separate download.

  • josephlemons69_4db0991b45josephlemons69_4db0991b45 Posts: 423
    Richard Haseltine said:
    Ostadan said:
    DoctorJellybean said:
    Thomas Windar said:

    Does this mean... Pascal is supported?

     

    Yes. You do need the latest NVIDIA drivers as it uses CUDA 8.

    Apparently the latest NVidia driver for Mac OS X won't do the job. 

    I thought that for Mac the CUDA drivers were a separate download.

    Have the camera issues in the new beta been fixed and if so do I need to redownload Daz Studio to get the fix or will it update on its own?

  • DoctorJellybeanDoctorJellybean Posts: 8,656
    josephlemons69_4db0991b45 said:
    Have the camera issues in the new beta been fixed and if so do I need to redownload Daz Studio to get the fix or will it update on its own?

    Once there is an update, you'll be notified in DIM. You'll then need to redownload and install.

  • DoctorJellybeanDoctorJellybean Posts: 8,656
    Richard Haseltine said:
    Ostadan said:
    Apparently the latest NVidia driver for Mac OS X won't do the job. 

    I thought that for Mac the CUDA drivers were a separate download.

    I believe this is required for Mac users:

    http://www.nvidia.com/object/macosx-cuda-8.0.46-driver.html

  • BeeMKayBeeMKay Posts: 7,019

    I have a question... do I have to update to CUDA 8.0 to run the Beta? And if I have to upgrade, will my installed version of 4.8 still work?

  • EsemwyEsemwy Posts: 578

    As of the latest driver and CUDA on macOS 10.12.1, GPU rendering is toast. This for both the beta and general release. 

    IRAY rend error: CUDA device 0 (GeForce GTX 980): an illegal instruction was encountered (while de-allocating memory)

    Used to get it occasionally. Now it comes immediately with every render.  

  • BeeMKayBeeMKay Posts: 7,019
    Esemwy said:

    As of the latest driver and CUDA on macOS 10.12.1, GPU rendering is toast. This for both the beta and general release. 

    IRAY rend error: CUDA device 0 (GeForce GTX 980): an illegal instruction was encountered (while de-allocating memory)

    Used to get it occasionally. Now it comes immediately with every render.  

    Ouch! That sounds bad! I hope you can roll back to the previous version of the driver?

  • EsemwyEsemwy Posts: 578
    BeeMKay said:
    Esemwy said:

    As of the latest driver and CUDA on macOS 10.12.1, GPU rendering is toast. This for both the beta and general release. 

    IRAY rend error: CUDA device 0 (GeForce GTX 980): an illegal instruction was encountered (while de-allocating memory)

    Used to get it occasionally. Now it comes immediately with every render.  

    Ouch! That sounds bad! I hope you can roll back to the previous version of the driver?

    Not without a reinstall. Nvidia only has one version of the driver that runs on 10.12.1. I put in a ticket, and I guess I'll play with Reality/Lux until there's a fix. 

  • Trigger_31Trigger_31 Posts: 19

    Ok, Iray crashes now...I am using an GTX 460 1GB VRAM with the latest NVIDIA drivers 375.63. I assume this card is too old now even though it says in the LOG : Your NVIDIA driver supports CUDA version up to 8000; iray requires CUDA version 7000; all is good.

    Rendering...

    Iray VERBOSE - module:category(IRAY:RENDER): 1.2 IRAY rend progr: CUDA device 0 (GeForce GTX 460): Processing scene...

    Iray VERBOSE - module:category(IRAY:RENDER): 1.8 IRAY rend stat : Geometry memory consumption: 13.7055 MiB (device 0), 0 B (host)

    DAZStudio.exe caused ILLEGAL_INSTRUCTION in module "E:\3D\DAZ 3D\DAZStudio4 Public Build\libs\iray\libneuray.dll" at 0033:00000000D3F10728, mi_neuray_factory()+7334328 byte(s)

    OK I see this card is too old and too bad but i am still a bit saddend because IRAY worked really nice in the release version 4.9 even with moderately complex scenes.

     

  • tedharris600tedharris600 Posts: 22
    Crescent said:

    I've tried renders with Use Local Dimension On as well as Off, with the Perspective Camera and with a newly created camera, etc.  It works just fine in the public, production version of DS but not with the new Beta.

    I have the same problem. I am using Nvidia drivers 373.06 and Windows 8.1 64bit.

  • DoctorJellybeanDoctorJellybean Posts: 8,656
    tedharris600 said:
    Crescent said:

    I've tried renders with Use Local Dimension On as well as Off, with the Perspective Camera and with a newly created camera, etc.  It works just fine in the public, production version of DS but not with the new Beta.

    I have the same problem. I am using Nvidia drivers 373.06 and Windows 8.1 64bit.

    See this:

    rbtwhiz said:

    It's being looked into, literally, at this very moment.

    -Rob

     

  • D.RobinsonD.Robinson Posts: 283
    edited October 2016

    I have a crash everytime i try to render with Iray,, or use Iray preview, the crash error is this.

    DAZStudio.exe caused ILLEGAL_INSTRUCTION in module "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\libs\iray\libneuray.dll" at 0033:00000000E11B0728, mi_neuray_factory()+7334328 byte(s)

     

    AMD 965 black edition, EVGA GTX 670, latest nvidia drivers. 16 gigs of ram, Windows 7 Pro

    Previous BETA build worked fine....this just started with latest Beta build so basically i cannot do anything at this point. Thing is i can use the Iray preview and render with just HDRi, but as soon as i put a figure in the scene this happens

    Daniel

    P.S. I dont know if this has anything to do with the crash, but i looked at the log file after i tried to use the Iray view and it says its using Cuda 3.0 My understanding is that it needs at least Cuda 7.0 to work. Its a bad report though because in my properties tab for Nvida devices it clearly says Cuda version 8.0

    Post edited by D.Robinson on
  • mrron2mrron2 Posts: 32
    D.Robinson said:

    I have a crash everytime i try to render with Iray,, or use Iray preview, the crash error is this.

    DAZStudio.exe caused ILLEGAL_INSTRUCTION in module "C:\Program Files\DAZ 3D\DAZStudio4 Public Build\libs\iray\libneuray.dll" at 0033:00000000E11B0728, mi_neuray_factory()+7334328 byte(s)

     

    AMD 965 black edition, EVGA GTX 670, latest nvidia drivers. 16 gigs of ram, Windows 7 Pro

    Previous BETA build worked fine....this just started with latest Beta build so basically i cannot do anything at this point. Thing is i can use the Iray preview and render with just HDRi, but as soon as i put a figure in the scene this happens

    Daniel

    P.S. I dont know if this has anything to do with the crash, but i looked at the log file after i tried to use the Iray view and it says its using Cuda 3.0 My understanding is that it needs at least Cuda 7.0 to work. Its a bad report though because in my properties tab for Nvida devices it clearly says Cuda version 8.0

    Same Problem. I use the 375.63 Driver, wich one use you? Maybe we need to downgrade to or 372.xx

Sign In or Register to comment.