3Delight rendering with Nvidia Pyshx Issue

kadirkose

Hello, firstly I searched all the parameters for using 3delight and have a nice knowledge about it. My issue is, I am opening daz studio with Nvidia processor and rendering with 3delight. I am having good results as how I want my renders, but when I change my PhysX processor from nvidia control panel (changing auto selection to Nvidia) everything still find in renders but the character skins maps is not appears in that renders, it is all white... eyes, eyelashes etc is ok, but skin is all white.

My question is:

• Is there a way to fix this problem while I am still using the nvidia physX without changing the PhsyX to auto (which I think when I change it, it uses the processor or integrared graphic of Intel)
• Is this about the skin textures that I choosed (I choosed all 3Delight skins)                       thank you for the answers for this newbie ))

BeeMKay

Let me see if I understood correctly what you are trying to do:

1. You set up a scene in 3delight, including surface, lights, etc.
2. You render that scene in 3Delight render engine, and all ist fine. BTW, 3Delight is CPU only, and doesn't use nVidea cards, or any functionality thereof)
3. You then go to the render tab, change to Iray render, and plug in that PhysX thingamin from nvidea? (I'm not sure that is even a valid option for Iray renders, but then, I only use a regular 980Ti...)

To answer the basic questions, yes, when you switch render engines, such issues can happen. 3delight uses different surface settings than Iray, so when you use them in Iray renders, they will be autoconverted in the background. That can, on occasion, lead to problems. It's usually best to simply close the scene, close DS and restart it, and reload the scene.

Richard Haseltine

As far as I know DS does not make any use of PhysX - so if one option works and the other doesn't stick with the one that does.

kadirkose

BeeMKay said:

Let me see if I understood correctly what you are trying to do:

1. You set up a scene in 3delight, including surface, lights, etc.
2. You render that scene in 3Delight render engine, and all ist fine. BTW, 3Delight is CPU only, and doesn't use nVidea cards, or any functionality thereof)
3. You then go to the render tab, change to Iray render, and plug in that PhysX thingamin from nvidea? (I'm not sure that is even a valid option for Iray renders, but then, I only use a regular 980Ti...)

To answer the basic questions, yes, when you switch render engines, such issues can happen. 3delight uses different surface settings than Iray, so when you use them in Iray renders, they will be autoconverted in the background. That can, on occasion, lead to problems. It's usually best to simply close the scene, close DS and restart it, and reload the scene.

Thank you for your answer and time. I have tried different things and guess figured it out. I just changed my textures from delight to nvidia iray and rendered it with 3delight renderer and the character showed up. But must say it is definately not the best result lol. As a memo but it gives fast results then 3delight rendering time.

BeeMKay

Er... there's a reason why 3 Delight textures are for 3Delight, and Iray textures are for Iray, you know.

If you change to Iray render, change the texture to Iray, too, if possible. That will force new data calculation, and the temporary data stored for 3Delight, which causes the headache for Iray, will be overwritten with one that the Iray tender engine can use.

kadirkose

Richard Haseltine said:

As far as I know DS does not make any use of PhysX - so if one option works and the other doesn't stick with the one that does.

That is why I wanted to ask the question. I was just trying to figure out what was going on. thanks for reply

kadirkose

BeeMKay said:

Er... there's a reason why 3 Delight textures are for 3Delight, and Iray textures are for Iray, you know.

If you change to Iray render, change the texture to Iray, too, if possible. That will force new data calculation, and the temporary data stored for 3Delight, which causes the headache for Iray, will be overwritten with one that the Iray tender engine can use.

Do not take serious the results. With help, I figured out that the white texture issue happens sometimes, here is the solution

Did you run these tests more than once? Sometimes the 3delight skin shader used on most recent figures doesn't compile correctly, and you get an all-white skin: restarting DS, or doing File>New, clears the bad files and allows DS to recompile at the next 3Delight render. If you did these tests just once I'd suspect that was what had happened, rather than anything as a direct result of the driver changes.

Just explaining my self a bit clear, I have not use the iray renderer in that prosesses )) here is what I did:

Here is the issue I noticed: I have try 3 different options:

1. I opened my daz studio with Nvidia graphic processor instead of the integrared intel graphics, I choosed all 3delight textures, and rendered with 3delight (Before I launched Daz studio, In Nvidia control panel, I choosed PhysX processor as auto) Result: It works fine.

2. I opened my daz studio with Nvidia graphic processor instead of the integrared intel graphics, I choosed all 3delight textures, and rendered with 3delight (Before I launched Daz studio, In Nvidia control panel, I choosed PhysX processor as Nvidia Graphic processor) Result: Everything looks fine but character skin textures not appear ( skin looks all white)

3.  I opened my daz studio with Nvidia graphic processor instead of the integrared intel graphics, I choosed iray character  textures, and rendered with 3delight (Before I launched Daz studio, In Nvidia control panel, I choosed PhysX processor as Nvidia Graphic processor) Result: Everything looks fine

Main result: When I choosed PhysX processor as Nvida in Nvidia control panel, when I add 3delight textures for character is not shown when rendering with 3delight, but they are shown when I choosed iray textures. (While this processes I never used nvidia iray rendered, for all 3 options, I always used the 3delight renderer as I mentioned above.

Hope I did explained it well, if any case someone will have the same trouble.

**This is all mainless after all we figure aut the real solution but in any case if someone needs what is written I leave it here.

Richard Haseltine

Did you run these tests more than once? Sometimes the 3delight skin shader used on most recent figures doesn't compile correctly, and you get an all-white skin: restarting DS, or doing File>New, clears the bad files and allows DS to recompile at the next 3Delight render. If you did these tests just once I'd suspect that was what had happened, rather than anything as a direct result of the driver changes.

kadirkose

Richard Haseltine said:

Did you run these tests more than once? Sometimes the 3delight skin shader used on most recent figures doesn't compile correctly, and you get an all-white skin: restarting DS, or doing File>New, clears the bad files and allows DS to recompile at the next 3Delight render. If you did these tests just once I'd suspect that was what had happened, rather than anything as a direct result of the driver changes.

Oh my, I tested again and it seems you are right! Well, I guess I have to delete my tests after all, thank you for wake me up

BeeMKay

@kadirkose no reason to yell in big red letters at me. I only tried to help, and your entire workflow makes no sense. 

kadirkose

BeeMKay said:

@kadirkose no reason to yell in big red letters at me. I only tried to help, and your entire workflow makes no sense. 

Oh man, you complately understood it wrong )) I didnt yell to you, it was kind of announcement to people if they will wonder and look out for the same thing, I just did it for let them know my thought was wrong. And I am sorry for this missunderstood, it was my fault, I am removing it right away.