I'm one of the lucky few who has an Ampere based Nvidia RTX 3090 from the task manager it is pretty obvious that all renders goes to my CPU. Even the message log confirms that It's kind of annoying since cycles/superfly works perfectly in Blender

In Poser 11 rendering using my 1080Ti

The 3090 isn't supported in Poser 11, so I had hoped it would have been supported in Poser 12. but everything goes to the CPU for some reason

Due to the scarcity of the Nvidia 3000 series graphics cards we've been unable to test their compatibility. We've had user reports that there are compatibility issues. We will resolve these as soon as we can acquire cards to test with.

Thank you,

Brian, Poser 12 QA tester.

Perfect.. Thank you for the quick answer. I know as a first mover.. and in some way s both lucky and unlucky :-)

Maybe I should join the beta test program?

Cheers!

You will need to go through the NDA process. Please send me your name and a brief summary of your experience with Poser to brian@posersoftware.com. Thanks and best regards, _Brian

It's not just the 3000 series. I have an RTX 2080 Super and I have exactly the same symptom. Doesn't matter whether I pick the GPU or the Optix:GPU (not sure which I should be using?). It also doesn't matter whether I render in Poser or use the Queue manager.

In Poser 11, I had this problem if I rendered a multiframe animation directly in Poser, it always used the CPU. But in Poser 11, single frame renders worked fine, and animations were also fine if I sent them to the Queue manager. Now in 12, it's all CPU.

Just a little word about nvidia cards: I have a GeForce RTX 2080Ti and it works like a charm, in both modes:

And it faster in OptiX mode. BUT: i used to have an old setting that was still checked: "Separate process" render. Uncheck this if you intend to use your GPU... Don't know if it's a bug but when it's checked, it uses the GPU as well, but at max 6-7% of its speed... And for what I understand, I'm not sure it's useful with a 64bits OS...

Oh, interesting. I had that checked. After unchecking it, the single frame render directly in Poser did use the GPU. Have not tested the multiframe methods yet.

That's kind of annoying, because I do still use Firefly as well and it improves performance there. It would be better if Superfly just ignored that setting, so I don't have to go into the general preferences each time I switch (which I am guaranteed to forget).

Thanks to you Y-Phil I've gotten a bit further

You cant use render in background either, but render now and the 1080Ti works. Trying to render with render now and the 3090 results in poser crashing and closing down by itself.

Here's a table

Rendering in background using the 1080TI works fine in Poser 11 Pro

ChromeStar posted at 9:32PM Tue, 03 November 2020 - #4403057

Oh, interesting. I had that checked. After unchecking it, the single frame render directly in Poser did use the GPU. Have not tested the multiframe methods yet.

That's kind of annoying, because I do still use Firefly as well and it improves performance there. It would be better if Superfly just ignored that setting, so I don't have to go into the general preferences each time I switch (which I am guaranteed to forget).

Rendering in a separate process was interesting at the time of 32bits, because of memory limits, for what I understand. I still think that this setting is useless in a 64bits OS, because the only limit is the free space disk, as the system swaps in case. I don't know for other OSes, but win10 can even compress parts of what is in RAM but not frequently used, to artificially increase the available memory.

Separate process is still needed because some of us like to work on scenes while the renderer is chugging away in the background.

ssgbryan posted at 8:29AM Wed, 04 November 2020 - #4403167

Separate process is still needed because some of us like to work on scenes while the renderer is chugging away in the background.

I understand but still don't understand... I mean: i can render using the GPU in the background, with the checkmark unchecked. In this case, the use of the GPU doesn't get over 6-7%, meaning that it will take 15-16x more time.

It seems a little erratic. When I unchecked the same box today in Poser 11, now even when I render multiframe scenes via the Queue manager (i.e. in the background), they are using the CPU (despite selecting the GPU). Worse, when I check the box again, it doesn't fix it. Not sure what is going on there, but I think it's fair to say there are some issues with this setting and it might not always do what it logically should.

Ok, revisiting these issues. I currently have "separate processes" unchecked. Single and multiframe Superfly renders within Poser 12 correctly use the GPU. Multiframe renders using the Queue Manager, however, incorrectly use the CPU. Are other people seeing that as well? Has anyone else tried the Queue Manager with Superfly?

As noted above, this is on an NVIDIA 2080 Super. I'm currently using the Optix option, don't know whether that is relevant. I'll try some other tests after the current renders finish.

