David Coiffier
Forum Replies Created
-
My eyes skipped this part, sorry
-
No one ever mentioned the Stage Object ? I guess it just has been created for this exact purpose…
-
Didn’t see the price at first…
-
That might be the missing thing you were all looking for…
App is importing xml from fcpx and can export reference QT !
-
From my understanding, the whole tex folder is uploaded to the clients, whatever file is used or not.
Than means you have to manage more or less manually this folder. One easy way is to save project from C4D to your admin folder, once you have removed all unused textures within C4D. This way you should only copy used files.
Once scene and tex files are uploaded to your client(s), they’re used until the end of the render.
But if you stop and relaunch a netrender, server will push again all files to the client(s). Sounds a bit rude, but it’s a good idea anyway to avoid versioning problems in your files.So does it render now ??
-
Well, if you have port forwarding issue, you can refer to my 3 years old answer, at the beginning of this thread. Here is a copy :
If at home, you’re behind a NAT, then you need a port forward rule that says “incoming TCP on 1080 goes to this particular local IP” (1080 is default port)
Next refinement is to connect several clients from one IP :
All you have to do is get a different port for each client behind the router, by specifying in the client prefs dialog other ones :1081, 1082, etc…
Of course, you also need port forwarding rules for each machine…Let me know if something is unclear…
-
Given your bandwiths, upload from server is the bottleneck.
In case mb means megabits, 0,35 mb/sec is only 0,043 megabytes, and transferring 250 megabytes would nearly take 2 hours to complete.
In case of 0,35 megabytes, 250 MB would take roughly 12 minutes to complete.How long did you wait before giving up ?
-
You’re correct when placing scene file and tex folder to your admin folder, for netrender server to see them.
When starting render from web interface, server distributes scene file and tex folder to every single client. Normally you don’t have to worry about that transfer, because it’s automatically done behind your back.
What I’m saying is that if you can read in your client window “starting xxx render” then “rendering image #yyy” it does mean that transfer occurs correctly, and so port mappings are correct, even with the simpliest scene file.
With heavier scene+tex files, client will quickly say “starting xxx render”, but you’ll have to wait that scene and tex folder are totally transferred to client before reading “rendering image #yyy”.
So depending on total files size, and bandwidth, it can take quite a long time to deliver them to every client.Renders never starting are usually symptom of incorrect port mappings on client side. But as you said a really small scene file is effectively rendered by your client, I understand that port mappings are ok, otherwise render would not even start (meaning you wouldn’t read “rendering image #yyy”)
Hope this is clear to you…
Have another try with a netmonitor on client machine (I do love menumeters, that is totally free, but there is also an Apple app named Activity Monitor.app, that resides in your utility folder). At the moment you start netrender on web interface, server should send files to client(s), and so you should see incoming traffic on client side… This will just eliminates long waiting for nothing in case nothing is transfered…
-
From my point of view, if scene file is correctly uploaded to your client, then tex folder should also be…
-
Do you have any net monitoring on your client(s) to see if something is coming in when starting render ?