Maya 2017 U4 and ipr

[francomanko]

Hi, is anyone else getting a lot of crashes when using IPR render with maya 2017 update 4? Im on my 10th today. I havent a definate clue what it is, except it seems connected to pausing ipr, region renders or maybe distributed ipr... I just updated to the latest stable version of vray but no improvement.

I'm not expecting a specific solution and am testing to see if its the distributed element, but wondering if other people are finding this to be the case too.

Just to check, cpu IPR rendering and progressive should work fine with a renderfarm in theory yeah?

[francomanko]

I did get this error when clicking reload on a texture whilst ipr was running..

// Error: line 1: V-Ray : Unhandled exception occurred, will exit render loop. Unhandled exception c0000005 //

and when i clicked rerender it crashed. This wasnt a distributed ipr cpu render..just my local.

[francomanko]

yip twice in a row now...same thing..click reload texture and i get the error...but scene only crashes when i click ipr render again.

[francomanko]

ok so i made a new scene with a sphere and texture...ipr rendered.....clicking reload on texture is fine as long as the image has no changes....if i take the texture into photoshop and do nothing but re save over the file...when i click reload the ipr brings up that error....only difference is with the new scene, maya didnt crash when i rerendered.

[yolov]

We'll see if we can replicate the crashes here, but any info that you might give us to help us out in the process is more than welcome: OS, vray version (build number).

I think the issue where a texture is not reloaded after being changed on disk is known, but we still haven't found a fix for it.
And yes, IPR and progressive renders with distributed should work fine.

[francomanko]

sure sorry, win7 sp 1 maya 2017 update 4, latest vray stable 64bit.

[yolov]

We've had no luck in reproducing this. Have you tried re-installing V-Ray after you've upgraded to update4 ? There is a slim chance the update itself might have broken something, although I doubt it.

[francomanko]

ive installed v3.6 an problem doesnt occur..I'll revert back when i have time to check.