Wed, Dec 25, 7:55 AM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)



Subject: Vue Disappears


bonnyclump ( ) posted Tue, 18 May 2004 at 9:26 PM ยท edited Tue, 24 December 2024 at 8:14 PM

Hello, has anyone experienced vue disappearances when using render cows. Whenever I put motion blur on and render over the network the program quits after 3 minutes. If I turn off motion blur it render fine over the network. Is there some type of limit I'm running into when using an updated vue4pro?


Dale B ( ) posted Wed, 19 May 2004 at 7:43 AM

The Motion blur implementation in VuePro is something of a memory hog. How much physical RAM do you have, and how big is your swapfile? And which update? Some of the VuePro updates have introduced issues....


bonnyclump ( ) posted Wed, 19 May 2004 at 11:54 AM

Wow! I had no idea. I have 1G of ram, with 3000 to 4072 swap. The update is 4.53 270045. Its the latest update and it works find otherwise. I can render the picture without the cows and it works but with the cows no success. I thought the cows would be good to use because I wanted to try for better quality motion blurs without the wait. Right now I'll just wait. I could add more ram to either computer. The cow has 512 ram with the same swap and the cow is updated. Maybe the the 2nd pc doesn't have enough ram. The computers both work well otherwise.


Dale B ( ) posted Wed, 19 May 2004 at 9:19 PM

How many Cows are you running? One thing I've found in my work is that they are vulnerable to packet collision, and you can run out of physical ram if you are starting several Cows simultaneously, and you have large textures. If you have the latest update, then that eliminates the handle issue that the update twice removed introduced. Try starting a render with 1 Cow, wait until all the frame and texture data has been sent, and it is rendering frame 1, before starting the next Cow. If this is a resource issue, that -may- solve it. If it is a network issue, having the operating times of the Cows offset from each other should take care of it.


bonnyclump ( ) posted Sat, 22 May 2004 at 12:10 AM

Intersting. I found out that if you don't use static ip's the names of the cows get mixed up in hypervue, so when you think you are rendering to cow a. it is really rendering to cow b. I also use different ports for both pcs 5002 & 5003. I only use 2 computers and the 1st pc has hypervue and a cow while the 2nd has a cow. I sometimes add a 3rd pc but anymore pcs always screws up the farm & lends itself to the inevitable reboot or reboots. I gave up and just rendered the scene with one pc. I wanted to compare different motion & render settings over the network but I'll just leave out the network variable. Thanks alot for your help.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.