Optional Biasing

Generic forum to discuss Octane Render, post ideas and suggest improvements.
Forum rules
Please add your OS and Hardware Configuration in your signature, it makes it easier for us to help you analyze problems. Example: Win 7 64 | Geforce GTX680 | i7 3770 | 16GB
gueoct
Licensed Customer
Posts: 402
Joined: Mon Jul 11, 2011 3:10 pm

I don´t know, if this has been discussed before:

Unbiased is all well and good, but have you ever thought about
offering Optional Biasing to give the possibilty to speed up rendering if needed?

Especially for interior shots, where grain is an omnipresent problem this could be an
option to choose speed over super-correct unbiased and slow render progress...
Last edited by gueoct on Thu Jun 26, 2014 10:53 am, edited 1 time in total.
Intel i7-970 @3,20 GHz / 24 GB RAM / 3 x EVGA GTX 580 - 3GB
User avatar
Refracty
Licensed Customer
Posts: 1599
Joined: Wed Dec 01, 2010 6:42 pm
Location: 3D-Visualisierung Köln
Contact:

What about the Direct Lighting Kernel ?
Stahlwolle
Licensed Customer
Posts: 68
Joined: Sat May 19, 2012 9:36 am
Location: Cologne, Germany

the DL Channel offers sufficient quality only in the diffuse mode and thats nearly slow as Pathtracing which offers better quality.
but for professional interior rendering both are way too slow. i think speed is not the main argument for the usage of octane.
it renders up to 50 times faster than cpu based unbiased renderers, hm - maybe. but for some certain reasons in big and complex scenes the biased render-engines are in advance - they are adaptive! so yes, octane can render same quality like e.g. vray even in interior-renderings, but needs much much much more time to reach same smoothness and quality. for product-studio-shots octane is much better than vray (in my opinion) and offers a workflow much closer to the output but dont expect octane to be a solution for everything by now... would be great if there s a way to build in some adpativeness into octane!
i7 3930K 6x3.2GHz | 32GB | ASUS Rampage Extreme iv | Geforce Titan + Geforce 780 ti | 1200W PSU
gueoct
Licensed Customer
Posts: 402
Joined: Mon Jul 11, 2011 3:10 pm

Stahlwolle wrote:the DL Channel offers sufficient quality only in the diffuse mode and thats nearly slow as Pathtracing which offers better quality. but for professional interior rendering both are way too slow.
Sad but true.
Stahlwolle wrote:i think speed is not the main argument for the usage of octane.
what is it then?
Stahlwolle wrote:it renders up to 50 times faster than cpu based unbiased renderers, hm - maybe.
Have you ever tried Corona?
Stahlwolle wrote:so yes, octane can render same quality like e.g. vray even in interior-renderings, but needs much much much more time to reach same smoothness and quality.
That´s why i am asking
Stahlwolle wrote:for product-studio-shots octane is much better than vray (in my opinion
Definitely!
Stahlwolle wrote:would be great if there s a way to build in some adpativeness into octane!
That´s exactly what i meant!
Intel i7-970 @3,20 GHz / 24 GB RAM / 3 x EVGA GTX 580 - 3GB
gueoct
Licensed Customer
Posts: 402
Joined: Mon Jul 11, 2011 3:10 pm

Refracty wrote:What about the Direct Lighting Kernel ?
Not really an option. it´s maybe 25% faster but does not give the same result...
Intel i7-970 @3,20 GHz / 24 GB RAM / 3 x EVGA GTX 580 - 3GB
Stahlwolle
Licensed Customer
Posts: 68
Joined: Sat May 19, 2012 9:36 am
Location: Cologne, Germany

hey,

i think the main reason for using octane should be the posibility to work very close to the output and archive a phantastic result by an very-easy-to-use renderengine. but you should not forget that the phantastic result comes due the lack of adaptiveness.
Compared to e.g. vray you can learn octane in a fraction of time and archieve results better than vray. but only in that cases for which the renderpower of octane is sufficient. and if you dont got 100 connected titan gtx the power of octane is not sufficient for very complex renders in big scale (like interiors) by now.
i7 3930K 6x3.2GHz | 32GB | ASUS Rampage Extreme iv | Geforce Titan + Geforce 780 ti | 1200W PSU
Vue2Octane
Licensed Customer
Posts: 88
Joined: Thu Jun 26, 2014 8:16 am

Adding a biased option might also be a major task, because it probably means rewriting the render engime in major parts. Not sure how easy or difficult it is to simply 'ramp down', an unbiased engine to a biased engine.
User avatar
Seekerfinder
Licensed Customer
Posts: 1600
Joined: Tue Jan 04, 2011 11:34 am

Somehow I don't think it's Octane's DNA.

I'd rather they focus efforts on regaining some of the speed we lost over the last year due to the new features.

If you want biased GPU, there's Redshift (for MAX - EDIT: Maya and Softimage... thanks Riggles)

Best,
Seeker
Last edited by Seekerfinder on Thu Jun 26, 2014 7:26 pm, edited 1 time in total.
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane
riggles
Licensed Customer
Posts: 493
Joined: Mon Feb 17, 2014 3:34 pm
Location: CT, USA

Having a biased option sounds nice, but typically comes with its own cost. Notably, simplicity. Now you need to have more granular control over sampling on an item or shader level to optimize for quality and speed. Same goes for GI controls.

They are two different approaches, and frankly I think it's easier for a biased renderer (which already utilizes brute-force methods) to include a pseudo-unbiased mode than for a purely unbiased renderer to included a biased option. And I'd rather the OTOY dev team focus on making the existing unbiased algorithms faster than try and rewrite their rendering engine to include a biased system.

If you're interested in biased GPU rendering, you might check out https://www.redshift3d.com — it's only available for Maya and Softimage currently.
Stahlwolle
Licensed Customer
Posts: 68
Joined: Sat May 19, 2012 9:36 am
Location: Cologne, Germany

Agree, but i wish there were a feature like "region-Painting" where you could after renderstop paint over some areas and the render engine just renders those painted/marked pixels - like region render just with an paintable mask and the continue-render option. that would be great cause you could focus the render onto the hard to render spots manually and focus the power to the spots where its needed. that would be a manual bias :)
i7 3930K 6x3.2GHz | 32GB | ASUS Rampage Extreme iv | Geforce Titan + Geforce 780 ti | 1200W PSU
Post Reply

Return to “General Discussion”