Author Topic: Waiting for render start  (Read 2905 times)

2017-05-11, 16:11:07

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
Is anyone else getting this behaviour/message? The nodes just sit there waiting unresponsively after a render has finished.

If you restart Max and the DR server it works.

2017-05-11, 16:42:08
Reply #1

sevecek

  • Corona Team
  • Active Users
  • ****
  • Posts: 197
    • View Profile
What does the master say in the DR tab?

2017-05-12, 10:27:06
Reply #2

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
I'll check it out and take a screenshot.

2017-05-12, 11:56:51
Reply #3

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
OK, did a bit of experimenting. Our nodes are running both Max 2013 and Max 2015.

If I send a DR render from a master running 2015 when the nodes have just started, it works fine. DR renders from 2013 master generally work OK, but if I send a render from 2015 master after a 2013 DR render has been running, it gives me the waiting for render start and I get nothing. If I then send a render from 2013 it works fine.

Few screenshots for you to look over attached.

Using four render nodes to start (three running windows 10, 1 running windows 7)
The first batch was captured when I sent a render from a 2015 machine.
No.2 render from a 2013 machine
I then turned on another DR node
No.3 render from a 2015 machine
last render from a 2013 machine


Give me a shout if you need any logs etc.


2017-05-15, 13:05:39
Reply #4

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
Any clues? This is slowing things up for me - I need to restart all the DR servers before I can use them.

2017-05-15, 13:43:59
Reply #5

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 8878
  • Turning coffee to features since 2009
    • View Profile
There is one weird thing with AcIPC_2_x64 - it seems this module crashed and is reading something from disk. But maybe the issue is somewhere else.

Can you try increasing the VFB refresh interval in system settings? for example to 5000ms?
Rendering is magic.
Private scene uploader | How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)

2017-05-15, 14:03:51
Reply #6

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
Hi Ondra, will give that a try and report back.

2017-05-15, 15:43:46
Reply #7

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
OK, I've done two things - I've removed the Autodesk Update manager program on the nodes and I've changed the refresh amount to 5000. Seems to be working.

I'll try changing the refresh rate back for next render and see how it goes. Will report back.

Adam

2017-05-15, 16:27:54
Reply #8

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
Success!

I changed the update interval back to 1000 and it said 'waiting for render start'.

I then reset it to 5000 again and it's working as it should.

Thanks Ondra

2017-05-16, 12:57:34
Reply #9

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
Almost success!

While it's a lot better than it was, we are still getting the odd node freeze up, even with 2013.

2017-05-16, 13:06:37
Reply #10

sevecek

  • Corona Team
  • Active Users
  • ****
  • Posts: 197
    • View Profile
There were some changes in the last daily build that will probably solve this problem. It would be very helpful if you could try it and let us know if it helps.

2017-05-16, 13:09:52
Reply #11

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
OK, will do. Thanks.

2017-05-17, 14:09:39
Reply #12

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
It's says that it is still waiting, but Max says it's stuck on downloading files. Screengrab from the DR node.

2017-05-30, 18:32:10
Reply #13

adamadam

  • Active Users
  • **
  • Posts: 63
    • View Profile
Have upgraded to the hotfix from the dailies and we are still getting this problem of downloading/waiting for render start.