HOME | DD
SuperBoomTurbo β Low Rent Recon
Published: 2019-07-03 02:33:36 +0000 UTC; Views: 756; Favourites: 20; Downloads: 0
Redirect to original
Description
With all the Cyberpunk 2077 news, I've been in the mood. Voila!ΒIray render 83 minutes.Β
Related content
Comments: 10
It's an amazing Cyberpunk scene! Β
84 minutes iray render with a lot of stuff on the scene, you have a turbo XXL computer!Β
π: 1 β©: 1
π: 0 β©: 1
I agree with you, time is killing GPU and computer spares.
There is a trick for iray and 3delight to spare time, maybe you know it? Resize all of your props and characters to 10% or 15% instead of the basic 100%, it's fast rendering especially when you work on iray. I do that with my 3delight and OpenGl for a year, my dying laptop keeps running thanks that.
π: 0 β©: 1
I hadn't heard of that but I'd sure like to give it a shot! The last physically based renderer I used, Luxrender, was very finicky about the scale of objects, so much so that if it deemed a figure or a background building to be out of scale with something else in the scene, it would gravitate the light towards one particular object and throw off the results. Granted that was many years ago, but it comes to mind quite frequently when doing these big scenes where I have or tend to change up the buildings, particularly like this one where the background cityscape is exceptionally smaller than the base mesh's 'normal' size.Β
π: 0 β©: 1
You're right, it's big concern, that's a big problem with iray, sometimes there is like grain on the render, that's one of the reasons I give up the Iray, I'm not good on Iray.
There is another trick you can use on Iray render. For example, your scene includes a room fully furnished at the center your character, you can hide all of the pieces of furniture off-camera to reduce the render time. Β
π: 0 β©: 1
My goodness, apologies for the late reply. I've gotten into the habit of getting rather extreme with my non-essential polys and either removing whatever isn't directly in the camera or deleting sections to whatever is critical. The polygons aren't really the base of the problem, but the attached textures that suck up all the RAM. I try to curb my really big scenes to a max headroom of about 3.2 million polys of physical geometry for the whole scene and have gotten respectable render times that way, and also by downgrading texture sizes where I can. If it's really in focus and I haven't altered the geometry already, I've also gotten into the habit of retexturing whole sets either to make older content more presentable or maximizing render time with more economical textures. A lot of the community who hasn't worked within a single PC's capability with GPU rendering will really use some exceptionally large texture sizes that are massive resource hogs. Just for example, I can make a normal map in PNG just as detail-oriented come in at 6-8mb as a TIFF or other format that comes in at 30-50mb, just for one map. That's a lot of real estate to trade. Or I can cook up rough, reflective, metallic and refractive maps for a really nice piece, with Iray's plentiful image channels, that can really showcase the right asset.Β
Anyway, not throwing out bragging rights or anything. I'm sure you're in the same boat and walk the talk, too. 
π: 0 β©: 1
No problem with the reply.Β
I've always found amazing how artists like you and many others can work with Iray, all of you've written in your last post comfort me in my choice to focus on 3delight and BasicOpenGL, Iray is a huge workΒ
With your amazing render I see how I'm far from great artists.Β
π: 0 β©: 0
Thank you! One of these days I'll have to get over my qualm about doing layer renders and really fill stuff like this in with tons of peds and things.Β
π: 0 β©: 1
UR WelcomedΒ
π: 0 β©: 0