i'll go ahead and blame Daz Central on this too, because this is a problem i din't have until now also.. lol

And is PostgreSQL installed?

No, i didnt know what it was, so i didnt install it.

I just did the new update on Daz 3D through the Daz Central but Daz Studio is not supported on Big Sur this is the full new verion not beta. I can find nothing on Daz being updated to work on the new Mac OS?

No, Apple didn't "break" anything, Apple has been warning users forever of a change in C library names in XCode and now it's final with Big Sur.  Someone at DAZ will figure it out and recompile with the new library name.

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

My driver is older, 452.06 - I'll try later with a more recent version but I certainly can't reproduce this right now. Actually, the GPU did fail tonight. Tried a couple of times and still getting the same result, also tried beta and General Release in case they were giving different results. Of course that doesn't mean Daz will see the same.

So, it has failed when you update the driver?
If not, maybe it hasn't failed before because you haven't waited long enough for the Iray preview to finish completely.

It's possible I didn't wait long eniough, though I thought I had. I think you are the first reporter to stress the need for the nVidia Iray preview mode to be on first; you're certainly the first to say it has to be complete.

I also have a problem with "Iray SectionPlane Node"
All my scenes have these planes and now they don't render, but if I delete all the 'Iray SectionPlane Nodes', the rendering happens.

This is very sad.

OMG, it would be good to have known this before... words are coming out of my mouth that I prefer not to write here, lol

SOLUTION TO THE IRAY SECTION PLANES PROBLEM
- Go to Render Settings (Nvidia Iray) > Section Objects
- Enable "Section Caps Enabled"
- ENJOY!

Now, with your permission, I'm going to cry, scream and jump at the same time :-p

I just did the new update on Daz 3D through the Daz Central but Daz Studio is not supported on Big Sur this is the full new verion not beta. I can find nothing on Daz being updated to work on the new Mac OS?

That looks as if the file has not been properly decrypted, so it is completely unreadable when run. If the set has thumbnails do they display correctly in the content pane - if not that would tend to back up the not-decrypted diagnosis. I don't think these scripts have been updated to run when isntalled through Connect, so it may be best to unisntall in DS and then install through Install Manager (or Daz Central - whichever you use).

Thank you for the quick response.

I install all DAZ products using IM. When I got the first error this evening I thought it might have been the DS update, so I uninstalled them and re-installed using IM. The thumbnails appear to be okay. I will try uninstalling, downloading and reinstalling again tomorrow evening and will post an update.

Cheers

Paolo

That looks as if the file has not been properly decrypted, so it is completely unreadable when run. If the set has thumbnails do they display correctly in the content pane - if not that would tend to back up the not-decrypted diagnosis. I don't think these scripts have been updated to run when isntalled through Connect, so it may be best to unisntall in DS and then install through Install Manager (or Daz Central - whichever you use).

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

My driver is older, 452.06 - I'll try later with a more recent version but I certainly can't reproduce this right now. Actually, the GPU did fail tonight. Tried a couple of times and still getting the same result, also tried beta and General Release in case they were giving different results. Of course that doesn't mean Daz will see the same.

So, it has failed when you update the driver?
If not, maybe it hasn't failed before because you haven't waited long enough for the Iray preview to finish completely.

It's possible I didn't wait long eniough, though I thought I had. I think you are the first reporter to stress the need for the nVidia Iray preview mode to be on first; you're certainly the first to say it has to be complete.

I'm happy to be able to help and contribute with my grain of sand to the solution of the problem :-D

Indeed, if the Iray preview isn't complete, one can turn the camera around and it will work properly; one must wait until it's complete to get the error.

Anyway, that is the error in the Iray preview, but that same error also appears when you want to render the image/animation, after a few iterations the error appears and from then on it works through the CPU.

Thanks for your time!

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

My driver is older, 452.06 - I'll try later with a more recent version but I certainly can't reproduce this right now. Actually, the GPU did fail tonight. Tried a couple of times and still getting the same result, also tried beta and General Release in case they were giving different results. Of course that doesn't mean Daz will see the same.

So, it has failed when you update the driver?
If not, maybe it hasn't failed before because you haven't waited long enough for the Iray preview to finish completely.

