Indigo Renderer Forum

Continuing to learn This wonderfull program...

Some questions:

1. What settings for pool water (with green-blue reflectance)
2. how often did you use sampling > 1 in big Images (>3000x*)
I am concerned be course nowedays i have 1Gb RAM and in my observations - results are identical (or pretty much)
3. Where is the materrial Library? Few weeks ago I foundet link to it, but now i didnt

PS I choose Indigo becose Fry dont want render with low memory and I think indigo very usefull, but need some convenience like Fry. My Exmple is: Indigo+violet=one programm and how did you think ppls

vux wrote:Continuing to learn This wonderful program...

Some questions:

1. What settings for pool water (with green-blue reflectance)
2. how often did you use sampling > 1 in big Images (>3000x*)
I am concerned because nowadays i have 1Gb RAM and in my observations - results are identical (or pretty much)
3. Where is the material Library? Few weeks ago I found link to it, but now i didnt

PS I chose Indigo because Fry doesn't want render with low memory and I think indigo is very useful, but needs some convenience like Fry. My example is: Indigo+violet=one program and how do you think ppls

1) greenishblue reflection comes from the greenishblue pool walls - you need simple water (I dunno, how much chloride effects the water, though)
IoR = 1.33
2) ??? - about the Ram: you don't need it for the full process. Ram is used for the Image size and for supersamples. (Or also for very hires textures or very detailed highpoly scenes) - if one or all of those are very high, your PC might get slow, as swapping is needed

3) Currently not in use (it exists, but you can't register, so, you also can't submit materials - you can download them, though )
http://elqx.com/indmatdb/

currently, you need to use this thread:
http://www.indigorenderer.com/joomla/fo ... php?t=2009



and that Indigo + Violet was suggested several times, already ;)

oh thanks for links and answers
but
how about superampling using???
i my cases (with big resolutions + supersampling=2) Indigo crashes in 170000Polys Interrior

did you often use supersampling>1?

what's "big res"?
that's very variable^^

for me, big res, starts at 1000². others might say, big res = 10000²
usually, for big res, you EVER use supersample factor 1 (although even "my" big res 1000² works at at least Supersamplingfactor 3 - slow but without crash)

btw, WHEN does it crash? Does it render, already? Or at the beginning? if it starts crashing from beginning, you might want to lower "Hybrid value" or something like that... It has the wrong name, in Blendigo, but there's a Tooltip "set the amount of tris, when Hybrid mode shall be used" - actually, there should stand "BiH mode", as it doesn't at all affect Hybrid, but it builds the KDtree in a different way: WAY faster, available for WAY bigger scenes, but slower to render

THANKs
for me BigRes - is from 3000 to 8000 - for HQ PRINT
about crash - it crush at beginnig

then, try to lower that value, beyond 170000 and it should work fine Supersamples don't affect the starting sequence, at all, as well as the res. They're too high, when there is a "Memory Error" AFTER the initial sequence

a couple of months ago I did a test:
that Interrior (170000Poly) at res > 4096x without supersampling - it was OK
but with SS it crash...

The reason why Indigo and Violet are two separate apps is that bloom, for instance, has to be evaluated again after each image upload (every 30s by default), and that's sooo time consuming... Some people were waiting for bloom update for a while, and during that time Indigo isn't computing the image. It's much better to set these parameters once for all, when the image is computed, than every 30s

I make no outputs for printings so I can't really answer that, but anyway if your Indigo crashes on higher supersamples settings you have no choice but to lower them.

Oh and now I remember that only a few days ago someone told that supsamp of 1 was ok for high rez because the very same process of high rez printing is softening edges IIRC.

1Gb RAM is too small amount by today's standards. Memory is very cheap nowadays. Get yourself at least another Gb

Fry have a very usefull instrument - Spray
it allows select a region in Image and render only it

beware of TOO CHEAP memory, Indigo stresses it very much, someone had to revert back from 3 to 1 GB because of ram quality

Yep region rendering is a redundant request here, many ppl are after that and the "developers team" is aware of that long time request already.

my 768 MB are enough for Indigo, as I said, already (although, that res might get VERY hard to render xD) - Arne has even less, if he didn't stock it up, yet and it worked for him, too, 'till now

Indigo understood faces with more than 4 vertices or I need to triangulate it?

neither nor, blendigo will triangulate it for you

...and Indigo doesn't "even" understand faces with more than THREE vertices

ah, btw - did you look, where the normals are pointing to?
When using a plane, they have to point upwards, while when using a volume, they have to point outwards

did you look, where the normals are pointing to?

of course