Author Topic: Update 1.4 - Problem with rendernode - 3dsmaxcmd related?  (Read 2061 times)

2016-06-17, 11:34:37

ikercito

  • Active Users
  • **
  • Posts: 111
    • View Profile
Hi there,

A couple of days ago I updated Corona to 1.4 (from 1.3) and everything looked brilliant. Today I tried to fire up a distributed render and I'm getting some miscommunication between workstation and node... Last time I checked there were no problems launching 3dsmax 2014 on the node, but I'm getting some 3dsmaxcmd (i guess) errors after the update.

Can anybody take a look at this please? Here are the logs.

Thanks!

2016-06-17, 11:45:28
Reply #1

ikercito

  • Active Users
  • **
  • Posts: 111
    • View Profile
Sorry... I kind of solved it myself. Max was set to always run as admin on the node. Unticked it and now it seems to be working fine.

Thanks anyway! :)

2016-06-17, 14:48:32
Reply #2

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12758
  • Marcin
    • View Profile
That's interesting. Thanks for the report and solution. We will keep it as it might be useful in the future.

Just some keywords: pipe , Got no response from 3ds max , aborting

Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2016-06-20, 13:41:22
Reply #3

Ondra

  • Administrator
  • Active Users
  • *****
  • Posts: 9048
  • Turning coffee to features since 2009
    • View Profile
I remember somebody solving this exact problem by reinstalling 3dsmax... we are currently not aware of better solution
Rendering is magic.How to get minidumps for crashed/frozen 3ds Max | Sorry for short replies, brief responses = more time to develop Corona ;)