I have been struggling now for days trying to get Vue to save a high resolution graphic. There are so many bugs in this software that I have just about given up! When I go to save to disk at the very end it says that it's unable to write to the disk because there's not enough disk space. I have 230 gigs free! If I try to save to the screen it gets about 1/8 through the process then just disappears to the desk top! I have tried everything including a complete re-install of Vue. I Now have to go tell my client that I can't do his job because the new $600.00 piece of software can't save his image. I have written many e-mails to Tech support about dozens of bugs , sent many files, and nothing has been fixed yet. I am really at the end of wasting my time with this package. I am tired of being a beta tester and not getting anything for it. Someone please tell me what secret there is to saving a high res image. The image size is 17"X11" at 300dpi. That's a walk in the park for Lightwave. I am running on a Mac G5 2.7 gig machine with 2.5 gigs of ram, and OS10.4.2. What a major disappointment!!

I know it's very annoying Tony, but as I said before....E-on are now trying to invite studios on board. They will not tolerate buggy software...I know, I tested Vue 4 for a studio that would have meant a complimentary software package for up to 20 animators if it met their standards....it didn't. Even though I used it successfully, and still do within freelance (where I could/can cope with the disruption in workflow) I had to recommend that it wasn't suitable within their pipeline and deadlines. As the saying goes, "you live and die by the sword" and e-on's sword is Vue;) Cheers

I save more often than when playing a first person shooter on hard. That's the only way to keep from losing your work all the time.

That problem went away for me when I rolled back to the 277255 build. I also told Poser 6 not to use an external morph data file when saving my figures. Before that, V5I told me my hard drive was full when it wasn't. And it took forever to save anything huge from it when there were corrupted models in a scene that imported badly.

Message edited on: 08/12/2005 19:57

I have rolled back ro 277255. I just rendered a single tree at 17"X11" 300dpi and it did it. I wonder if it has something to do with using multipass?

I have just done a quick couple of test renders at the settings you are using, one test on a single machine and the other using hyperview network render, one a simple scene, and the other a medium scene with eco ect, and they both worked fine. I am using a PC so not sure why you are having these problems on a MAC. I to am using build 277255.

Videodv, did you try it using the multipass feature? I think that may be the problem.

no, I will try it with multipass now and see what happens, I will get back to you shortly and let you know how it go's

Oops sorry tony what mutipass options were you using and I will match them to see how it go's.

Object Masks and Material masks. The file that I'm having trouble with is about 800,000,000 polys. It's about 8 meg can I send it to you?

Just tried another test using more or less the same settings and it worked fine. You can send the file no problem and I will have a look for you and see if we can sort your problem out asap.

Do you have an e-mail address? The zip file could be about 8megs!! Today I tried saving a multipass image and it worked fine on a small image. I wonder if i'm doing something wrong when I save it. First of all, can you only save amultipass image from the screen? It seems that if I set up multipass then say save to disk is when I get nothing.

Hi Tony I tried it on save to screen also and it worked fine so maybe as you say saving to disk is the problem. I have not used mutipass before so I am not sure of the whys and where fores of it, but I'm sure you are doing nothing wrong when saving. While I am waiting for your file I will try the test scene here again but this time I shall save to disk and we shall see what the outcome is. I have just sent you an IM with an e-mail address that should let me receice your file. Will get back to you shortly.

OK Tony I have had a look at your file as far as the scene it self go's I cant see anything to change that will make it faster, but on the rendering side with the options that you have it will not let me render it is saying I need at least 2g of memory I have 1g. The test render that I did to disk worked fine, I then setup my test scene with your render settings/mutlipass options and got the same memory message as above! If I remove the mutlipass options it will let me render and it will take approx 36hours acording to my machine with your setting but if you go into the Anti-Aliasing options and reduce the quality setting to 70% and the min to 9 and the max to 20 then this renduced the rendering to around 18 hours, I have heard that these settings give a good result over render times. As I cant do more without more memory Im not sure how you can improve things to get you going, maybe look at the multipass options, I see that you have all of them ticked maybe you could untick some of the ones that are not so important and it will work for you as well as others. I see that someone over at cgtalk has been doing some renders at your size so maybe they can give you more advice. Sorry I could not be more helpfull, I hope you get this sorted very soon, if I can of any more help I will try my best to help you. videodv.

I think I will try to skip the multipass stuff. I have one more question for you though. I am trying a camera fly through and need to solve one other problem. The camera starts at the shorline then moves up to an over head view. I'm using smooth velocity and ease in/ease out. At the beginning I get this extra camera movement down before it begins to rise. How can I stop that? In Lightwave it's a simple fix in the graph editor.

If you have Lightwave, you might want to export the scene to LW, do the camera, then import it back. LW, as you say, is easier to handle than Vue when it comes to camera movements.

Check your timeline and make sure you have not put an extra key point at the begining (I did this many times when I started) just right click on the timeline and zoom out to make sure, if you have an extra one there just delete it. Or open the options for your camera on the right you will see the function box (the little box with the half white thing in it) right click on it from there you can edit the function. Or use the syncro plugin as DMM said (This is what I prefere I use cinema) to get the best for camera motion.