It's been slightly depressing that the change log for the private beta seemed stuck at build number 4.9.3.99... But today I see we are up to 4.9.3.103
Too bad there's no way of knowing when the next Beta version will be released...
Considering that it's a private beta, I think it's nice that we get to see what's being worked on.
I agree.
I still wish I had some idea when to expect the next beta release, hopefully with support for the Pascal based Nvidia cards. (Me and a number of other folks with new Nvidia cards...lol)
It's been slightly depressing that the change log for the private beta seemed stuck at build number 4.9.3.99... But today I see we are up to 4.9.3.103
Too bad there's no way of knowing when the next Beta version will be released...
Considering that it's a private beta, I think it's nice that we get to see what's being worked on.
I agree.
I still wish I had some idea when to expect the next beta release, hopefully with support for the Pascal based Nvidia cards. (Me and a number of other folks with new Nvidia cards...lol)
Well those results will tell me if I need to consider getting one, or not.
I was actually at Nvidia's page contemplating a new Titan, then figured I want to benchmarks, timings from folks here... Not read sales hype.
The web team is working on a number of issues relating to the site and content delivery systems - I imagine that is the issue with downloading DS. I would give it a rest for today and see if the situation is fixed tomorrow.
The web team is working on a number of issues relating to the site and content delivery systems - I imagine that is the issue with downloading DS. I would give it a rest for today and see if the situation is fixed tomorrow.
Thank you very much,
I shall wait, few days maybe.
I can only say you have only been very kind and very helpful.
It's a most wonderful community here, on Daz.
I wish you a wonderful day, good luck and inspiration!
Fixed a crash when attempting to use the “New Shader…” action in the Catalog of the Shader Builder pane
Thankkkkkkkkkkkkkkkkkkkkkssssssssssss!!! DAZ team. I'm waiting for this beauty release.
Made tweaks to Shader Builder UI; work toward consistency with Shader Mixer and ultimately toward fixing the minimum size center dock issue of both panes
Certainly the change log mentioned adding (a beta version of) the 2016.2 SDK.
So will the next beta launch by the end of the month or what because Im getting a new pc for my birthday which has a 1070 in it so I would love to be able to use it in Daz Studio
Certainly the change log mentioned adding (a beta version of) the 2016.2 SDK.
So will the next beta launch by the end of the month or what because Im getting a new pc for my birthday which has a 1070 in it so I would love to be able to use it in Daz Studio
I don't think anyone knows...
I just bought a new computer with a 1080 and though DS isn't using the GPU for renders, it's still very fast. How well/fast your birthday computer will render until Pascal is supported will be dependent on your CPU, so if you have the choice, get as good a CPU as you can afford. I got an i7-6900K Eight-Core 3.20GHz with 20MB Cache and a test render shows the new computer rendering about 5.6 times faster than the old one, an i7-4770 Quad-Core 3.40GHz cpu.
Made tweaks to Shader Builder UI; work toward consistency with Shader Mixer and ultimately toward fixing the minimum size center dock issue of both panes
Again with this.
Please, not only tweaks for the UI. Please, enable multi-output for user function blocks and calls to user functions from user functions. Multi-output and call to functions only work for macros. RSL editor was recommended to me...but this works only to create macros.
Made tweaks to Shader Builder UI; work toward consistency with Shader Mixer and ultimately toward fixing the minimum size center dock issue of both panes
Again with this.
Please, not only tweaks for the UI. Please, enable multi-output for user function blocks and calls to user functions from user functions. Multi-output and call to functions only work for macros. RSL editor was recommended to me...but this works only to create macros.
That's a functional thing, not just a UI thing, as far as I can tell.
Made tweaks to Shader Builder UI; work toward consistency with Shader Mixer and ultimately toward fixing the minimum size center dock issue of both panes
Again with this.
Please, not only tweaks for the UI. Please, enable multi-output for user function blocks and calls to user functions from user functions. Multi-output and call to functions only work for macros. RSL editor was recommended to me...but this works only to create macros.
That's a functional thing, not just a UI thing, as far as I can tell.
Exactly, please don't stop in UI, follow with more deep tweaks.
I wish new beta will come soon with 10 series Pascal support, just using my Cpu to rendering my Iray projects sucks as it's taking me almost 2 hours to render 720p that should only take 10 minuites with the gpu supported.
not sure if this is a DS bug, or a windows update issue. i have noticed that saving Material Presets in the current Beta is taking an extremely long time, ( over a minute for a simple Lip colour option) WAY longer than in the previous build. Windows 7 Ultimate. Khory mentioned that she has noticed the same lagginess , i believe Khory is running Windows 10.
in previous versions of DS, saving even a complicated Material Preset only took a few seconds.
not sure if this is a DS bug, or a windows update issue. i have noticed that saving Material Presets in the current Beta is taking an extremely long time, ( over a minute for a simple Lip colour option) WAY longer than in the previous build. Windows 7 Ultimate. Khory mentioned that she has noticed the same lagginess , i believe Khory is running Windows 10.
in previous versions of DS, saving even a complicated Material Preset only took a few seconds.
If you try a plain OpenGL render does that seem slower?
Then,, when you offer new beta, or up-date build, DAZ test team work with , which video card, and windows, with driver,, ?
without knowing it,, I feel,, I can not find best driver for my PC and windows. anymore.
when I serch driver in Nvidia,, I can only see new drivers.. for windows 10. but if current DAZ stuido, and interective mode, still need old driver,,
please tell me,, which driver you recommend, with which video card please... you DAZ really luck document about manything,, just strong about promote I feel.
Now I reander,, simple scene (just 2 character, all mat use iray shader,, without DOF,, ) my render window keep 20 % forever I feel.
maybe it may not change,, after 2 hour or 3 hour,,
I check 10 minutes it show just 20%,, I check 38 minutes later , it still show just 20%, , I do not tweak render setting, keep as default .
it is nothing about interective mode. just render with photoreal mode. as same as before.
DS iray do not work well at least newest Nvidia driver
375.63 WHQL
2016.10.23
when I serch nvidia, these driver are recommended for windows 10 . then which may work well about interective and blend mode, without,, many crush and finish viewport render?
just tweak one parameter of draw setting, with iray blend mode DS suddenly crush, I had already seen, many times. or can not render in 3d view at all.
You must feel un-stalbilty with many case , when you play with blend mode to see interective scene.
It may not problem when i just load new one nude figure, or primitive, and with default HDRI then render.
but no one may hope to use as final render, and no one may not say, it work well. I hope more test when they release beta, or version up product build.
at least please DAZ discribe , test detail ,, ( windows version,, video card, drover version,, and which scene they use,, to test the beta etc)
==============
I still see this "fatal erroer window" even though I roll back to 372 , untill I load scene, then interective render actually start and show scene in 3d view.
It seems better, I do not use GPU but CPU only. actually when I use SLI mode, ( I know it may not recommended)
itnrective mode sometimes work well (maybe I feel cpu only render,, with SLI mode) .
I gradually hope to perfectly remove interctive blend mode,, from DAZ STUDIO. , sometimes it show access violence erroer, somtimes it say,, unexpected erroer etc. abpit same scene.
So that now I up-date driver from 372.20 to 372.70, (clean up-date) , then start daz studio without LSI, SLI then open same scene, keep draw setting (iray view)
blend mode, interective to rendersetting,, (rendersetting = photorreal),, DS can load scene, but preparing viewport seems take manytimes, then I think memorize but
untill DS show 3d view as rendered (interective),, DS shut down again. I get same erroer above pic.
libert.dll seems cause this erroer, but memoy address? seems change. I just report,, it seems not simple driver issue. may check with product build too.
then may send report,,,
I really hoped to modify and tweak my project scene this month, I had many plan which I want to try , but,,, after find this problem , I can not get any progress,
simply because shut down happen, too often to change something in the scene ><; Boo Boo Boo.
then,,, Richard,,, ,, I think,, You promised me one month before to check my topic which I ask you by PM,,, ( bug report) when you have time,,, but I believe,,
Richard must forget it perfectly ><; I really feel Nothing but sad. ><;
==============
Anyway I sent bug report arelady,, Request #229693
I can confrm it only happen, when I use blend mode (or interective mode) in draw setting, keep "photo real" in draw setting not cause this problem.
and closed scene ""in room scene, with "scene only" light , mesh light",, often cause this problem.
it happen both beta and product build. with most of recent Nvidia drivers which offered for windows 10 (now I use 372) for 980 ti
Sorry, I have your PM sitting unread in my inbox as a (reproachful) reminder that I need to look at the issue but I have been running late on everything.
Comments
Considering that it's a private beta, I think it's nice that we get to see what's being worked on.
+1
I agree.
I still wish I had some idea when to expect the next beta release, hopefully with support for the Pascal based Nvidia cards. (Me and a number of other folks with new Nvidia cards...lol)
Well those results will tell me if I need to consider getting one, or not.
I was actually at Nvidia's page contemplating a new Titan, then figured I want to benchmarks, timings from folks here... Not read sales hype.
Hello guys,
I wish I could download DS beta with DIM 1.1.0.64 but always it says "download fail" for both 32 and 64 bit version.
Everything else works and can be downloaded or installed except the DS beta version.
I'm on windows 10 64 bit, everything is up to date and my download speed is very good.
If there is a way to help me, please let me know.
Thank you !
I have the same problem !!! :_(
The web team is working on a number of issues relating to the site and content delivery systems - I imagine that is the issue with downloading DS. I would give it a rest for today and see if the situation is fixed tomorrow.
Thank you very much,
I shall wait, few days maybe.
I can only say you have only been very kind and very helpful.
It's a most wonderful community here, on Daz.
I wish you a wonderful day, good luck and inspiration!![wink wink](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/wink_smile.png)
Thank you, and thank you too for your patience.
From change log
Thankkkkkkkkkkkkkkkkkkkkkssssssssssss!!! DAZ team. I'm waiting for this beauty release.
Ohhhhhhh!!! waiting for this too
i need help i use DIM 1.1.0.64 , when i want update 2 products , it Written on the button ( download failed ) every time i press download bottom .
my products : 1- Look at my Hair FREE Player .
2- Kaia for Kalea 7 .
Can someone from DAZ confirm that this delay is occurring due to the implementation of CUDA 8 and Iray 2016.2? If so, I will love you guys
Certainly the change log mentioned adding (a beta version of) the 2016.2 SDK.
So will the next beta launch by the end of the month or what because Im getting a new pc for my birthday which has a 1070 in it so I would love to be able to use it in Daz Studio
I don't think anyone knows...
I just bought a new computer with a 1080 and though DS isn't using the GPU for renders, it's still very fast. How well/fast your birthday computer will render until Pascal is supported will be dependent on your CPU, so if you have the choice, get as good a CPU as you can afford. I got an i7-6900K Eight-Core 3.20GHz with 20MB Cache and a test render shows the new computer rendering about 5.6 times faster than the old one, an i7-4770 Quad-Core 3.40GHz cpu.
THANK YOU
Again with this.
Please, not only tweaks for the UI. Please, enable multi-output for user function blocks and calls to user functions from user functions. Multi-output and call to functions only work for macros. RSL editor was recommended to me...but this works only to create macros.
That's a functional thing, not just a UI thing, as far as I can tell.
Exactly, please don't stop in UI, follow with more deep tweaks.
I wish new beta will come soon with 10 series Pascal support, just using my Cpu to rendering my Iray projects sucks as it's taking me almost 2 hours to render 720p that should only take 10 minuites with the gpu supported.
not sure if this is a DS bug, or a windows update issue. i have noticed that saving Material Presets in the current Beta is taking an extremely long time, ( over a minute for a simple Lip colour option) WAY longer than in the previous build. Windows 7 Ultimate. Khory mentioned that she has noticed the same lagginess , i believe Khory is running Windows 10.
in previous versions of DS, saving even a complicated Material Preset only took a few seconds.
If you try a plain OpenGL render does that seem slower?
I run current beta and product bulid ds 4.9 with windows 10, I feel really un-stable at least about current beta.
the only reason I may keep use this beta is simply because,, iray up-date and You discribe many bugs are fixed.
I flankly ask DAZ man, you dsicrbe, you are on going doucment about draw setting pane,
about 4.9.3.37 (July 5, 2016)
Draw Settings
Ongoing updates to documentation; remaining pages are actively being reviewed/edited
then today,, 2016 10/24 ,, I still can not read any useful official document about draw setting with iray rendering (photoreal and interective)
Are you really understand importace of doucment?
Then,, when you offer new beta, or up-date build, DAZ test team work with , which video card, and windows, with driver,, ?
without knowing it,, I feel,, I can not find best driver for my PC and windows. anymore.
when I serch driver in Nvidia,, I can only see new drivers.. for windows 10. but if current DAZ stuido, and interective mode, still need old driver,,
please tell me,, which driver you recommend, with which video card please... you DAZ really luck document about manything,, just strong about promote I feel.
Now I reander,, simple scene (just 2 character, all mat use iray shader,, without DOF,, ) my render window keep 20 % forever I feel.
maybe it may not change,, after 2 hour or 3 hour,,
I check 10 minutes it show just 20%,, I check 38 minutes later , it still show just 20%, , I do not tweak render setting, keep as default .
it is nothing about interective mode. just render with photoreal mode. as same as before.
As far as I know DS works with the current drivers from nVidia - I am not quite up-to-daye but not far off.
DS iray do not work well at least newest Nvidia driver
when I serch nvidia, these driver are recommended for windows 10 . then which may work well about interective and blend mode, without,, many crush and finish viewport render?
just tweak one parameter of draw setting, with iray blend mode DS suddenly crush, I had already seen, many times. or can not render in 3d view at all.
I'm using 372.70, but I rarely use the nVidia preview mode.
thanks,,, but,,,,,, Please try frequently, iray preview mode ^^;
You must feel un-stalbilty with many case , when you play with blend mode to see interective scene.
It may not problem when i just load new one nude figure, or primitive, and with default HDRI then render.
but no one may hope to use as final render, and no one may not say, it work well. I hope more test when they release beta, or version up product build.
at least please DAZ discribe , test detail ,, ( windows version,, video card, drover version,, and which scene they use,, to test the beta etc)
==============
I still see this "fatal erroer window" even though I roll back to 372 , untill I load scene, then interective render actually start and show scene in 3d view.
It seems better, I do not use GPU but CPU only. actually when I use SLI mode, ( I know it may not recommended)
itnrective mode sometimes work well (maybe I feel cpu only render,, with SLI mode) .
I gradually hope to perfectly remove interctive blend mode,, from DAZ STUDIO. , sometimes it show access violence erroer, somtimes it say,, unexpected erroer etc. abpit same scene.
So that now I up-date driver from 372.20 to 372.70, (clean up-date) , then start daz studio without LSI, SLI then open same scene, keep draw setting (iray view)
blend mode, interective to rendersetting,, (rendersetting = photorreal),, DS can load scene, but preparing viewport seems take manytimes, then I think memorize but
untill DS show 3d view as rendered (interective),, DS shut down again. I get same erroer above pic.
libert.dll seems cause this erroer, but memoy address? seems change. I just report,, it seems not simple driver issue. may check with product build too.
then may send report,,,
I really hoped to modify and tweak my project scene this month, I had many plan which I want to try , but,,, after find this problem , I can not get any progress,
simply because shut down happen, too often to change something in the scene ><; Boo Boo Boo.
then,,, Richard,,, ,, I think,, You promised me one month before to check my topic which I ask you by PM,,, ( bug report) when you have time,,, but I believe,,
Richard must forget it perfectly ><; I really feel Nothing but sad. ><;
==============
Anyway I sent bug report arelady,, Request #229693
I can confrm it only happen, when I use blend mode (or interective mode) in draw setting, keep "photo real" in draw setting not cause this problem.
and closed scene ""in room scene, with "scene only" light , mesh light",, often cause this problem.
it happen both beta and product build. with most of recent Nvidia drivers which offered for windows 10 (now I use 372) for 980 ti
Sorry, I have your PM sitting unread in my inbox as a (reproachful) reminder that I need to look at the issue but I have been running late on everything.