[Solved] After re-install, rendering stops instantly

statistx_42556c1853

I had to reinstall everything, cause I suddenly got that PostSQE resource error and none of the solutions posted anywhere worked.

After re-installing everything looked fine again, but now when i tried to render my first scene, it basically starts to render and INSTANTLY stops at the first iterration as if it was finished.

I used render settings I used before, but maybe I'm missing some basic setting somewhere. The render window only shows a completely black scene and the render progress window closes as if it was finished.

I then checked the log and it says the following:

2019-08-04 22:06:16.942 WARNING: ..\..\..\..\..\src\pluginsource\DzIrayRender\dzneuraymgr.cpp(302): Iray ERROR - module:category(IRAY:RENDER):   1.0   IRAY   rend error: Cannot render: found no usable devices.
2019-08-04 22:06:16.950 Iray Render error: Invalid parameters (NULL pointer).
2019-08-04 22:06:17.073 Saved image: C:\Users\StatistX\AppData\Roaming\DAZ 3D\Studio4\temp\render\r.png
2019-08-04 22:06:17.081 Finished Rendering
2019-08-04 22:06:17.125 Total Rendering Time: 10.21 seconds

felis

If you look in your Render Setings > Advanced, does it then list your CPU and GPU?

Richard Haseltine

If this is DS 4.11.0.383 or DS 4.12.0.42 make sure your driver version is new enough. The requirements are given in the threads about the new versions' features in the Daz Studio Discussion forum

statistx_42556c1853

felis said:

If you look in your Render Setings > Advanced, does it then list your CPU and GPU?

It lists both and GPU is checked on both. CPU is unchecked, but I rendered just fine with those settings before the whole re-install.

If this is DS 4.11.0.383 or DS 4.12.0.42 make sure your driver version is new enough. The requirements are given in the threads about the new versions' features in the Daz Studio Discussion forum

It worked before on the same PC though, so I doubt it will work, but I'm updating everything and see if it works.

 

Update: Either the driver update (which is weird, since it worked with the same driver before) or the restart or whatever the weird computer gods decided, helped and it now works.