Unable to enable GPU rendering Substance Stager 3.0.2

[Eva30185407y9r8]

In the new Substance Stager version 3.0.2 I've got the message: Unable to enable GPU rendering. I've updated my NVIDIA RTX 4000 to the latest drivers, Uses Windows 11. Nothing helps. Any suggestions what to try more? Rendering takes forever without GPU /Eva

[John37866685500z]

Having the exact same problem with the same graphics card but running Windows 10. Help desk was unable to resolve the issue so far. If you roll back to the previous installation that worked for us.

[rampion]

Hello, I have the same problem: ‘Unable to start the rendering engine’ on an RTX 4070 TI and Windows 10. I’ve updated the NVIDIA drivers and tried various solutions suggested on the Adobe forums for Stager… (Stager 3.0.2)

[AlanGilbertson]

You may know this already, but be sure that you're not using the Game-Ready driver. NVIDIA only tests the Studio drivers against graphic and 3D applications, and I've seen a number of problems cleared up by replacing a Game-Ready driver with the same version number Studio driver. 

[zarrdave]

Ditto. Exact same problem with the same graphics card, Win version and Stager version.

Wasnt happening in previous versions.

Frustrating when clients are on your back.

Tried all sorts of settings tweak combinations.
Anyone found a solution?

[Ares Hovhannesyan]

I use Asus Nvidia RTX 4060 without any problem with installed latest Game Drivers. Make clean install and reinstall Game Driver with GeForce Experience

[zarrdave]

I spent over a whole day trying various fix combinations on my RTX 4000 including the one you've suggested, but no luck. I think it must be the 4000 specifically thats the problem, or a combo of Win 11 and the 4000. Some are saying not to use the game driver, others say it works but on different cards. I've tried all of those options including removing hardware etc and plenty of re-starts in between. I've tried various combo settings in Nvidia Control panel too including creating a Stager program settings preset.

I've rolled back to previous version 2.1.4 now and no problems but lost newer features and benefits. Best compromise for now.

[Andrew A_]

At about the "stage"  to do / try likewise. It seems that RayTrace will work but using the CPU - in task manager the CPU looks to be doing most / all of the compute. The GPU is showing some VRAM usage and 3D [ expected] use. Thought it might be the latest GPU driver but the older driver did not help. At this page :

https://helpx.adobe.com/substance-3d-stager/common-issues/gpu-rendering-is-disabled.html#

I do not see this option:  Select the high performance NVIDIA processor as the option for preferred graphics program for Stager

in the Nvidia Control Panel.Stager does show as a program to customize.

[AlanGilbertson]

@Andrew A_ If you're on WIndows 11, you won't see that in the NVidia control panel. That control has moved to Settings, under System > Display > Graphics. Choose "Desktop Apps" and browse to add Stager. Under Options, select the GPU.

[Ares Hovhannesyan]

Not sure about this point but did you have "ON" Render GPU in Stager?

[Andrew A_]

Sorry, well yes, this would be "on" given working in the Render mode; but all was observed  in the Design mode. However, my lack of clarity and your response open another way to check on what "is going on". Right ? check to see what happens in Render mode.

[Andrew A_]

Thank you; good to know for when the move to Win 11 happens.

[Andrew A_]

I gave this a go, but still a no go. Gald it is working for your group and [maybe already known- if universally thje case] a file made in the new version did not [here] open in the older one.

[michaelk50823497]

Same Problem here. Quadro RTX 4000 is not recognized by Stager 3.0.2. Had to roll back to previous version.

Fix it, Adobe. We pay a lot for it. 😉

[christiane80624062]

Having the same issue here with a Quadro RTX 3000.

[michaelk50823497]

Stager UPDATE to 3.0.3 available on 27.08.2024 STILL DID NOT fix the problem.

Come on Adobe! Quadro RTX 4000 is not a toy graphicscard. Again I have to downgrade to Stager 2.1.4 to render my stuff. Thats so annoying for a payed app. Seems you don't even read your community threads. 😞

[Eva30185407y9r8]

Come on Adobe. This issue is still not solved, go backwards is not the future. We pay a lot for this program that doesn't work the way it should. Please find a solution soon.

[michaelk50823497]

FINALLY!!!

Version 3.0.4 fixed this problem und Stager finally works like a charm. ...and much faster. 

[rampion]

Still the same error for me in version 3.0.4 with the 4070 TI: 'Unable to start the rendering engine.'

[Andrew A_]

Ray Trace Mode is now working  here to. Howevre, for an animation if, after renering a numer of frames it seems to frezze. Will not ptoceed to rendenting the next frame?

[rampion]

After researching whether others had this issue, I was able to resolve it because my Windows username contained an accent. With a new Windows user profile without an accent, it works perfectly.

[michaelk50823497]

Interesting fact. ...or did you update and the change of username and the raytrace-fix is just a coincidence?

[zarrdave]

Interesting. Mine has been fixed since the update before last, & my windows profile doesnt contain any accents nor have I changed anything to do with it.

Are people still having this problem after updating?

[michaelk50823497]

Works perfectly since the 3.0.4 update. Today got the beta update to 3.1 ...hooooooly S!  ...and still with GPU Raytracing.

[Andrew A_]

As of 3.1.1.1 GPU Raytracing and animation [ output to vidio] are working fine. Also as an FYI for those where importing a Rhino 8 mosdel was an issue, R8 can now be directly imported. However, in my experince, importing as an STL works better still. The mesh can remain in a Rhino 8 file, just simpimply go from NURBS>ST first. Also perhaps check that you are happy with the mesh befoe import. I found a suboptimal mesh area in a model but did not notice until after I had imported the STL model into Stager. Obtained what appeared to be some abberant render artifacts, but the cause was this off mesh area.