Indigo Renderer Forum

Originalplan® wrote:It is ready for play and reporting problems back. :)

That's the name of the game !

Zom-B wrote:The CPU renderer is faster now and does a great job running stable for me and my 2 Renderslaves.
The GPU renderer indeed always misses some features that I need for a project, but the CPU part is great...

There is also no need to uninstall v3! I always install new Indigo versions in a new folder with version number and thereby can always use the earlier version if sth is not working or do benchmarks between the different versions.

Of course for the first test run I jumped over GPU rendering out right, I'm about to install the latest drivers now.
I expected to see the CPU listed as a device, maybe OCL 1.2 support is not enough ? (i7 860)

PS: I have 95%+ of all versions of Indigo from 2.0.5 to 3.6.9 currently installed, I then switched to a fixed folder until this release.

Zom-B wrote:

CTZn wrote:

afecelis wrote:Is this stable enough for production?

No no no no, that will be in quite some time, beta does mean beta ! It took several years for 3.0 to go from first public beta stage to "stable".

I actually work with the v4 beta in production from Day one!
The CPU renderer is faster now and does a great job running stable for me and my 2 Renderslaves.
The GPU renderer indeed always misses some features that I need for a project, but the CPU part is great...

There is also no need to uninstall v3! I always install new Indigo versions in a new folder with version number and thereby can always use the earlier version if sth is not working or do benchmarks between the different versions.

Ahhhhh! great to know! :D That's a smart move! (Though I had already uninstalled version 3, lol! Time to reinstall everything).

I also keep getting the program reset back to trial every time I launch it, even after entering my serial/license and activating it. Is this normal?

Thanks for clarifying my doubts.
regards,

Alvaro

CTZn wrote:

Originalplan® wrote:It is ready for play and reporting problems back. :)

That's the name of the game !

Zom-B wrote:The CPU renderer is faster now and does a great job running stable for me and my 2 Renderslaves.
The GPU renderer indeed always misses some features that I need for a project, but the CPU part is great...

There is also no need to uninstall v3! I always install new Indigo versions in a new folder with version number and thereby can always use the earlier version if sth is not working or do benchmarks between the different versions.

Of course for the first test run I jumped over GPU rendering out right, I'm about to install the latest drivers now.
I expected to see the CPU listed as a device, maybe OCL 1.2 support is not enough ? (i7 860)

PS: I have 95%+ of all versions of Indigo from 2.0.5 to 3.6.9 currently installed, I then switched to a fixed folder until this release.

It's OpelCL 1.1 or better. Your CPU will not do a great job at GPU rendering unfortunately, better get yourself a reasonably new Nvidia or AMD card. :)

Btw afecelis: do you have a V4 license? Otherwise it's no wonder it doesn't work properly.

yup I'm working the budget for a new card, getting the same error than with earlier drivers version now: What kind of error is this (GTX260 860MB) ? Sorry if it was reported already.

Thanks Ono !

From the little experience I have the CPU isn't used much, it would be swell if one could use CPU bidir path and merge it with GPU path, like when in network mode.

afecelis wrote:I also keep getting the program reset back to trial every time I launch it, even after entering my serial/license and activating it. Is this normal?

Nope, that absolutely uncommon!

Check out your license.sig, maybe it is write protected and can not update or sth like that...

Hi.
Seems that when GPU is selected lightlayers parameters are readed as 1,0.
And, how to explain...
GPU starts... (right, the problem in this moments is that the openCL kernel is builded with one core (a minute for a simple scene in a GTX 980 due to architecture (a lot of small cores)).
But for example change the sun direction (don´t change because need to rebuild the kernel and actually this don´t happens). The same with every kind of stuff (changing the emission on/off don´t has afectation...)...
EXCEPT the white balance and the tonemapping, every step needs actually to rebuild the kernel... and actually only recbuilds if you change the SS or if you change the modality of process (and the stop button don´t exist anymore).
This is a hell for a single core (but is known that multithread kernel build is a goal nearly)...

Has this sense or I miss something?

Edit: This is the message of error when I try to render a fast SSS with GPU ( and seems that for others users this works). Nobody has this problem seems. Once GPU starts I can´t change a value, there has no response.

McLaren:
1.450M only after 40 seconds (0.500M at first 40 seconds)

Bedroom:
0.300M

i5 4670 8gb gtx680 2gb

F*CK YEAH, the new Fast SSS... KILLER!!!
AWESOME JOB!!!
After 2 minutes on my old iMac... PT w/o GPU, SS4... red body only the new Fast SSS material... wow!

snorky wrote:McLaren:
1.450M only after 40 seconds (0.500M at first 40 seconds)

Bedroom:
0.300M

i5 4670 8gb gtx680 2gb

Have you tried letting it render for a little longer? Say 3 minutes or so?

Oscar J wrote:

snorky wrote:McLaren:
1.450M only after 40 seconds (0.500M at first 40 seconds)

Bedroom:
0.300M

i5 4670 8gb gtx680 2gb

Have you tried letting it render for a little longer? Say 3 minutes or so?

Y

1: Found a BUG on OSX. (minor)
When you put Indigo in Fullscreen mode there is a second icon frame. (see pic one)
2: Found this beauty! (see pic 2) :)

3: Fast SSS is FAST AF :) Sorry for the language (pic3)

4: I need to get a 500euro loan soon :D

Cool tests! 3 minutes is properly quick for nice looking SSS.

If you purchased Indigo after the 3.8 stable was released, v4 is a free upgrade. If you didn't there will still be upgrade prices from Indigo 3 I think.

Originalplan® wrote:1: Found a BUG on OSX. (minor)
When you put Indigo in Fullscreen mode there is a second icon frame. (see pic one)
2: Found this beauty! (see pic 2) :)

3: Fast SSS is FAST AF :) Sorry for the language (pic3)

4: I need to get a 500euro loan soon :D

OMG you'd found an easter egg! :D

yonosoy wrote: Edit: This is the message of error when I try to render a fast SSS with GPU ( and seems that for others users this works). Nobody has this problem seems. Once GPU starts I can´t change a value, there has no response.

Hey yonosoy - Fast SSS is its own material type - so don't use glossy transparent.