Itoo Software Forum

Author Topic: Bug: V-Ray DR Crash  (Read 3388 times)

Mustafa

  • Newbie
  • *
  • Posts: 27
Bug: V-Ray DR Crash
« on: April 30, 2014, 06:56:40 AM »
I got this error on slave PCs when rendering with V-Ray DR



windows 8.1.1 64-bit
3ds Max 2013 64-bit + Update 6
V-Ray 2.40.03
Railcone Pro v2.2.3 Network License

Michal Karmazín

  • iToo Software
  • Hero Member
  • *****
  • Posts: 1490
Re: Bug: V-Ray DR Crash
« Reply #1 on: April 30, 2014, 09:56:29 AM »
Hi,

It occurs just using render slave/s or also locally? Please try to delete railclonevray20.dll file (in the 3ds Max root directory) on all your render slaves and reinstall RailClone with V-Ray DR spawner service stopped. Also double check you are using the same release of V-Ray on all computers included in DR. Hope this helps you but let us know in case of any troubles.

Kind regards,

JTP Vis

  • Full Member
  • ***
  • Posts: 107
Re: Bug: V-Ray DR Crash
« Reply #2 on: April 30, 2014, 01:21:30 PM »
I've had this problem for some time now on the render nodes only. I just accept it and restart the spawner on the render node.

I'll try the fix suggested and let you know.

Bill

Mustafa

  • Newbie
  • *
  • Posts: 27
Re: Bug: V-Ray DR Crash
« Reply #3 on: May 01, 2014, 11:18:53 AM »
It just happens on the slaves PCs and doesn't occur on the master PC .. (each PC render the scene locally with no error when DR is OFF)
I have the same version of V-Ray & 3ds Max on all PCs ..
sometimes it resolved by restarting the spawner but at the last time it doesn't work at all .. I had to convert RailClone to EditPoly to discard it from the scene ..
Edit: Restart the spawner is working but I need to restart the spawner each time I press render
I will try your suggested solution and tell you what I got ..

Regards,
« Last Edit: May 01, 2014, 05:36:19 PM by Mustafa »

BI1654

  • Newbie
  • *
  • Posts: 38
Re: Bug: V-Ray DR Crash
« Reply #4 on: May 08, 2014, 12:52:11 PM »
Have also had this problem for a while, but is intermittent

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3158
    • iToo Software
Re: Bug: V-Ray DR Crash
« Reply #5 on: May 09, 2014, 09:52:50 AM »
This type of intermittent problems may be difficult to fix, more if happens within of V-Ray.

Please, send us the vraylog.txt files to support@itoosoft.com. Hopefully we can get some useful info from them.
Carlos Quintero
iToo Software

BI1654

  • Newbie
  • *
  • Posts: 38
Re: Bug: V-Ray DR Crash
« Reply #6 on: May 12, 2014, 10:46:53 AM »
I have it happening at the moment on a scene Im working on.
Which Vray log files do you need? The DR slaves?

Any idea where I can find them?  :)

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3158
    • iToo Software
Re: Bug: V-Ray DR Crash
« Reply #7 on: May 12, 2014, 11:46:23 AM »
Yes, we need the VRayLog.txt of the slaves, which is created at c:\

If this issue happens always with a specific scene, please send it as well. It may very helpful to identify the problem.
« Last Edit: May 12, 2014, 11:50:29 AM by iToo »
Carlos Quintero
iToo Software

JTP Vis

  • Full Member
  • ***
  • Posts: 107
Re: Bug: V-Ray DR Crash
« Reply #8 on: May 14, 2014, 05:26:39 PM »
Ok, so I have not tried the fix suggested, but here is a bit of an update:

I have just updated all our machines to the latest version of Forest pack and have just had the error occur, so it is not fixed in the latest release of Forest pack. However, for me it is a very specific time, and process that causes this error. In order for me to get this error, all I have to do is: start a local render with v-ray distributed rendering enabled and a selection of nodes being used; then when the process is started, but the nodes have not actually contributed any buckets to the pre-passes, just hit cancel in the v-ray render dialogue to cancel the render. The last time I did this (only a few minutes ago) I got the error locally, although this doesn't usually happen, and on all the nodes. Hitting cancel on this error dialogue will reset the max dummy on the nodes, and you are ready to go again.

In brief, I think it has something to do with the calculation of the forest pack geometry ready for rendering, which is in some way connected to vray, and yet when you cancel the render in the middle of this process it doesn't like it.

I hope that helps.

EDIT: I just realised that this post is in the rail clone forum. I have been having the problem with forest pack, but I assume the error is caused by the same problem. I have both, so don't know which is causing the problem.

Cheers,

Bill
« Last Edit: May 14, 2014, 05:30:35 PM by JTP Vis »

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3158
    • iToo Software
Re: Bug: V-Ray DR Crash
« Reply #9 on: May 15, 2014, 05:20:21 PM »
Thanks for the information, Bill. We'll make some tests following your indications.
Carlos Quintero
iToo Software

BI1654

  • Newbie
  • *
  • Posts: 38
Re: Bug: V-Ray DR Crash
« Reply #10 on: June 02, 2014, 10:52:37 AM »
Any updates on this issue?

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3158
    • iToo Software
Re: Bug: V-Ray DR Crash
« Reply #11 on: June 02, 2014, 11:41:30 AM »
No, sorry. Until now we could not reproduce this problem in our test machines. This is essential in order to debug and fix it.
We have modified slightly the VRay initialization in RailClone 2.3.0b (to make if safer), but we don't know if that change would help with this problem.
Carlos Quintero
iToo Software

JTP Vis

  • Full Member
  • ***
  • Posts: 107
Re: Bug: V-Ray DR Crash
« Reply #12 on: June 02, 2014, 06:18:53 PM »
Did you get this error to appear when you tried my "method"?

Cheers,

Bill

iToo

  • Administrator
  • Hero Member
  • *****
  • Posts: 3158
    • iToo Software
Re: Bug: V-Ray DR Crash
« Reply #13 on: June 02, 2014, 06:56:55 PM »
Did you get this error to appear when you tried my "method"?

Unfortunately not. May be it fails more frequently in render farms using many nodes, but in this case we must use a single node running under a debugger (if not, we cannot trace the problem). Even on these conditions, usually we must reproduce the crash several times.

The main problem is that the crash doesn't generates a minidump (which is easily traceable).
Carlos Quintero
iToo Software

Richard Birket

  • Full Member
  • ***
  • Posts: 141
    • Specialists in visualisation
Re: Bug: V-Ray DR Crash
« Reply #14 on: June 23, 2014, 03:00:50 PM »
We are also getting this. Any solution?
Kind Regards,
Rich

www.blinkimage.com