2016-10-27 22:58:44.244 Cuda Version: 6.1 <------?????
Somehow the person naming those logfile parameters confused "CUDA Version" with "Compute Capability".
I just found out that trying to render an untextured figure (using SpyroRue's "Genesis 3 Female Grey Materials" Iray preset over at shareCG) doesn't crash DAZ Studio 4.9.3.117 with an AMD chip and NVIDIA GC. For some odd reason the HDR doesn't seem to be counted as a texture.
Are those who are experiancing the crashing using ALL Iray materials on EVERYTHING?
If everything is Iray materials, then the JIT compiler should not be active. It is what does the on the fly conversion of the materials from 3DL to Iray. It looks to me to be a problem converting things over.
A lot of supposition and/or outright guessing about the problem going on. Most likely is that there is a "close to edge condition" that simply wasn't found before the beta was sent out for public testing. This is one of the dangers of having testing done by those overly knowledgeable about the software: familiarity keeps the testers from doing the things that the general userbase does.
Do I have some ideas where the problem likely lies? Yes, but only because I have had a look at some of the stuff from nVidia's release. Am I gonna make guesses at what exactly is occurring? No, because the cause can come from multiple vectors and since I don't know exactly what DS is doing at this point (reverse engineering is against the EULA) I am not confident that my guess would have any validity. I *AM* sure that the Daz Devs are aware of where the problem is and are likely describing it in very non-PC and "not appropriate for work but used anyway" verbage.
What I am saying is that throwing out guesses based on less than scant evidence about the cause is unhelpful and likely to be taken by some as credible. This can cause folks to make decisions unwisely using data that are completely without merit.
My advice is to wait for definitive information from Daz.
...well one thing I can say, it seems Iray performance (at least for CPU rendering) seems to have improved. I test rendered a scene in the current Beta that I originally rendered a couple days ago on 4.8: I made no changes to any of the render settings or the file between both tests.
Single character, medium size Stonemason set, sun/sky with 5% haze, render size 695 x 900, Render Quality 2
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
...I just ran a test render in the latest Beta release where I didn't convert the clothing materials to Iray and it didn't crash.
How you didn't convert the clothing to IRAY? You mean you render in 3Delight?
...no in Iray. Iray will autoconvert 3DL materials as it sets up the file, though it does take a little longer than manually changing all the surfaces before rendering (I might have saved a couple minutes at best). However, this way I didn't have to mess around with setting the bump and displacement of the fabric so the weave would have some surface deatail instad of looking flat.
It may or may not have somethig to do with iray conversion, but my test GPU and CPU was with Danika default skin, which is 3dl by default. I did not convert to the Genesist 2 iray optimized skin. It crashed whenever i used the Iray preview or tried to render. Weirdly enough though some Iray textures work without crashing, it would take a life time to figure out which ones but in my case i stripped off all textures from Danika and applied some of Mech4d's Cloth shaders from her Volume 2 PBR kit and it didnt crash, however when trying to use some of the Organic PBR shaders as well as metal shaders would immediately crash DAZ. I didnt try all of them for obvious reasons.
The crash also occured as well if i did convert before preview to the Genesis 2 optimized skin setting. I also tried various combinations of texutures removed, starting with just the diffuse layer, than each crash going back in and removing in a row, next being translucency etc..each time causing a crash. It was was only after removing them all would it not crash.
...interesting that the GPU crashes then. As I do not do GPU rendering (I have an old 1 GB 460 which would at best be able to handle a cube primitive with a simple backdrop) I have no idea why it is crashing on the 670 unless its exceeding the card's memory (the 670 only has 2 GB) and dumping to the CPU which is where the issue might be.
...interesting that the GPU crashes then. As I do not do GPU rendering (I have an old 1 GB 460 which would at best be able to handle a cube primitive with a simple backdrop) I have no idea why it is crashing on the 670 unless its exceeding the card's memory (the 670 only has 2 GB) and dumping to the CPU which is where the issue might be.
Are you on Win10?
This crash occurs as soon as hit Iray preview, It doesnt matter if its an HD character, or just a simple low poly table. It crashes if i load a cube and apply any texture to it. So its not a matter of a hand off to CPU.
Am running Windows 7 64bit Pro
This only occurs with the lastest Beta Version, the latest public build runs fine.
I just ran a test both GPU and CPU to see if there was any correlation. Which there doesnt seem to be. Something in the lastest Beta build is just jacked up
...interesting that the GPU crashes then. As I do not do GPU rendering (I have an old 1 GB 460 which would at best be able to handle a cube primitive with a simple backdrop) I have no idea why it is crashing on the 670 unless its exceeding the card's memory (the 670 only has 2 GB) and dumping to the CPU which is where the issue might be.
Are you on Win10?
This crash occurs as soon as hit Iray preview, It doesnt matter if its an HD character, or just a simple low poly table. It crashes if i load a cube and apply any texture to it. So its not a matter of a hand off to CPU.
Am running Windows 7 64bit Pro
This only occurs with the lastest Beta Version, the latest public build runs fine.
I just ran a test both GPU and CPU to see if there was any correlation. Which there doesnt seem to be. Something in the lastest Beta build is just jacked up
Daniel
Maybe its an issue of older CPU´s that not support 4.1/4.2.
This explains some people can render (AMD-FX CPU´s and Intel) an some cannot (AMD PHENOM and maybe older Intel)
...I thought SSE4.1 was only important to take advantage of the speed boost in Reality4/Lux 1.5. Odd, because I have a first generation Nehalem (Bloomfield) i7 which is not supposed to support it and I have no trouble.
...I thought SSE4.1 was only important to take advantage of the speed boost in Reality4/Lux 1.5. Odd, because I have a first generation Nehalem (Bloomfield) i7 which is not supposed to support it and I have no trouble.
...I thought SSE4.1 was only important to take advantage of the speed boost in Reality4/Lux 1.5. Odd, because I have a first generation Nehalem (Bloomfield) i7 which is not supposed to support it and I have no trouble.
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
It's the other way round, each new CUDA library continues to support all the older hardware, (unless the hardware is really, really ancient, then it will eventually get dropped!).
This combination: AMD Phenom II X6, Windows 10, nVidia 750ti and old nVidia 369!!! drivers; is not giving any problems.
I was running 369 drivers, have an AMD 965 black edition, nvidia GTX 670, with windows 7 64-bit pro editions. I updated to the driver in hopes it would fix the crash but no change. So its not the driver.
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
thast new for me. i read only the 10xx runs with CUDA 8
Since when is Wikipedia a 100 % reliable source of information?! Due to the english article the actual version of DAZ Studio would be 4.9.0.63, the german one says it's 4.7.0.12 and the swedish 3.1.1.73. If you want to know what GPU's and/or compute capabilities Iray 2016.2 supports, just ask at the NVIDIA Advanced Rendering Forum. They don't bite.
The same for your unconfirmed SSE 4.1 theory. I got an AMD Athlon 64 X2 4600+ (Windsor) CPU which supports the instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64, AMD-V. So, no SSE4 support. I am able to render an untextured Genesis 3 figure (using SpyroRue's "Genesis 3 Female Grey Materials" Iray preset over at shareCG) just fine. I can also render an untextured Genesis figure with its default RDL material (bare grey) just fine.
If the problem would be SSE4 related, DS would still crash for me then, since my chipset doesn't support that, right?
So, people, please stop spreading unconfirmed theories in the forums, open a ticket and send Support your crashlogs, along or not along with your guesses where the error might be relying on.
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
thast new for me. i read only the 10xx runs with CUDA 8
Since when is Wikipedia a 100 % reliable source of information?! Due to the english article the actual version of DAZ Studio would be 4.9.0.63, the german one says it's 4.7.0.12 and the swedish 3.1.1.73. If you want to know what GPU's and/or compute capabilities Iray 2016.2 supports, just ask at the NVIDIA Advanced Rendering Forum. They don't bite.
The same for your unconfirmed SSE 4.1 theory. I got an AMD Athlon 64 X2 4600+ (Windsor) CPU which supports the instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64, AMD-V. So, no SSE4 support. I am able to render an untextured Genesis 3 figure (using SpyroRue's "Genesis 3 Female Grey Materials" Iray preset over at shareCG) just fine. I can also render an untextured Genesis figure with its default RDL material (bare grey) just fine. But whenever I try to render something textured, be it RDL or MDL material, DS goes into mutiny mode.
If the problem would be SSE4 related, DS would still crash for me then, since my chipset doesn't support that, right?
So, people, please stop spreading unconfirmed theories in the forums, open a ticket and send Support your crashlogs, along or not along with your guesses where the error might be relying on.
And this is what i am experiencing, although as i said above some MDL iray textures dont cause the crash i used some of Mech4ds pbr fabric shaders and it does not crash. But loading Metal or construction materials crashes it.
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
thast new for me. i read only the 10xx runs with CUDA 8
Since when is Wikipedia a 100 % reliable source of information?! Due to the english article the actual version of DAZ Studio would be 4.9.0.63, the german one says it's 4.7.0.12 and the swedish 3.1.1.73. If you want to know what GPU's and/or compute capabilities Iray 2016.2 supports, just ask at the NVIDIA Advanced Rendering Forum. They don't bite.
The same for your unconfirmed SSE 4.1 theory. I got an AMD Athlon 64 X2 4600+ (Windsor) CPU which supports the instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64, AMD-V. So, no SSE4 support. I am able to render an untextured Genesis 3 figure (using SpyroRue's "Genesis 3 Female Grey Materials" Iray preset over at shareCG) just fine. I can also render an untextured Genesis figure with its default RDL material (bare grey) just fine. But whenever I try to render something textured, be it RDL or MDL material, DS goes into mutiny mode.
If the problem would be SSE4 related, DS would still crash for me then, since my chipset doesn't support that, right?
So, people, please stop spreading unconfirmed theories in the forums, open a ticket and send Support your crashlogs, along or not along with your guesses where the error might be relying on.
And this is what i am experiencing, although as i said above some MDL iray textures dont cause the crash i used some of Mech4ds pbr fabric shaders and it does not crash. But loading Metal or construction materials crashes it.
at my chrashes it when i load simple hair textures on untextured hair
Comments
Somehow the person naming those logfile parameters confused "CUDA Version" with "Compute Capability".![frown frown](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/confused_smile.png)
I just found out that trying to render an untextured figure (using SpyroRue's "Genesis 3 Female Grey Materials" Iray preset over at shareCG) doesn't crash DAZ Studio 4.9.3.117 with an AMD chip and NVIDIA GC. For some odd reason the HDR doesn't seem to be counted as a texture.
Are those who are experiancing the crashing using ALL Iray materials on EVERYTHING?
If everything is Iray materials, then the JIT compiler should not be active. It is what does the on the fly conversion of the materials from 3DL to Iray. It looks to me to be a problem converting things over.
...I just ran a test render in the latest Beta release where I didn't convert the clothing materials to Iray and it didn't crash.
A lot of supposition and/or outright guessing about the problem going on. Most likely is that there is a "close to edge condition" that simply wasn't found before the beta was sent out for public testing. This is one of the dangers of having testing done by those overly knowledgeable about the software: familiarity keeps the testers from doing the things that the general userbase does.
Do I have some ideas where the problem likely lies? Yes, but only because I have had a look at some of the stuff from nVidia's release. Am I gonna make guesses at what exactly is occurring? No, because the cause can come from multiple vectors and since I don't know exactly what DS is doing at this point (reverse engineering is against the EULA) I am not confident that my guess would have any validity. I *AM* sure that the Daz Devs are aware of where the problem is and are likely describing it in very non-PC and "not appropriate for work but used anyway" verbage.
What I am saying is that throwing out guesses based on less than scant evidence about the cause is unhelpful and likely to be taken by some as credible. This can cause folks to make decisions unwisely using data that are completely without merit.
My advice is to wait for definitive information from Daz.
Kendall
...well one thing I can say, it seems Iray performance (at least for CPU rendering) seems to have improved. I test rendered a scene in the current Beta that I originally rendered a couple days ago on 4.8: I made no changes to any of the render settings or the file between both tests.
Single character, medium size Stonemason set, sun/sky with 5% haze, render size 695 x 900, Render Quality 2
4.8 render time: 1hr 29m 29 s
4.9.3.117 render time: 51 m 44 s.
How you didn't convert the clothing to IRAY? You mean you render in 3Delight?
I'm a little confused. I have a GTX970 and I went ahead and updated to the latest drive. But do I need to get the Cuda 8 update too or is that just for the 1000 series folks?
900er Family doesn´t support CUDA 8
https://de.wikipedia.org/wiki/CUDA
So will I still be able to use the new Beta?
I think so. Otherwise all people must buy a Nvidia 1000er. You can use your Card but use CUDA 6.5-7.5.
...no in Iray. Iray will autoconvert 3DL materials as it sets up the file, though it does take a little longer than manually changing all the surfaces before rendering (I might have saved a couple minutes at best). However, this way I didn't have to mess around with setting the bump and displacement of the fabric so the weave would have some surface deatail instad of looking flat.
It may or may not have somethig to do with iray conversion, but my test GPU and CPU was with Danika default skin, which is 3dl by default. I did not convert to the Genesist 2 iray optimized skin. It crashed whenever i used the Iray preview or tried to render. Weirdly enough though some Iray textures work without crashing, it would take a life time to figure out which ones but in my case i stripped off all textures from Danika and applied some of Mech4d's Cloth shaders from her Volume 2 PBR kit and it didnt crash, however when trying to use some of the Organic PBR shaders as well as metal shaders would immediately crash DAZ. I didnt try all of them for obvious reasons.
The crash also occured as well if i did convert before preview to the Genesis 2 optimized skin setting. I also tried various combinations of texutures removed, starting with just the diffuse layer, than each crash going back in and removing in a row, next being translucency etc..each time causing a crash. It was was only after removing them all would it not crash.
Daniel
...however don't you have both an AMD GPU and CPU?
Also Iray doesn't permanently convert the materials (they still show up as 3DL materials in the Surfaces tab), it only does so for the render process.
No, i have AMD CPU but a EVGA GTX 670
...interesting that the GPU crashes then. As I do not do GPU rendering (I have an old 1 GB 460 which would at best be able to handle a cube primitive with a simple backdrop) I have no idea why it is crashing on the 670 unless its exceeding the card's memory (the 670 only has 2 GB) and dumping to the CPU which is where the issue might be.
Are you on Win10?
This crash occurs as soon as hit Iray preview, It doesnt matter if its an HD character, or just a simple low poly table. It crashes if i load a cube and apply any texture to it. So its not a matter of a hand off to CPU.
Am running Windows 7 64bit Pro
This only occurs with the lastest Beta Version, the latest public build runs fine.
I just ran a test both GPU and CPU to see if there was any correlation. Which there doesnt seem to be. Something in the lastest Beta build is just jacked up
Daniel
Maybe its an issue of older CPU´s that not support 4.1/4.2.
This explains some people can render (AMD-FX CPU´s and Intel) an some cannot (AMD PHENOM and maybe older Intel)
...I thought SSE4.1 was only important to take advantage of the speed boost in Reality4/Lux 1.5. Odd, because I have a first generation Nehalem (Bloomfield) i7 which is not supposed to support it and I have no trouble.
Nehlam supports SSE4.1/4.2 https://en.wikipedia.org/wiki/Nehalem_(microarchitecture)
It does.
This combination: AMD Phenom II X6, Windows 10, nVidia 750ti and old nVidia 369!!! drivers; is not giving any problems.
EDIT: spoke too soon, I got the crash with jpg textures!
thast new for me. i read only the 10xx runs with CUDA 8
It's the other way round, each new CUDA library continues to support all the older hardware, (unless the hardware is really, really ancient, then it will eventually get dropped!).
I was running 369 drivers, have an AMD 965 black edition, nvidia GTX 670, with windows 7 64-bit pro editions. I updated to the driver in hopes it would fix the crash but no change. So its not the driver.
Since when is Wikipedia a 100 % reliable source of information?! Due to the english article the actual version of DAZ Studio would be 4.9.0.63, the german one says it's 4.7.0.12 and the swedish 3.1.1.73. If you want to know what GPU's and/or compute capabilities Iray 2016.2 supports, just ask at the NVIDIA Advanced Rendering Forum. They don't bite.![wink wink](http://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/wink_smile.png)
The same for your unconfirmed SSE 4.1 theory. I got an AMD Athlon 64 X2 4600+ (Windsor) CPU which supports the instructions sets MMX (+), 3DNow! (+), SSE, SSE2, SSE3, x86-64, AMD-V. So, no SSE4 support. I am able to render an untextured Genesis 3 figure (using SpyroRue's "Genesis 3 Female Grey Materials" Iray preset over at shareCG) just fine. I can also render an untextured Genesis figure with its default RDL material (bare grey) just fine.
If the problem would be SSE4 related, DS would still crash for me then, since my chipset doesn't support that, right?
So, people, please stop spreading unconfirmed theories in the forums, open a ticket and send Support your crashlogs, along or not along with your guesses where the error might be relying on.
Finally my Pascal GTX 1060 card can render, much appreciated!
And this is what i am experiencing, although as i said above some MDL iray textures dont cause the crash i used some of Mech4ds pbr fabric shaders and it does not crash. But loading Metal or construction materials crashes it.
at my chrashes it when i load simple hair textures on untextured hair