netrender over the internet anyone?

[imashination]

hi everyone !
does someone have experience with netrendering over the internet? are there any clients i could use? (also providing my own pc as well of course)
thx
markus

www.markusmooslechner.com

Its been tried before, the logistics of it just wont work, the sheer amount of data to be sent back and forth is usually too much

[RenatoT]

It work and with a standard ADSL (256/1024) run like a charm..
Maybe slow to send scene to all client so better to use procedural shaders and procedural models.

just take a look and foward the firewall port if there is a router or firewall.

Cheers
Renato

[mm149047]

It work and with a standard ADSL (256/1024) run like a charm..
Maybe slow to send scene to all client so better to use procedural shaders and procedural models.

just take a look and foward the firewall port if there is a router or firewall.

Cheers
Renato

renato !
can we try a render? what infos do you need exactly? which fw port?
markus

[LucentDreams]

to make a lie a lot easier Chi and I have used hamachi to set up a virtual local area network to use net on, makes it very simple to use especially for someone not savvy with Ip's and firewalls etc like me.

That said as mash mentioned the logistics in moving most files does sort of defeat the idea a bit. but hey we can also zip the file send it very small and manually place it in the clients which works fairly well and sadly I find manually placing files in the client more reliable that relying on net to do it.

[sjcrompo]

I am running netrender as we speak. I have my pc which is the server and 1 client, I have another pc in the house which is the other then my friends which is dealt with over the internet. I works pretty well with some issues but mostly its ok.

I always work on the thing that every frame done by another computer is one less to have to do on mine.

Cheers

Steve

[flingster]

does any form of compression take place when moving data back and forth?

could some form of P2P take place within say the 10 clients so once one client has it then the others can be accessing from 2 and then 3 and so on?


anyone?

[unseenthings]

We use netrender over the internet fairly often. With 2 PC's here, 2 PC's in another location, and a handful of mac's at the third. Usually the mac is also hosting the server, but not always.

Netrender does leave a lot to be desired, such as really slow file transfers (take for-ever to start), lack of helpful error messages/alerts when there's a problem, sending individually to machines that ought to be able to transfer across their own network, being able to place files manually (which, unlike Per, I've never had luck with, but may give it another shot, because if he says it works, it works!)... I'm hoping it's on the list for an update... I don't think the whole thing needs a complete overhaul, because while complicated, it still works quite well once you get it all set up. But it definitely needs an update in a handful of areas to really be up to the quality that the rest of C4D generally has.

It helps to know your firewall and router a little bit... I will give this hint. If there are multiple machines at each location, you'll need to set them up with different ports. I usually set mine up for 1080 (the default) and 1081. And the next guy can set his two up for 1080 and 1081, etc. As long as you open those ports in your firewall, and change it within your net client settings, you're usually in pretty good shape.

Flingster: I really, really doubt there's any compression taking place. There *should* be, in this day and age, but I'd be really surprised given filetimes.

Also, the mac network is not on a basic cablemodem setup, but a "business class" cablemodem setup, which usually (just) means more upload power... which, when you're sending files out and such, you need. I think that's probably contributed a lot to our success in using it, even though it takes a tremendously long time to receive all the files and get started sometimes.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.