So far so good...

[Birukas]

About biased render engines. Is it possible to accelerate them using cuda?

[radiance]

About biased render engines. Is it possible to accelerate them using cuda?

possibly, our philosophy is that most people prefer unbiased algorithms as they are quick and easy to use with no configuration and always the best result.
before octane, some artists prefer to use photon mapping, irradiance cacheing, etc to be able to render images faster, eg you don't have to wait hours and hours,
but with octane's speed I think this is not a problem anymore, unbiased rendering is now fast.

cached algorithms like photon mapping, lightcaching and irradiance caches are also more difficult to implement in the GPU as they need more memor, which is already small on GPU's and needed to store scene and texture data.
they also make implementation of spectral light calculations very difficult to implement.

So we're focusing on unbiased rendering algorithms for now, alongside directlighting and ambient occlusion if speed really is an issue.

Radiance

[samartin]

Here's another DM image you may want to use :-



The bottom 2 images are filtered using Noise Ninja. I let the samples run through to the default 2048 samples and I used 5 bounces. Came in at around the 11 min mark )

I really like this product. As for the irrad cache, yeah I know it's an unfair test but I thought it would be interesting to see what the quality looked like, I've always favoured modo's rendering, but I really don't think it can compete with un-biased rendering. To be fair I didn't spend a lot of time tweaking, but then that's where time can be eaten up, by setting up a good lighting rig along with all the other variables!

*edit*

BUG - One thing I did notice, I tried using custom res, typed 600 in W and then mistakingly typed 0600 in H and this killed Octane. My GFX card was then corrupting windows totally with random dots every where, I tried yet again and the same happened. I've also tried Square aspect 600x600 and it kills Octane.

[[gk]]

Are you pausing the render before changing resolution?
If not, do that, that solves close to all crashes Ive had regarding radical changes to the scene.

[radiance]

i recommend not changing the resolution for now at any time other than after you've just started octane and not loaded anything yet...
i'm nearly done fixing this bug (working on it now), it will be solved in the next release

nice images
what's your full name for the credits in the gallery ?

Radiance

[samartin]

samartin will suffice, I'm sure I'll be on the forum for a while

Oh one other thing I did notice, I set my res to 512x512, but when it came to cropping the screen, it ended up being 512x510. Not sure if this goes for all square aspect ratios.

[radiance]

samartin will suffice, I'm sure I'll be on the forum for a while

Oh one other thing I did notice, I set my res to 512x512, but when it came to cropping the screen, it ended up being 512x510. Not sure if this goes for all square aspect ratios.

yeah, this is something that's on my todo/bug list, i'll fix it for the next release.
it's best to keep resolutions in both axii as multiples of 32 for now.

Radiance

[samartin]

Here's another, I just love this setup, very intuitive.



Bravo on coding such an easy to use program which yields great rendering. Everything I've done is natively output, no level adjustments or anything done in post. I always do post work but I feel those days might not be needed so much anymore