IRay interactive - nothing rendered
![marble](https://farnsworth-prod.uc.r.appspot.com/forums/uploads/userpics/488/n8P2SPAXVTBEI.png)
I have only just tried this for the first time since the DAZ Studio update to 4.9.2.70. I can use IRay Interactive mode in the viewport but if I try to render to a window in interactive mode - nothing happens. A window pops up and asks me if I want to save but nothing has been rendered.
Photoreal mode works just fine. I have the GTX970 selected for both Photoreal and Interactive in the Advanced settings. As I say, it works in teh Viewport and in the Aux viewport but I wanted to try an animation and I get nothing.
EDIT: If I open the timeline pane with the viewport in Interactive Draw, the scene switches to untextured (grey) and I get an endless (10 minutes, so far) "Preparing Scene" progress bar.
Post edited by marble on
Comments
Just rebooted and tried rendering to a window in Interactive mode and this time it was completely black. When I closed the render window, the viewport had retruned to untextured (grey) and stayed like that.
EDIT: Just tried with a simple scene - one G2F figure. No problems.Seems to be related to the complexity of the scene but memory isn't a problem for that scene in Photoreal mode.
This is the log. I started from fresh with the scene that has been failing. First try at Interactive worked. Second try failed - log says no memory.
Curiouser and curiouser - I put the same characters in another scene with more content, more clothing, furniture, etc. and that renders in both photoreal and interactive (and I have tried successive renders in case it was a problem of the VRAM not being cleared between renders).I have no clue as to why the first scene is failing.
In no particular order:
1. Be sure you're not using mesh lighting. Interactive won't work with it.
2. Devices are independently set in the Advanced tab for Photoreal and Interactive.
3. It could be a shader or geometry that's crashing the scene for Interactive. A simple scene test (as you've done) can help answer that one.
4. Try rebooting your PC from a cold start. Drivers can sometimes get hung up.
i have this all the time with interactive
and i know all things tobor says
aux viewport renders but main black
restarting daz most of the times let it work again
theres something really wrong in 4.9 with rendering
Thanks, both.
@Tobor - 1&2 were checked. As for 3 - I tried a simple scene and an even more complex scene and both rendered fine. The more complex scene contained all of the content of the failing scene plus more. Go figure. I did reboot several times but the failing scene continued to fail.
@Ruphuss - I'm relieved that someone else has seen this. I was beginning to suspect my NVidia card again and I've just had the original one replaced under warranty.
To verify if it's card related, be sure to leave CPU checked as one of the rendering devices. If the card(s) fail, you should still have fallback to the CPU. I have occasionally run into this as well, and the problem only affectd rendering on the graphics card. The scene rendered (eventually) to completion using only the CPU. It was solved by rebuilding the scene from scratch. I have no idea what element, or elements, have caused it. In all the times, though, I was converting older V4 and Poser content.
If you still get black renders even with CPU, then I'd file a bug report with Daz. They'll probably ask you to send the scene file.
Lol, I don't think DAZ support would appreciate my subject matter (or perhaps they might). Anyhow, what you say about the CPU fall-back makes sense. That's how I knew the original card was faulty. Also, what you say about building a new scene appears to be my experience too, as I mentioned above (come to think of it, I'm using a converted M4 skin on G2M). I hope there is a bug fix in the next release as it seems to be something that has happened to others.
rendered image series with interactive mode
renders as long theres ram left then renders black
image rendering with interactive is broken due to ram management
this is not the case with photoreal
Yeah - I've tried some more today. Very hit and miss with interactive. I have had to reboot a few times to get the same scene to render - and I agree that it seems like memory management. Something is broken.
Is there a reason you're rendering in Interactive? Control of shadows or AO?
Just as a matter of comment, Interactive has some limits on number of lights, textures, and other scene elements. I wouldn't think the render would just stop if you exceeded these limits, but you never know.
I'm trying to create an image series for an animation. Interactive seems to be much quicker than Photoreal. The scenes are pretty minimal in terms of lights and props, etc.
for testrenders
they are quick
and it always worked before so must be a 4.9 thing
Windows 10. 64-bit I had been using 4.9.2.70 with an EVGA 1060 - Interactive worked for several weeks as I futzed with some settings off and on. Then I tried a real render. Wasn't satisfied with speed but when I went back to interactive got this...
016-18-06 09:18:56.905 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER): 1.0 IRT rend error: failed to estimate required local memory per kernel launch
which was quickly followed by
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER): 1.3 IRT rend error: failed to load: device kernel image is invalid
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER): 1.3 IRT rend error: Kernel linking failed
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER): 1.0 IRT rend warn : A device failed during rendering
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER): 1.0 IRT rend error: Cannot render: device failed.
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray ERROR - module:category(IRT:RENDER): 1.0 IRT rend error: Failed on first frame. Dropping failing devices and re-rendering
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER): 1.0 IRT rend warn : All devices disabled.
2016-55-06 08:55:15.539 WARNING: dzneuraymgr.cpp(261): Iray WARNING - module:category(IRT:RENDER): 1.0 IRT rend warn : There are no devices that can be used with IRT (Compute Capability 2.0 required)
2016-55-06 08:55:15.539 Iray INFO - module:category(IRT:RENDER): 1.0 IRT rend info : -------------------------------------------------
Which is not what I had expected. As the CPU has no chance whatsoever of doing this (it is a not blindingly fast old quad-core) I am somewhat DIW . Not sure what happened with this driver. It seems to have worked until I tried to switch it or that could be coincidence.. I have no trouble with other programs which all do rely on the card, though not in the same way. Apparently have to go back to 3delight.
Wish they'd come up with something that used the cudas to just go really damned fast with 3delight quality (the OpenGL isn't useful as it stands) and the heck with photoreal.
One does hope that they get a handle on this quickly.
I should note that the card DOES work just fine in opengl. Opengl just gives problematical results in respect to lighting and the like.
Since the last two Updates to 4.9 Public Build Beta, I cannot render anything anymore. The Viewport is not reacting and it keeps saying "Preparing scene". If I start a normal render, it only renders black. My 4.8 installation still works fine and renders as usual. Tryed to deinstall and reinstall a few times but no luck. Any suggestions?
The build you are using does not support the 10x0 series cards...
System specs, please...
Wound up getting it back. Had the brainstorm that if it had worked with scenes that had been done initially with the combo of CPU and GPU that conceivably it was relying on the CPU to do some of the meta-information loading the scene into memory and working out how big it was.
Went and restarted with both devices present and all seems to be working as-was. I had thought the slow old 4-core CPU I have was slowing it down, but it was doing just fine using interactive, so I'll just leave it ticked on and leave it for my Christmas Prezzy to deal with any speed issues.
So far that's my story and I'm sticking with it ... unless it turns out to be POM (phase-of-moon) dependent :-)
I do wish that 3Delight had the ability to use its more rudimentary but for my purposes satisfactory methods to get fast and acceptable renders out. Photorealism is overrated when you want flat-out speed to do any sort of animation. Primitive but FAST. Lord give me patience, but I want it RIGHT NOW!!! :-)
Thanks...
Since the last two Updates to 4.9 Public Build Beta, I cannot render anything anymore. The Viewport is not reacting and it keeps saying "Preparing scene". If I start a normal render, it only renders black. My 4.8 installation still works fine and renders as usual. Tryed to deinstall and reinstall a few times but no luck. Any suggestions?
System Specs:
Windows 7 Home Premium
i7-4771 CPU 3,50 GHz
16 GB RAM
Grafic nVidia GeForce GTX 970
DAZ3D 4.9.3.128 Pro Edition (64-bit) Public Build
Have you installed the DS Essentials for the Beta?
As long as the content directories match you should not need to install content separately for each version.
What's the driver version for your GPU? The public beta requires 368 or higher.
Yes, I have everything installed. Here the driver version:
Nvidia driver version...
The video card driver -- Control Panel > NVIDIA Control Panel > click "System Information" in the lower left.
It says 353.30
Just installed 375.70 it works now! Thank you!