After installing the latest update to Vue Complete 2014, RenderCow has stopped working on both my nodes partially through a node render. I get the message RenderCow has stopped working.

After the latest update to Complete I was prompted to download and install the latest versions of RenderCow, so I
do have the latest version of RenderCow to match the updated version of Vue Complete.

Prior to this update Vue Complete and node rendering worked flawlessly.

Anyone else having this issue?

Thanks Ken

Pretty frustrated with e-on's latest patch 12003284 to Vue Complete 2014. I tried to render a scene which rendered
flawlessly prior to the update using the external render option.

well this scene will not render with either the external or internal render option. Pretty disgusted with e-on pushing
down a buggy update to a prefectly stable install of Vue Complete 2014.

And before anyone asks....Yes my RenderCows and Vue Complete 2014 are both of the same build version as RenderCows also got updated....

I'm setting up three more server blades for my network.  When done (few days?) I'll do a test network render (Vue Infinite 2014.5, build 2014.500807, release 12776) and report whether or not I encounter this problem.

Thanks kindly. I appreciate it....

     First, I had difficulty just getting Hypervue to acknowledge my cows (note:  I have two 5-cow packs added to the 5 cows included with Infinite).  The Windows network saw all the computers, and I triple-checked both the Windows firewall and the Avast! firewall, and checked port numbers.  HyperVue never did succeed in auto-scanning for all of the cows.  It found about half, and kept popping up some oddball address 198.105.244.240 which isn't even in the right range for my network computers.  I shut off auto-scan, and tried adding cows by name - Hypervue couldn't find them.  I added by address, and HyperVue acknowledged each computer, listing them by name.

     So, I sent four 90-degree panorama renders to the batch.  HyperVue began the prepass, and just as the final tile was completed and sent back to the master, HyperVue hung.  I closed out HyperVue, the batch list, and Vue 2014.5 itself, then began again.  HyperVue again hung just when the final prepass tile was being returned to the master.  The weakest machine in the network is a 24GB HyperThreaded hex-core, and it was not near its RAM limit.

     Some crash data:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    HyperVue.eon
  Application Version:    0.0.0.0
  Application Timestamp:    5376049c
  Fault Module Name:    StackHash_2061
  Fault Module Version:    6.1.7601.18229
  Fault Module Timestamp:    51fb164a
  Exception Code:    c0000374
  Exception Offset:    00000000000c4102
  OS Version:    6.1.7601.2.1.0.256.1
  Locale ID:    1033
  Additional Information 1:    2061
  Additional Information 2:    20616fd8b5482cb11d8f3839844e15fb
  Additional Information 3:    48a8
  Additional Information 4:    48a860a652c001fdad74317e8dcea2fa

.     At the moment, Vue Infinite 2014.5 (build 12500807 r12776) is non-functional as a network renderer.  I sure hope e-on gets this fixed.

     Oh, in case it helps with a diagnosis, my Big_Girls network consists of two workstations and eleven blades.  One workstation runs Vista Ultimate 64bit;  everything else runs Win7Pro 64bit.

seachnasaigh, I think the best thing to do is for you to put in a tech support ticket with all theinfo you include here, it seems quite detailed to me and might be very useful for the developers to see what the problem might be.

     Already done, Djeser.

     I also intended to supply them with the scene file, but their upload file size limit is "1000KB", but my scene is 29.8MB.  I'd also re-un the render (and crash) and then capture the crash log and send it, if they tell me where Vue stashes it.

On the weekend I did a network render "3500x2300" of a new scene using "Superior" quality.

it rendered fine with no issues. Not sure what caused the previous errors...

     KenMo, I have found that some scenes kill HyperVue, and other scenes do not.  I have put in a ticket to e-on, providing links to a filehost to supply them with scene file, crash logs, etc.  Notably, this is the same scene file which network rendered flawlessly in Vue 2014.

~~     E-on tech has duplicated the crash.  They aim for a fix in a "future update".  I don't know if that means a Service Release patch fairly soon, or not until Vue 2015.   ~~**

     If anyone modifies a scene and its behavior in Vue 2014.5 changes from network rendering successfully to crashing, or vice versa, please post what changes you made to the scene and/or changes made to the render settings.

...wondering if I'm ever going to be able to use my network for rendering in Vue again.  Sigh...

     The "2014.6" update, 12501193, release 13490 appears to have restored HyperVue and network rendering capability (I have a batch running now).  :biggrin:

     This update does not appear if you open Vue and check for updates;  you need to go to the e-on update web page.

     One irksome issue is that after all the RenderCows updated, HyperVue still "discovers" all of the old 12500807 build cows - which no longer exist.  I shut off the auto-discover RenderCows feature, and was then able to get HyperVue to only look at the real 12501193 build cows.