Iray no longer rendering
![SoulUnit](https://farnsworth-prod.uc.r.appspot.com/forums/uploads/userpics/949/nABBA55D22C39.jpg)
I have rendered an iray Marcoor scene on my previous computer with win 7 several months ago but upgraded to Win 10 and now iray render just shows a blank screen. 3dlight works fine but not iray. As a test I just loaded the Marcoor scene by itself and 1 camera but still nothing. I am using the iray scene.
I dont know that win 10 has anything to do with the problem, it is just the first time I have tried to open and render a scene since win 7.
I see I am not alone on this as other have posted but I have seen no soulution.
Any help would be appreciated.
Comments
Update turned on cpu and optix seems to be working now must have been a glitch
Now I am curious, why does this only work with CPU checked?
We dont' know, and can't shouldn't guess. All we know about your system is you are using Windows 10
Post you computer specs please; and include version of Daz. Any info can be helpful. No info provided is pointless.
Some things to check:
- am I using a Nvidia graphics card?
- is Graphics card selected as a render device?
As I'm using Windows 8, I've not kept up on the issues folks are having when they have W10; so can't help there if that is the issue.
Another possibility is that the Marcoor scene takes up too much graphics memory, so the render automatically falls back from the graphics card to the CPU.
Are you using the same materials for 3Delight and Iray renders? Iray tends to be more efficient if the materials are pre-converted to Iray; also, some materials don't auto-convert to Iray very well. That might make enough of a difference if the scene is marginal.
Is it just that scene or all? (load a cube, select GPU only under 'advanced' then try rendering).
If it's all iray renders, do you have the latest CUDA drivers installed for Win10?
(I ask because I was having the same problem in Win7 - 3Delight no worries, IRAY was CPU only), my GTX780 wasn't being used at all - I looked around, found the right drivers at NVIDIA's site and now it's working fine).