Author Topic: DR failed...  (Read 2672 times)

2014-10-29, 09:22:29

Christa Noel

  • Active Users
  • **
  • Posts: 911
  • God bless us everyone
    • View Profile
    • dionch.studio
Dear all,
I'm using corona with distributed rendering as usual and have never had trouble before.
main PC: i5 4570, RAM4G, Radeon R200, win7 SP1, max14 SP5, corona A7.1
slave PC: i7 4770, RAM4G, Radeon R200, win7 SP1, max14 SP5, corona A7.1

few days ago, i add a new PC as a slave PC. the specs is i5 4570, RAM4G, Radeon R200,  win7 SP1, max14 SP5, corona A7.1
i install max, corona, just same like before.. then i add this new PC via search LAN and it is appeared on the main PC (slaves replying correctly). but when i hit render, the new slave is failed to work (older slave run without any problem).
i rechecked again and all PC has the same OS & max version/SP.
what is the problem?

2014-10-29, 12:34:46
Reply #1

fire3d

  • Active Users
  • **
  • Posts: 48
    • View Profile
Try to initiate a Backburner Net Render for the first time initialization, after that it should work

2014-11-08, 22:20:56
Reply #2

ktulu

  • Active Users
  • **
  • Posts: 33
    • View Profile
Hi guys,

I have a similar issue: on our local network all the machines have the same specs. 13 out of 15 work fine with Corona and DR. Two of them I can't force to work however - they are stuck on starting UDP Socket... Everything seems to work fine with Backburner though. Do you have any ideas how to approach this?