I think the character adds to it, although one keeps looking at her instead of the trees...:blush:

---

Production log 7

A quick test for Indigo and speedtree.
Bugs I encountered for two days here.
https://forum.reallusion.com/Topic225125-388-1.aspx
I think Iclone+indigo = lovehate relationship :D
Love that I can get renders faster than any unbiased renderers I've had(octane, maxwell, fry).
Hate the export process from Iclone that takes long and eats gigs of hdd space.:D
Apologies for the preset character, she wasn't supposed to be there. Just testing indigo with heavy speedtree stuff.:w00t:

Last test. Indigo is very predictable and easy to understand compared to other renderers of its type. Easier than octane definitely. Going to pick this up for sure.

A little more time to cook the grain could be lesser but not completely noise free. Interiors are just difficult to render for unbiased renderers.

Some more tests with different modes. bidi with mlt has less noise.

Wow the last one is looking pretty lifelike!

Writer/Director of the feature film PLATO'S REALITY MACHINE
Featuring IClone animation
www.platosrealitymachine.com

1 hour render at 720p. Still a lot of noise as expected with unbiased renderers.
Speedtree library plus cheap models in marketplace could potentially attract pro archiviz users.
Not bad for a render plugin at this price. :D



The spotlight in Iclone becomes an object in Indigo. :D

Another test. This is the problem again with pathracers same as maxwell,etc even with bidirect and mlt. Too long render times for enclosed interior scene. :D Gpu contribution is very minimal for indigo. 100% used but contribution to actual render power is less than 20%. Very behind octane. Biased renderers like vray and kray would eat this scene for breakfast in 3 minutes.




Iclone


But for exterior shots and grass with high detail scenes nothing beats a pathtracer though ;)
For interiors..nay.

Some tests. Didn't touch the materials or lighting, only tonemapping and post work.
I wanted to see how well the autoconvert material worked.
Its 80% there which is really good work by RL. There really is a need to adjust materials imo but for lazy people 80% is good enough imo.
Even if I have 3dxpipeline now it would be too much work to export these scenes by fbx.

Pretty slow to process and gfx card was using 1500mb while ram is around 1000mb




I looked at the camera settings the conversion from Iclone was wrong so just manually adjust it. So the camera can match we just need the proper settings from RL like the IClone sensor width, fov.
The bump mapping is pretty weak in indigo and color values seems incorrect. That needs tweaking.

Production log 6

I noticed that when its in cpu mode there are other render modes, which is good since some of them are cheat engines to make it faster.

But to compare closely with octane and other unbiased renderers lets use pathtracer mode.

500 samples is not enough I still see a lot of noise compared to octane.
But its still a good benchmark for comparison. I ran it multiple times making sure it started from stop to render.

Cpu mode 3770k cpu - 3:38s ish
pretty good render time considering this is pathracing mode.



Gpu mode 750 gt ti - 3:03s ish
cuda or opencl tested its negligible time difference. Why? Because the gpu only assists the cpu. Most of the work is still cpu. If this was a pure gpu renderer I suspect it wil be half the render time.



Intel hd 4000 gpu in opencl - not supported
Too bad it doesn't seem like you can use multiple gpu for indigo rt yet.


My opinion. The render time probably is 5 times slower than octane to get clean image but you can survive with good cpu. Getting a highend gpu like titans,etc not so much help in render time with this renderer, 750gt ti 3mins to 980 gtx 2:45mins.

But Indigo RT is worth it for people who want more quality render for a cheap price of an unbiased renderer. There's no renderer in its class that comes close in price. The implementation is pretty good except for the frame by frame export.


File converted to Iclone format by animagic.:D

Test for vidi.

Production log 5 - Iclone to Modo Indie



Its working but the viewport in Modo is extremely sloooooowwwww because of deformation calculation and mocap keys is heavy. The textures didn't get in so I have to reassign all of them :D The morph info is there, too.

All in all I would rather use modo for what its good at which is asset creation particularly sculpting and painting.