Hi guys.

I would like to ask some help.

I bought a RTX 3080Ti Asus GPU.I want to use this card for rendering.

But the problem is the GPU is not working.I mean the Optix "cores" do not do anything.

My card is working well when i play with some video games.

Do you have any idea why the Optix "cores" doing nothing?

Thank you for your help.

(sorry my english is not so good but i tried to explain the situation)

If you see an error during the rendering process, such as a crash, it may be because of a geometry causing this.
I often encounter this while rendering Cycles-based hairs figures/props with the base or the scalp using a cycles nodes. often I  switch the scalp/base to posersurface and it works.
I've contacted the support during 2021, and I know that they are working on this problem, because of a bug that is hiding quite deep in the Cycles/RTX part of the rendering engine.

For example with this figure: it's a Sasha-19 using one of Afrodite Ohki's Hairs for La Femme:

Something you can check also: be sure to use a Studio version of nvidia's drivers, often their game versions are bugged.

Look in the log (the yellow speech bubble in the far upper right). Is there a CUDA error? If that happens, no renders will work until you close and restart Poser. It will happen again at the same point if you re-render the exact same scene that triggered it originally, but it might not in a very similar scene. I find it happens rarely with Optix but never with non-Optix renders, so a regular GPU render is a workaround. Making sure all the characters are set to Unimesh may be helpful.

Studio driver helps too, as noted by Y-Phil.

They're still working on this one, it's much less frequent than it used to be, and it's now confined to Optix renders.

@Chromestar I have to say that I've never seen any CUDA error logged here- Furthermore, when I encounter the problem I'm describing in my preceding post, I correct the problem and the RTX mode restarts to work correctly without relaunching Poser, but I suppose that it could heavily depend on the reason of the crash.

Y-Phil posted at 3:12 PM Sun, 9 January 2022 - #4433052

If you see an error during the rendering process, such as a crash, it may be because of a geometry causing this.
I often encounter this while rendering Cycles-based hairs figures/props with the base or the scalp using a cycles nodes. often I  switch the scalp/base to posersurface and it works.
I've contacted the support during 2021, and I know that they are working on this problem, because of a bug that is hiding quite deep in the Cycles/RTX part of the rendering engine.

For example with this figure: it's a Sasha-19 using one of Afrodite Ohki's Hairs for La Femme:

Something you can check also: be sure to use a Studio version of nvidia's drivers, often their game versions are bugged.

Yeah!!!

I had to install "Studio version of Nvidia's drivers".

Now the card is working well.

But still I have a little problem.Anyway the rendering looks fine.

One more time:thanks guys for your help.

Those errors within the circle area are due to bad connections in the Material Room for that particular shader.  This requires either removing the offending node(s) or rearranging the connection(s).  TBH, I wouldn't use any of those old shaders under the basic materials folder unless you are rendering in FireFly.  They are holdovers from previous Poser versions.  There are better shaders out there that give excellent results.

You can see one such invalid link below, example provided by... Poser itself, and its "Add reflection" script in the mat room  😂

On the subject of not using old materials in Superfly, I just want to give a reminder that there ARE Supefly-specific materials included with Poser :)

The ones within a folder with my name are merchant resources and all. Use them and change them and include them in your stuff as you see fit. And if you open them in the material room you'll see that they're pretty easy to understand, specially the PhysicalSurface is absurdly straight-forward. Have fun!

@Chromestar I have to say that I've never seen any CUDA error logged here

Most of the time the CUDA errors don't get logged, making the Log rather pointless as you have to try to read the whole error message when it occurs. Sometimes however it does end up in the Log, but there doesn't seem to be any reason for this.

As for the issue itself, Optix renders can also be rather odd. One day they'll run fine, and then suddenly you run into these issues with half-completed renders that are only resolved by hiding certain elements (the geometry issue mentioned, probably) even when they worked fine before. Using the latest gaming drivers can also lead to some issues.

I'm having exactly this problem after upgrading video drivers. I can render just fine NOT using OPTIX now, but before the update, OPTIX worked.