I can try Queue Manager in Poser 12 if does use GPU like with OptiX or just normal with CUDA, can you please check Notifications if there are not errors, be sure you are not using Ambient Occlusion(usually you will find them in older shaders), if Ambient Occlusion is in the shaders usually it will trigger CUDA error and SuperFly won't render that

Hope this helps

Thanks, Jura

No errors in the message log. But I also don't see any messages about the render status, cancelling renders, etc when I am using the Queue renderer. So I'm not sure they would show up there...? I do notice there is a very brief blip of CUDA activity right at the start, which goes away and the CPU activity jumps to near 100%. So that is probably consistent with something going wrong in the GPU render and aborting to CPU, but no hints about what.

I checked the main figures in the scene for ambient occlusion nodes, and there aren't any. I haven't checked every single object but, given that Superfly is working fine when I render in Poser itself, that doesn't seem likely. I did search the pz3 for the word "occlusion" and not get anything relevant, not certain that would have caught any though.

I do have the same problem (CPU rendering) if I do a single render using either "Render to Queue" or "Send Render to/Queue". It's not specific to multiframe rendering or movies.

I tried using the non-Optix option (which I guess is CUDA?), and that doesn't make any difference. (Seems slower though...) Still uses the CPU if I render from the Queue manager.

Is anyone else trying the queue manager? Can you get GPU renders using it?

Hi @ChromeStar

I just tried QM and render with GPUs with QM and as you said,seems Poser QM doesn't use GPUs at all,only CPU,tried CUDA and OptiX and it won't make any difference.

Thaks,Jura

DefaultGuy posted at 2:52PM Fri, 13 November 2020 - #4402815

Due to the scarcity of the Nvidia 3000 series graphics cards we've been unable to test their compatibility. We've had user reports that there are compatibility issues. We will resolve these as soon as we can acquire cards to test with.

Thank you,

Brian, Poser 12 QA tester.

I am a little surprised.I have Poser Pro 11.2. I was going to do a upgrade but now I have to clear the situation. I was very happy to hear Poser 12 release date. But now...... Because when I read the news on "posersoftware.com" it is written "OptiX, which utilizes the hardware ray-tracing capabilities of Nvidia's Turing architecture & Ampere architecture;"..........Place display text here

I want to buy also a new RTX 3080 card.But now I am not sure the "Ampere" architecture is supported.Because this page telling:yes.Or maybe I wrong?

Hi Wilks. Save your money for now. My RTX 3090 with its 24 Gb of vRAM does not work in poser. I haven't tried the 3080, but I think it will be the same problem. In fact rendering in the background using the GPU seems to be an impossibility at the moment.

I'm trying to join the Beta testing program so I can help getting support for the 30xx series ASAP.

Not for now,RTX3xxx series are not supported but hopefully they will release update soon but for now Turning is latest Nvidia which is supported guys

Hope this helps

Thanks,Jura

I do wish Bondware would step up with AMD cards.

An RX6800 will have 16Gb of ram and have an MSRP of $579.

With that I agree there, I really hope SuperFly2 will be supporting AMD GPUs I will have here for testing 6800XT or 6900XT and let's see how they will perform

Thanks, Jura

Looks like AMD card support not in the immediate future according to Nerd3D on the webinar.

--- posted at 7:23AM Fri, 27 November 2020 - #4404603

Hi Wilks. Save your money for now. My RTX 3090 with its 24 Gb of vRAM does not work in poser. I haven't tried the 3080, but I think it will be the same problem. In fact rendering in the background using the GPU seems to be an impossibility at the moment.

I'm trying to join the Beta testing program so I can help getting support for the 30xx series ASAP.

Hello guys.

Thanks for the advice.I hope that 30 series cards will get supported in following year.

oh no just bought rtx 3070 card , will they update or not

They updated to use 30XX cards a week or so ago.

thank you will buy poser 12 now. whew..............

Confirmed - I updated to the version they put out two days ago, and now it works on my RTX 3070. (As seen here: https://www.renderosity.com/rr/mod/forumpro/?thread_id=2956045 )

There are still some oddities, like the Progressive Refinement only works on Render and not on Render in Background (in which case it only shows anything of the render when it's complete) but that's not a showstopper as it seems that render cancelling works correctly now without crashing the program, so I don't need to rely on Render in Background for my progressive refinement renders.