Render Slave Gamma

[arqrenderz]

It happens somethimes to me  :( Is it possible that Corona Forces all the slaves to render at the gamma specified by the master??

[lius86]

SOLVED

Ok I finally solved the problem.

Basically my main workstation was setup with output gamma to 1.0, even if from the ini file, was 2.2. (don't ask me why!).

I solved opening a file with the gamma setup on 2.2 for both, saying to use system gamma, instead of the file gamma, and then i saved the file.
I then run the script again, and apparently somehow, i managed to save the Bitmap output gamma on my main to 2.2.

Opening the file then from the node, i did NOT GET the mismatch gamma settings, which is fundamental to DON'T HAVE!
If you get that message, your render will look bad.

Finally, after having checked that the node was reading the file with the same gamma of the master, i sent the DR render, and it was finally looking good.

[luissee]

SOLVED

Ok I finally solved the problem.

Basically my main workstation was setup with output gamma to 1.0, even if from the ini file, was 2.2. (don't ask me why!).

I solved opening a file with the gamma setup on 2.2 for both, saying to use system gamma, instead of the file gamma, and then i saved the file.
I then run the script again, and apparently somehow, i managed to save the Bitmap output gamma on my main to 2.2.

Opening the file then from the node, i did NOT GET the mismatch gamma settings, which is fundamental to DON'T HAVE!
If you get that message, your render will look bad.

Finally, after having checked that the node was reading the file with the same gamma of the master, i sent the DR render, and it was finally looking good.

Edit:

On 2 workstation we have same settings for the bitmap gamma: input and output to 2.2

Can't change this settings on the nodes, where is 2.2 input 1.0 output.
I tried changing the ini file, using a script, but nothing. Any idea?
The mystery is that with vray it renders fine..!

So you got your textures to render correctly?  And everything's good now?

[lius86]

SOLVED

Ok I finally solved the problem.

Basically my main workstation was setup with output gamma to 1.0, even if from the ini file, was 2.2. (don't ask me why!).

I solved opening a file with the gamma setup on 2.2 for both, saying to use system gamma, instead of the file gamma, and then i saved the file.
I then run the script again, and apparently somehow, i managed to save the Bitmap output gamma on my main to 2.2.

Opening the file then from the node, i did NOT GET the mismatch gamma settings, which is fundamental to DON'T HAVE!
If you get that message, your render will look bad.

Finally, after having checked that the node was reading the file with the same gamma of the master, i sent the DR render, and it was finally looking good.

Edit:

On 2 workstation we have same settings for the bitmap gamma: input and output to 2.2

Can't change this settings on the nodes, where is 2.2 input 1.0 output.
I tried changing the ini file, using a script, but nothing. Any idea?
The mystery is that with vray it renders fine..!

So you got your textures to render correctly?  And everything's good now?

yes!

That's why the hdri was having problems!

[maru]

SOLVED

Ok I finally solved the problem.

Basically my main workstation was setup with output gamma to 1.0, even if from the ini file, was 2.2. (don't ask me why!).

I solved opening a file with the gamma setup on 2.2 for both, saying to use system gamma, instead of the file gamma, and then i saved the file.
I then run the script again, and apparently somehow, i managed to save the Bitmap output gamma on my main to 2.2.

Opening the file then from the node, i did NOT GET the mismatch gamma settings, which is fundamental to DON'T HAVE!
If you get that message, your render will look bad.

Finally, after having checked that the node was reading the file with the same gamma of the master, i sent the DR render, and it was finally looking good.

Sorry but I d not fully understand how you did this. Could you try explaining step by step (bes would be in points 1,2,3...) what you did to fix it? It would be greatly appreciated.

[luissee]

SOLVED

Ok I finally solved the problem.

Basically my main workstation was setup with output gamma to 1.0, even if from the ini file, was 2.2. (don't ask me why!).

I solved opening a file with the gamma setup on 2.2 for both, saying to use system gamma, instead of the file gamma, and then i saved the file.
I then run the script again, and apparently somehow, i managed to save the Bitmap output gamma on my main to 2.2.

Opening the file then from the node, i did NOT GET the mismatch gamma settings, which is fundamental to DON'T HAVE!
If you get that message, your render will look bad.

Finally, after having checked that the node was reading the file with the same gamma of the master, i sent the DR render, and it was finally looking good.

So what are your gamma settings on the master and slaves?
It was a gamma issue after all?
I'm still having issues with it.

[luissee]

Ok.  I finally got mine to work on four machines.  Hopefully I can add more now.

My issue wasn't the gamma issue.
My gamma was enabled, so the default 2.2 in and 2.2 out were fine.  I didn't have to mess with the ini file or run a script.

- My issue was the network mapping of textures.
- Even though they were mapped to the network (N:) and they would open fine on the slaves to render out alone, and I got the master and one slave to work this way.  But when I added more than one slave, it didn't work.
- When rendering together the stripes would show up
- So I changed all my texture paths to\\networkname\folder name\file name
- Seems simple enough, but since the files opened ok by themselves and got one slave to render with the master, I thought it was something else, and went crazy looking for it.
Also, the port numbers in backburner general settings should be the same.  They suggest you use 19667 and 19668, but I didn't have to, to get it to work.

- Before I was thinking it was a gamma output of the slaves
- Maybe the order things were installed on my computer. 3ds max, backburner, corona
- Maybe I had to uninstall corona and install service packs, then install corona again
- Maybe different versions of corona would work


I'm sure you've come across this, but this helped.
https://coronarenderer.freshdesk.com/support/solutions/articles/5000501666

[iuvalles]

luis86 Can you explain how to change the output gamma computer?
thanks

[Ludvik Koutny]

This seems to be solved.

Therefore moving it to resolved section.