Cool But somehow the printer looks weird... maybe check the normals or so?

I don't think we had such a thread before, so here it is, a thread about what you can do when rendering to increase performance. Any kind of settings, what is important when building a computer, when overclocking it (is RAM speed, FSB etc. important? ...) etc. is welcome. Set the task to high priori...

Hm... does it take just as long to render a image at 800x600 with ss2 as it takes to render a image at 1600x1200 with ss1?

Btw. if you have the igi, you can set the ss to 1, resume and render until it saves. You png should have the full resolution then.

Just start the master with -n wm, and the slave as you usually do. That should do the trick. Though you can also use this automated system, but if it doesn't work you can always start it manually this way.

Well, it saves a lot of CPU cycles, not supersampling. And I rather prefer to render at a higher resolution and then do supersampling by reducing the screen size myself. You're right suv, it's a bit overexposed. I've made the device pure black, so in order to have it show up a bit I had to expose it...

Sure. There don't only have nonsense groups

Posted about Indigo/Cindigo in the c4d group in StudiVZ a while ago

@dougal: That's what I'm doing at the moment, but I can only define when a image has to be saved before I start the rendering. At least as far as I know. So I first start with maybe a image every 60 seconds, then every 5 minutes and when I think it will turn out ok every 20 minutes. Would be nice to...

Hm, features I would like to see is refresh when I want it, pausing the displaying of images, etc. I think all that is needed is a tool that can tell Indigo when to render the image, and then it needs to display the saved PNG. That would also improve performance since I don't have to display an imag...

Oh, ok, didn't notice that, probably because the region renders too fast.

Odd, but great.

Hm, maybe someone else could work on a new GUI? I think I have some ideas for that, I just lack the coding skills.

Ok, what works for me now is running a working master on the Mac and the client on the PC. Unfortunately the Mac isn't connected to the internet, so when I try to let computers over the internet join that would be a problem. But for now this works fine :) I still think it is a problem with the maste...

I love render region. It's great for determining if the texture will turn out ok or if the exposure is ok, or to see if the DoF is ok etc. (simply things you would notice when the rendering cooked for many hours). Very useful, saves a lot of time when testing. Wouldn't want to miss it :D It would be...

Ok, I have tested running the server on the mac now, with even weirder results. The PC client sends the packages flawlessly to the Mac server, but the Mac client fails to send its data to itself. I will try 127.0.0.1 now... I think the problems are related to Wine/Crossover, but I recall other users...