It's possible I didn't wait long eniough, though I thought I had. I think you are the first reporter to stress the need for the nVidia Iray preview mode to be on first; you're certainly the first to say it has to be complete.

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

My driver is older, 452.06 - I'll try later with a more recent version but I certainly can't reproduce this right now. Actually, the GPU did fail tonight. Tried a couple of times and still getting the same result, also tried beta and General Release in case they were giving different results. Of course that doesn't mean Daz will see the same.

So, it has failed when you update the driver?
If not, maybe it hasn't failed before because you haven't waited long enough for the Iray preview to finish completely.

Just another take......I always just end up finding where all the space is taken, moving and creating a symbolic link

mklink /J "C:\Users\User\Documents\DAZ 3D\Studio" "D:\Studio"

mklink /J "C:\Users\Public\Documents\My DAZ 3D Library" "D:\My DAZ 3D Library"
mklink /J "C:\Daz 3D" "D:\Daz 3D"

Connect/DIm/Central all default to different places and make files in every nook and cranny of my c: drive, I just route them where I want.

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

My driver is older, 452.06 - I'll try later with a more recent version but I certainly can't reproduce this right now. Actually, the GPU did fail tonight. Tried a couple of times and still getting the same result, also tried beta and General Release in case they were giving different results. Of course that doesn't mean Daz will see the same.

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

Correct me if I'm wrong, but is this the first time you've mentioned you're using Daz Central as your installation manager? I don't know why it would matter in this case, but there have been many reports of buggy behavior with Daz Central (it's a very new program) and Daz installations to the point where it seems most experienced users (even ones who don't need the much more advanced options DIM offers) have shied away from adopting it. Could be that the difference between people seeing this and not is actually which install manager they're using (could also be proven wrong about this very quickly.)

Yep, this is the first time I mention it because it's the first time I do it through it; previously I had downloaded it through DIM but installed it manually, with the same result and the same error, and finally I also tried updating directly through DIM, and it also failed.

So I tried the 3 methods, manual/DIM/Daz Central, and there's no difference in the result :-/

Thanks anyway.

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

 

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

 

Hope that helps.

Correct me if I'm wrong, but is this the first time you've mentioned you're using Daz Central as your installation manager? I don't know why it would matter in this case, but there have been many reports of buggy behavior with Daz Central (it's a very new program) and Daz installations to the point where it seems most experienced users (even ones who don't need the much more advanced options DIM offers) have shied away from adopting it. Could be that the difference between people seeing this and not is actually which install manager they're using (could also be proven wrong about this very quickly.)

That User Data is for content, and will should not be affected by updating Studio, although it is a good idea to back it up regularly, and now would be a good time, just in case, as they say.

To save the current version of Studio on your system, copy the existing installers from your download folder to a safe place. If you use DIM (and, I suppose, DAZ Central), you will see the new files that will be downloaded with "DAZ Studio 4.14" in the name. You will first want to copy the same files you have with "DAZ Studio 4.12" in the name (if you are using 4.12) out to another folder out of the reach of DIM (or Central).

Given your join date you probably already have Victoria 4, but it isn't part of the free base content so you need to install it (through Daz Central/Install Manager or manually, it can't be installed through DS itself).

I uninstalled through both DAZ DIm and Central, each time separately. I then reinstaled with each and those did not help the issue. i decided to reset my database(taking forever), but it appears that is not fixing the issue either.

Unfortunately, v4.14 still presents the same problem :-/

https://www.daz3d.com/forums/discussion/comment/6190691/#Comment_6190691

 

This is a bit frustrating, to use the 3090 without Iray planes I prefer to continue with my 2x1080Ti and be able to use Iray planes in the stable version.

No news on possible solution?

Thanks!

Can you provide a scene file or set of steps to reproduce it, so Daz3d can report it to NVidia?

 

Sure, it's really easy:

- Open Daz

- Load G8, G3 or G1 (G1 with some skin texture) (INTERESTING NOTE: The G2 characters, specifically Genesis 2 Base Female, DO NOT present that problem!)

- Create a Iray Section Plane node (Move it a little bit the Y axis up to see part of the character)

- Activate the Iray preview and wait for it to finish (use GPU-Z or Windows resource monitor to monitor GPU usage)

