A PHP Error was encountered

Severity: Notice

Message: Only variable references should be returned by reference

Filename: core/Common.php

Line Number: 242

A PHP Error was encountered

Severity: 8192

Message: Non-static method Low_search_model::load_models() should not be called statically, assuming $this from incompatible context

Filename: low_search/base.low_search.php

Line Number: 279

A PHP Error was encountered

Severity: Notice

Message: Undefined property: Channel_images_model::$LOCS

Filename: models/channel_images_model.php

Line Number: 540

A PHP Error was encountered

Severity: 8192

Message: Non-static method Low_search_model::load_models() should not be called statically, assuming $this from incompatible context

Filename: low_search/base.low_search.php

Line Number: 279

A PHP Error was encountered

Severity: 8192

Message: Non-static method pxutils::usage() should not be called statically, assuming $this from incompatible context

Filename: pxutils/pi.pxutils.php

Line Number: 9

A PHP Error was encountered

Severity: 8192

Message: Non-static method Extract_URL::usage() should not be called statically, assuming $this from incompatible context

Filename: extract_url/pi.extract_url.php

Line Number: 11

A PHP Error was encountered

Severity: 8192

Message: Non-static method Hj_social_bookmarks::usage() should not be called statically, assuming $this from incompatible context

Filename: hj_social_bookmarks/pi.hj_social_bookmarks.php

Line Number: 19

A PHP Error was encountered

Severity: 8192

Message: Non-static method Comment::form() should not be called statically, assuming $this from incompatible context

Filename: libraries/Template.php

Line Number: 2994

A PHP Error was encountered

Severity: 8192

Message: Non-static method Low_search_model::load_models() should not be called statically, assuming $this from incompatible context

Filename: low_search/base.low_search.php

Line Number: 279

A PHP Error was encountered

Severity: 8192

Message: Non-static method Char_limit::usage() should not be called statically, assuming $this from incompatible context

Filename: char_limit/pi.char_limit.php

Line Number: 10

A PHP Error was encountered

Severity: 8192

Message: Non-static method Low_replace::usage() should not be called statically, assuming $this from incompatible context

Filename: low_replace/pi.low_replace.php

Line Number: 12

A PHP Error was encountered

Severity: 8192

Message: Non-static method Mf_google_analytics::usage() should not be called statically, assuming $this from incompatible context

Filename: mf_google_analytics/pi.mf_google_analytics.php

Line Number: 9

A PHP Error was encountered

Severity: Warning

Message: Cannot modify header information - headers already sent by (output started at /usr/www/clustr.com/sys/codeigniter/system/core/Exceptions.php:170)

Filename: core/Common.php

Line Number: 412

Why iRay? | Clustr

In order to post any news you must be logged in!

Why iRay?

Published:  May 01, 2011    Category:  3D Graphics, Design, General    Published by:  GriT  
Rendering Guru Jeff Patton gives us a comprehensive look at on why you should consider your rendering options using iRay, especially for those who specialize in product visualization. Complete with comparative materials, rendering settings and time output.

From jeffpatton.net:
"I’ve been getting peppered with emails, PM’s, facebook messages, smoke signals, you name it about why I’d use iray and/or why anyone else should. Well, it’s just another digital tool in our ever growing software toolbox. While I was eating supper tonight I prepared a few examples showing what I feel are benefits to iray. Read on for more…

Why have I started using iray so much lately? Well, for me and the projects that I’ve been working on lately it’s been pretty useful and can provide some great results. Yes, there are some restrictions/limitations to deal with but IMHO it’s quite useable for the product-vis and to some degree the architectural-vis communities. I hesitate on the architectural-vis side of things because typically architectural interiors can be quite time consuming to render with path-tracer type applications.

This holds especially true on interiors illuminated by a few small light sources or small windows. You’d have to give iray a lot of fast hardware at a scenario like that in order to achieve decent render times. Architectural exteriors are usually pretty good with path-tracer type applications. You get more light/bounced light in areas in a more efficient/faster manner than on an interior.

Character renders will be difficult with iray since currently there isn’t support for a Sub-Surface-Scattering material. So if you’re a character person, you will not be as pleased with iray. Likewise VFX artists will not find it very helpful as it lacks volumetric support at least at this time as well as the general inability to “cheat” things as you can with other rendering applications."
Source:  Jeff Patton      Share:    Views: 2221

 
   

There are no comments for this entry yet.

In order to post any comment you must be logged in!