Indigo Renderer Forum

nice, i like

two little things:
* white point settings dont work because of some parsing error ("Error: TinyXmlWrapper: Parse error while parsing float from '0,25'")
* one has to click on "render" after opening the scene - not really a bug but i got used to indigo just starting the rendering

fused wrote:nice, i like

two little things:
* white point settings dont work because of some parsing error ("Error: TinyXmlWrapper: Parse error while parsing float from '0,25'")
* one to click on "render" after opening the scene - not really a bug but i got used to indigo just starting the rendering

Personally, I love how you have time to collect your thoughts and get your settings worked before. It makes the whole process seem much more calm and collected imo.

I've updated the links to a new version, 2.0.2, which should fix the float parsing issue.

Hey,
I like it. A step in the right direction. Nice.
I just love that you can pick the cam. resp. func during the rendering now.
Also the image saving + new formats are awesome !!

One thing i noticed though (I think Smart already mentioned it).
It currently doesn't respect the aspect ratio of an image. It scales everything down to 800x600, but if my image is not in landscape, but is a portrait (600x800 for example), then it still streches it to fit 800x600. I think you should consider the image aspect too. (for 600x800 the aspect is 0.75 so when scaled down the correct resolution would be 450x600). That's how the Maxwell demo does it. Otherwise you can only render in landscape and only with 1.333 ratio.

[edit]
Has the displacement changed too? I'm getting different results compared to 1.18.

benn wrote:Commercial licenses for Indigo will cost 595€ for a full version, or 195€ for a node license. To say thanks to all the early adopters of Indigo, we are offering full version licences for 295€.

Hmmm...

Do I read this correctly that there is NO possibility to get network rendering done if I only buy the full license??? For each of my slaves I need to pay 195€ to get it work, and even this seems to be fingerprinted with the hardware of my slave node.... so I can't swap the slaves easily

I still have the idea to build a Helmer in the end of this year.... to run Indigo on it I have to buy main version and 6 render node versions, that only work so long I don' upgrade the hardware.

295€ + 6x195€ = 1465€

And without lifetime licenses this seems to be a expensive journey from zero to hero

Heya ZomB,

It might be a bit expensive, but we will have node licences on 50% discount for a period as well - we'll let you know when they're available. As for the hardware fingerprinting - we may be relaxing the fingerprint used for the licences - I understand that many of you use a laptop and desktop at the same time - we want to provide logical solutions to this.

Ben

ehm, Ben, should i download and build libjpeg by my own? or something bad on my machine and no other mac user has problems?

carbon - you definitely dont have to build libjpeg yourself - I must have incorrectly set the library paths - I'll redo the package now...

carbon what error are you getting exactly? I must be missing something.

it just crash, before it start, i have posted crash report earlier..

Oh sorry carbon - I'll fix it now. My apologies.

Fixed carbon - http://www.indigorenderer.com/dist/beta ... seimage.gz

(for those interested - I hadn't run otool -L on all the libraries included in the distribution)

ok, now it works..

but i have question, how about exporter developers? are you going to hire current developers? because Indigo, by my opinion, is unusable in real production without exporter of same great quality as rendering engine is. the new shiny gui is pleasant, but big button 'render' is nothing compared to, for example Blendigo's material editor and/or even more important geometry - to - indigo mesh conversion..

regards
c.

edit: don't take me bad, i am thinking seriously about purchasing indigo license, but the price you estimated is a bit higher than i was expecting (almost 2/3 of maxwell's price), so this question promptly came to my mind..

fused wrote: * one has to click on "render" after opening the scene - not really a bug but i got used to indigo just starting the rendering

This will be a problem for me when I do material preview renders with SkIndigo. Maybe a switch to determine if Indigo starts rendering immediately after opening the scene file?