Messages

1

[Max] Resolved Bugs / Re: Render Slave Gamma

« on: 2015-03-18, 13:35:26 »

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

2

[Max] Resolved Bugs / Re: Render Slave Gamma

« on: 2015-03-17, 18:57:18 »

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.

3

[Max] Resolved Bugs / Re: Render Slave Gamma

« on: 2015-03-16, 18:50:46 »

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?

4

[Max] Resolved Bugs / Re: Render Slave Gamma

« on: 2015-03-15, 00:50:14 »

i did another test, instead of using an hdri, with the sun, and seems working..would you mind trying as well?

I haven't been using an HDRI, just the sun and corona sky.  But I think I got it to work :D

I work on my local computer then archive to gather all my textures, then i put it on the network drive, so all the slaves can read it.
That works with mentalray anyway.
When I looked at the textures paths in the material editor, the paths read as my local one, but when i opened the link, it opened the network folder.
So, I just linked it to the network path, so it had the network name in the path name.
It works :D

Let me know if that doesn't make sense.

5

[Max] Resolved Bugs / Re: Render Slave Gamma

« on: 2015-03-14, 17:35:40 »

ok, some more test today..

THe render looks good for the first passes on the main computer, and the node is rendering fine. But, i don't know why, on my node, after the 30th pass, it starts again from 1-2-3, and when it does that, the stripes appear on the main workstation buffer.

I tried to play with .ini file, changing the gamma settings with different combination, but it doesn't seem helping.


edit1: changing the  sync interval to 10 seconds, makes the stripes appear sooner.
edit2: tried to copy and paste the ini file on both computer using the same but nothing
edit3: tried to remove textures and using an override but nothing.

Good thinking to copy the ini file.
I thought it was the ini files on the slaves that had to be changed, but it's the ini on the master computer.  The slaves use that outputgamma value of the master.
I saw a distributed rendering with corona video, and the guy had it at 0.0, but that didn't work for me either
I changed it to 1.000000 and nothing
I saw somewhere else where someone added 1.0+2.2 to make 3.2, but that didn't do anything either.
All those options produced the same result, so I'm thinking the output value doesn't affect it.
I'm thinking maybe it's the input value of the textures that affect it?....

The override with a solid material didn't work?  It works for me.  So, I'm thinking it's how gamma is applied to textures on the slaves?

6

[Max] Resolved Bugs / Render Slave Gamma

« on: 2015-03-13, 18:42:36 »

Hey guys I have a quick question.  I also get strips on my renders when i use distributed rendering. I put the max file and all the textures on the network, so all computers have access to them.  I've gone through the forum and read all the other people that had the same issue, but nothing seems to help.

The only thing I can think of is that the master computer outputs the gamma at 1.0, but the slaves at 2.2. I attached the screen shots.

I read to make sure they are all the same, but how do I change either the master or the slaves?  I tried changing the 3ds Max Gamma/LUT, but that doesn't seem to help.




I also ran a test without textures and it doesn't seem to get strips, so I'm not sure what it could be anymore.