- When the preview is complete and the GPU doesn't make use of the CUDA cores, simply move the perspective or camera, at this point the Iray preview will no longer work, the GPU will not be detected by the program and will require a restart; or if you try to uncheck and re-check the GPU in the advanced Iray settings, and activate the Iray preview again, Daz will give an error and shut down. (NOTE: Curiously, you can move the perspective or camera while the Iray preview isn't completely finished and it works that way; so the problem is when the preview is completely finished).

 

Tested on versions 4.12.2.60 and 4.14.x, with a 3090 or a 1080Ti (so it's not an exclusive problem of the new GPUs), with several drivers (Game or Studio), with W7, W10, and with a new installation of W10.

BTW, the example is using the Iray preview, but if the scene or animation is rendered the same problem happens.

 

Thanks!

 

UPDATE:
New tests carried out indicate that the problem is related to the skin material. I had previously mentioned that, curiously, G2 Base Female didn't suffer from this problem, and that's right, BUT if you apply a G1 skin material, BOOM! The problem appears.
On the other hand, I've tested properly G2 Base Female, doing 4 complete Iray previews, no trace of the problem... so, what's different about the material used in G2 referring to G1, G3 or G8 in order that this problem doesn't occur?

Those are slightly different steps from any I've seen before, but trying it just now I didn't get any issues and the GPU remains avaialble for rendering. Until Daz can figure out a combination of factors that reliably triggers the issue (and they have been trying) it isn't going to be possible to report the issue to nVidia.

Thank you for trying it, I didn't think it would be so difficult to replicate the problem since so many seem to suffer from it.

I have tried again, clean installation of W10, I haven't installed anything else (apart from Chrome and Winrar), I haven't even installed drivers or Windows updates.

While I was downloading Daz Central and Daz Studio v4.14.0.8, Windows installed the Nvidia driver, v456.38, and I thought that before installing a more recent one from the nvidia website I could try this one, and it failed.
Then I closed Daz, installed the latest Nvidia Studio driver (v456.71), restarted, opened Daz to clean the error log, restarted it and tried again, same error.

Attached the LOGs of both occasions.

Steps that I have followed.
- Open Daz
- Load G8 Female Base
- Create an Iray section plane (raise it a little bit to see the legs of the character rendered)
- Activate the Iray preview and, IMPORTANT, wait until it's completed, that is, the GPU is not being used yet to finish the rendering (in the windows resource monitor, wait for the CUDA cores to drop the percentage and not be in use)
- Move the perspective (I haven't even created a camera), and from there on it renders through CPU.

Hope that helps.

...well, having read numerous threads about DAZ central issues, the implementation of Filament excluding Mac users, products now being made for Filament which is a viewport option, (seriously... can we please have some new shaders for Open GL too and maybe some outfits, pretty please), quality control going downhill, if not non-existant already, the store that has been a complete mess for years and will continue to be despite attempts of "fixing" it, and lastly...help support now trying to convince me that the Iray Uber shader infact is an RSL shader, so the fact that a product's MDL shader presets now are just copied over and renamed RSL materials and put in a 3Delight materials folder is totally fine because they actually render (kind of) in 3DL, I'm inclined to believe that DAZ is actually heading south...

Have you tried daz Central? That asks which drive to use, and then creates a single uber-folder named Daz 3D on that drive that is used for everything - that would have updated the DIM paths too.

.

We just did a fix for an issue that was causing some to not be able to see their products in DIM and Daz Central with that JSON error.  If you're still receiving JSON errors from DIM, please let me know.

 

DIM still doesn't show anything to download for me. The log is showing:

2020-11-11 17:51:12.719 +++++++++++++++ Install Manager 1.4.0.67 starting +++++++++++++++++

2020-11-11 17:51:12.719 OS bits: 64

2020-11-11 17:51:12.719 Platform bits: 64

2020-11-11 17:51:12.719 Qt Version: 4.8.7

2020-11-11 17:51:12.719 Locale: en_GB

2020-11-11 17:51:12.719 Running on Windows 10, Build 9200, No Service Pack Installed

2020-11-11 17:51:12.719 Physical Memory:

2020-11-11 17:51:12.719 Total: 11.9 GB (12875382784)

2020-11-11 17:51:12.719 Avail: 6.2 GB (6667657216)

2020-11-11 17:51:12.719 Virtual Memory:

2020-11-11 17:51:12.734 Total: 127.9 TB (140737488224256)

2020-11-11 17:51:12.734 Avail: 127.9 TB (140732965187584)

2020-11-11 17:51:12.734 Current Memory Usage: 48%

2020-11-11 17:51:12.734 Current DateTime:

2020-11-11 17:51:12.734 Loc: Wed 11. Nov 17:51:12 2020

2020-11-11 17:51:12.734 UTC: Wed 11. Nov 17:51:12 2020

2020-11-11 17:51:12.735 Application Data:

2020-11-11 17:51:12.735 Location = C:/Users/peter/AppData/Roaming/DAZ 3D/InstallManager

2020-11-11 17:51:12.735 Disk Total: 1.9 TB (2197940428800)

2020-11-11 17:51:12.735 Disk Avail: 67.1 GB (72071716864)

2020-11-11 17:51:12.736 Reading dzInstall.ini

2020-11-11 17:51:12.740 Current Account: Peter Wade

2020-11-11 17:51:12.742 Current Download Path:

2020-11-11 17:51:12.742 Location = C:/Users/Public/Documents/DAZ 3D/InstallManager/Downloads

2020-11-11 17:51:12.742 Disk Total: 1.9 TB (2197940428800)

2020-11-11 17:51:12.742 Disk Avail: 67.1 GB (72071716864)

2020-11-11 17:51:12.742 Current Content Install Path:

2020-11-11 17:51:12.742 Location = G:/3DStuff/Daz Library Extension

2020-11-11 17:51:12.742 Disk Total: 2.2 TB (2463426932736)

2020-11-11 17:51:12.742 Disk Avail: 3.7 GB (4036071424)

2020-11-11 17:51:12.743 Current 64-bit Software Install Path:

2020-11-11 17:51:12.743 Location = C:/Program Files

2020-11-11 17:51:12.743 Disk Total: 1.9 TB (2197940428800)

2020-11-11 17:51:12.743 Disk Avail: 67.1 GB (72071716864)

2020-11-11 17:51:12.743 Current 32-bit Software Install Path:

2020-11-11 17:51:12.743 Location = C:/Program Files (x86)

2020-11-11 17:51:12.743 Disk Total: 1.9 TB (2197940428800)

2020-11-11 17:51:12.744 Disk Avail: 67.1 GB (72071716864)

2020-11-11 17:51:12.745 Starting CMS...

2020-11-11 17:51:18.639 Connected to CMS: PostgreSQL 9.3.4, compiled by Visual C++ build 1600, 64-bit

2020-11-11 17:51:26.801 Json Parser (1,1): Syntax error - expected '{' or '['

2020-11-11 17:51:26.801 Unable to parse purchased products

2020-11-11 17:51:26.813 Current Account: Peter Wade

2020-11-11 17:58:53.216 Installed Packages: 12759 : 2.2 TB

2020-11-11 17:58:53.739 Network Error during authentication.

2020-11-11 17:58:53.739 Json Parser (1,1): Syntax error - expected '{' or '['

2020-11-11 17:58:53.739 Unable to parse purchased products

2020-11-11 17:58:53.739 Invalid JSON formatting while processing purchased items.

 

My DIM downloads had returned a few days ago and are now gone again this morning.

From my log:

2020-11-11 10:59:35.887 Network Error during authentication.

2020-11-11 10:59:35.887 Json Parser (1,1): Syntax error - expected '{' or '['

2020-11-11 10:59:35.888 Unable to parse purchased products

2020-11-11 10:59:35.888 Invalid JSON formatting while processing purchased items.

 

Could you try again. We're tweaking some of the server configuration to take into account the load and memory usage patterns to better distribute concurrent requests which is causing some of the larger requests to exceed the memory available to the instance which it looks like you're account is hitting.

@Daz_jon Nothing is showing in the Ready to Download of DIM since this morning. That has not changed.

2020-11-11 13:22:25.571 Network Error during authentication.

2020-11-11 13:22:25.572 Json Parser (1,1): Syntax error - expected '{' or '['

2020-11-11 13:22:25.572 Unable to parse purchased products

2020-11-11 13:22:25.572 Invalid JSON formatting while processing purchased items.