|
Description
Renderman is a well documented API with several, very good GPL as well as commercial standalone rendering systems available. It would be nice if Blender could talk with Renderman more eloquently complete with RM shader support, perhaps a "Renderman" tab could appear in the materials editor when a Renderman engine is selected.
A lot of Blender->RM Shader support has already been spearheaded with RIBmosaic. I'd like to see RM more tightly integrated along side Blender Render and Yafray.
The more options the better, and the fastest way to create those options would be Renderman integration.
Attachments
No attachments.
Duplicates
Comments
|
Cessen wrote on the 12 May 08 at 23:16
|
While I agree that Renderman integration would be a boon, it would need to be very well thought-out. Renderman's benefits aren't just its surface/displacement shaders, but also its light, volume, and image shaders, as well as numerous other flexibilities.
As a fairly technical user, I wouldn't want to miss out on those capabilities. But I also wouldn't want less technical users to be forced to deal with the complexities of Renderman just to take advantage of external renderers.
Lastly, it seems like this would be best dealt with as part of a broader render api.
|
|
wayneberry wrote on the 13 May 08 at 02:29
|
to be honest, i don't see why renderman is that great...
it is a raytrace / scanline hybrid as is blenders internal rendering engine...
i'd rather developers spend time on adding the (few) features the internal engine doesn't have compared to renderman than working on integration.....
but that's just me, i spose it would make blender look good to the commercial environment if it had seamless renderman integration... (and what about mentalray?)
|
|
madmesh wrote on the 15 May 08 at 00:42
|
A good renderman intergration would be great if it supported al the Blender features. An intergration similar to Yafray would be very good.
If an integration is possible to the degree of accurately rendering particles, the shader node system, dupliverts and every dirty trick you can pull in Blender i'm al for it.
|
|
Cessen wrote on the 15 May 08 at 11:59
|
@wayneberry:
Renderman is not a particular piece of rendering software. You are likely thinking of Pixar's RenderMan (or PRMan for short), which is Pixar's rendering software.
What we're talking about is the RenderMan interface specification as can be found here:
https://renderman.pixar.com/products/rispec/index.htm
Renderman support in Blender would allow Blender users to use *any* Renderman compliant renderer, of which there are quite a few, including some good open source renderers.
@madmesh:
While I do think integrating well with Blender's feature set is important, I'm actually more concerned with being able to do every dirty little trick that *RenderMan* allows (which I needn't point out are a lot more robust and flexible than Blender's rendering tricks). Although taking advantage of such things would likely fall to more technical users.
|
|
foreward wrote on the 23 May 08 at 11:45
|
Hi all,
I agree with most that is said here.
Cessen:
I think that would be great, but, I also think that flexibility in the way ribMOSAIC is necessary, but without such a large overhead technically (whiterabbit: don't get me wrong, your product is a HUGE leap forward)
The renderman UI could be user extendable, similar to, but perhaps easier than, the current ribMOSAIC "code fragment" approach, allowing folks to "plug-in" and extend the interface without complete overhaul.
Obviously, basic blender and RM features should come "out of the box"
@wayneberry:
I also agree that the internal renderer should remain priority. However, there is no way that Blender will have all the same strengths (and weaknesses for that matter) of every renderer for EVERY situation.
For most things, Yafray and Blender Render work great. However, for other things, not so much and new features are constantly being discovered and implemented. There is no way that any one renderer can implement ALL technologies.
For this reason, Blender should be as flexible as possible and allow it's users access to as many rendering options as possible so that the user can choose which rendering option is best for his or her application.
The fastest way to provide these options is with existing well known standards, such as Renderman RIB.
Cessen:
I also agree. Integration would need to be seamless and as few as possible features should be left out.
However, I needn't remind you that even Yafray integration isn't perfect, and 100% perfect integration, albeit more likely with renderman than Yafray, isn't likely realistic.
|
Post your comment
|
