absorption

#21

Yeah, it’s pretty crazy. Look in the Render window and watch the Geometry Cache bloat to obscene levels as you render displacements. I don’t mean to criticize it — I’m sure it’s using as much as it needs to — but wow. I’ve only got 2 GB of RAM on my machine, so it can get a little scary sometimes, and on my girlfriend’s 1 GB MacBook you can forget it unless you go in and isolate the displacement to only the essential polygons (which can be a pain).

EI’s bump-maps really are fantastic. Unless you get super close they look almost as good as displacements. Obviously there’s things you can’t do that you need displacements for, but I was just appalled by modo’s bump-mapping. I don’t even bother trying them anymore they look so poor; I just automatically switch the channel to Displacement. And happily the displacement quality is great if you’ve got the RAM.

#22

Holy cow, I just noticed you said 6000x4800! I’ve never rendered anything even approaching that size.

#23

Hi Paul, how far can you go size wise with Rhino/Brazil combi. With EI, I’m not surprised you dont have memory issues with largish images as you mostly are using procedurals.

Martin K

#24

I’m not sure with Brazil4Rhino - a few versions back the largest I could go on one project was roughly 3000 X 2400 but there have been some changes since.

My technique with different 3D apps doesn’t really change much so I’m not sure of the point you are making:-) Yes, EI handles procedurals very well.

#25

No point other than using procedurals takes less memory that using a lot of bitmap textures.
I’ve occasionally had to render very large images and one soon seems to run out of memory when you’re getting up to the 4500 pixel wide, what with the size of bitmap required and the necessary denser mesh. I was curious about the Rhino/Brazil combination and how far it would go size wise.

Martin K

#26

I’ll let you know on the Brazil/Rhino size once the beta is over…which should be quite soon.

The Rhino crowd is a bit of a different crowd…for the most part, a one button click is what many want a render engine to be. They want very, very simple but with great output:-)

Seems Brazil has gotten it’s share of “it’s too complex” from many users though I can get a great looking image out of it with about 5-6 clicks. It’s pretty simple but might be a little more than most want. I hope it does well as it deserves to - great render and makes using Rhino a complete joy.

I’m completely sold on having a half-decent rendering engine in one’s modeler.

#27

Yes, I have the beta, but haven’t tried it yet- it’s the time thing. It looks complex enough to have to spend a fair bit of time on.
I think with all these things, the art is getting the potential user going quickly enough- with something…There needs to be some sort of quick start that you can build on.
Rhino is a nice modelling environent, but not too keen on the meshing- it can bring the Modo ‘model’ window to a stand still. Modo is best with its own inhouse modelling/mesh at rendertime system.
Did a bit of EI messing about earlier- it really needs a better previewing facility. I notice mostly the mesh shading quality and the nicely shaped highlights. Also the way objects are affected by the lights in a way you don’t get with c4d.

Martin K

#28

You’re missing out if you haven’t tried it!!:slight_smile:

Here’s what you do…create your object and make a ground-plane, open the Brazil Options interface, scroll down to the Luma server and click the Sky Light check box in the Direct Illumination section.

Hit render…perfectly exposed white plaster GI scene. A little grainy but that goes away when the AA and sampling is brought up to output quality. Click on the Button which says P3 in the Sampling parameters under Image Sampling in the options tab to get a nice preset fr output quality.

That’s all you have to do to get a general idea of your objects…setting up materials and a great GI Environment is almost just as easy.

I’m using the Modo to Rhino and Rhino to Modo pluggins and they work great for in and out…though if too large Modo can slow down.

Objects created in EIM and exported as fact with a good sound mesh shade and render incredibly well in EI. I believe the smooth shading is assigned per normal (I’m not certain) so you don’t get the weird stuff C4D can throw at you.

Rhino behaves exactly the same way with Brazil…no smooth shading errors…everything is perfect within the app. Mesh created elsewhere and brought in (Modo, C4D) is a different story and one has to deal with smooth shading angles, etc. I stay away from that as it’s such a pain at times…but the only thing I really bring in are SubDs so the shading is quite fast to set up.

Give Brazil a run…the beta is expiring soon and you may not get a chance.

#29

Wow! I just tried that- looks good. Must do some more…

Martin K

#30

Here’s the next thing to do:-)

In the Environment tab load in the GI environment. And then assign one of the HDRI’s which came with Modo in the image slot.

Assign a chrome material to your object and set the color of the chrome to less than white…a nice warm or cool grey.

Hit render:-)

#31

Hi Paul how are those NX shaders working for you so far. I have seen tonight some of your art and David as well. They look incredible. There is no need for any texturing just with that NX shading system you got enough.

#32

David’s shaders are great - NX included. He really did a lot to increase the value and useability of EI.

Yes, maps aren’t as needed with all of the great procedurals available but they still have their place - EI’s filtering of maps is first rate.

#33

Thanks Paul, I’ll try that when I get time- off to photograph flowers…

Martin K

#34

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.