Skies Of iRadiance - Not Rendering?
Xenomorphine
Posts: 2,421
Skies Of iRadiance looked like just the thing I needed to create a range of different realistic-looking skies which phase into full-on night-time settings. Got the bundle, because that allowed me some beautiful day and sun-rise/sun-set effects, too.
So, I try testing it... Starship Vampire, I remembered, has Iray materials. I want to see how the lighting on these skies interact with proper metallic vehicles. But every time I try, DS crashes and leaves this message:
DAZStudio.exe caused ACCESS_VIOLATION at 0033:000000001A183E80
What could this mean? Is something wrong with Starship Vampire or is the new product bugged in some way? Even after restarting the computer and setting up a new scene, the same problem happens, but all other renders seem to be fine.

Comments
Starship Vampire is, as I recall, one of the items that triggers a known Iray bug. You can try rendering using only the GPU, I believe excluding the CPU is a workaround, or you can use the 4.9 beta which has an updated version of Iray that doesn't suffer the issue.
Yes, I have no problem rendering the vampire with the Skies of iRadiance, using only GPU. (render sample coming shortly)
Hah! Just unfortunate luck of the draw, then! Thanks for let me know.
Was able to remember that Remus 02 is another vehicle with Iray materials and it turns out that one's fine, which is a huge relief, as I have a lot of use for night skies with Iray.
Strange hearing that Starship Vampire has Iray problems after all this time, though. At least I now know there's a way to get around that.
Problem already solved, but here's two test renders. Interesting how different camera positioning effected render times (due to different lighting I suppose). The first one took some 15 minutes to render. The second one not even six. The ship is in the same place. Just rotated the camera around it.
Iray materials used and everything default. Only changed the opacity of the glass to not reveal there's no pilot in it.
[edit] - - (solved elsewhere)