When I'm rendering with Vue it seems to suck up all my systems power ( win xp, 800megs ram, celeron 1.1 gig). Other 3d programs seem to leave you enough memory that you can still work on other things, surf the web, etc... Anybody know a way around this? Is it simply a matter of adding more memory? Or will vue just use the max amount of that too? Thanks

You may have many resident programs open (all these icons in the taskbar) or many icons on your desktop. Close them before you use Vue if you encounter memory problems. Uncheck OpenGL. Normally with a 1 G and 512 Ram I was working normally with Vue. But, of course, there are some limits. How many objects do you have in your scene? How many polygones? Guitta

Vue has the problem that it don't always clean up the memory after usage. You can always add more memory but it's going to use all of it anyway. If you render an Image, stop when the memory is full, save image and scene, end vue, wait until memory cleaned up. Start vue, load scene, resume render. Gebe: Try render the free fountain animation, and see what happens.

I have not tried the "free fountain animation" (???), but I already said that there are some limits. My 2.8 G/1024 RAM machine can more then my 1 G/512 RAM. Every software and every computer has a limit as far as I can see:-). Closing all these programs running in the background is the first thing to do. That's VERY important. :-)Guitta

Think you need a can of bugspray ;) MightyPete wrote about a memory cleaning software, when I wrote about this last time. Can't remember wath it was though. Oh by the way, you shouldn't surf and use other software when rendering. It slows down the comp and can cause errors. I always get this problem when rendering some materials, so what do you render? Gebe: It's a bug I tell you, it's a bug. eeeeeeekkk.. ;)

what not wath... arghhhhhh

LOL, just LOL

Attached Link: http://www.memturbo.com/

YA I use MemTurbo but there is others around now too.. Keep this in mind, Some of my renders have used all available memory and 3 more gigs on the disk as virtual memory. You never said what operating system but I'm assuming XP. The operating system is the pig of wasting memory and not Vue. Micronot uses memory very poorly. If you want things to run smooth then you need some kind of memory manager. It's the thing that's missing in winders. On thing this program is way cheaper than adding more memory and you can try it for 30 days for free to see if it cures your problem. My point: Don't matter how much memory computers I've used have had Memturbo always made the puter run way better. If your running XP get the task window up and running and see what is running in the background. I found a few programs on Micronot machines using lots of resorces but with no beneifit to you what-so-ever. One of them can't remember the name but it's by micronot and it's sole purpose in life is to report back to them what your doing.It's does not remove as spyware even though that what it is and the puter works just fine without it. It's a quality agent. Hey this is not beta it's my working machine! Delete ! Here is a good place to look up what the heck all those programs are doing... http://www.answersthatwork.com/Tasklist_pages/tasklist.htm If you go to the home page of this place there is more tweeks. If you can't find one listed here that is running in memory then just search for it on google. Somebody will have something on it on the web and if you need it and how to get rid of it if you do not.

You don't need any memory manager with XP. XP is extremely efficient about giving you back all your cache. Under Win98 it's optional. I had more memory free lowering my vcache under Win98 than using things such as MemTurbo. Unfortunately Vue and Poser aren't system friendly about multi-tasking during a render. They take over your screen too. You have to run programs on top of them which can cause problems sometimes. Maybe at some point Vue will send its rendering off to use Idle time like Bryce does and allow you to minimize during a render. Let's hope for that. (I have no hope for Poser, though).

Mighty Pete and I went round and round with this issue last year. How ya doin' Pete? The easiest thing to do is shut Vue down and open it back up before you render. It'll give back the resources so your render will go smoothly. There's no way to 'fix' it. Do follow the above tips...background apps, mem management etc. I'm convinced that Windows and Vue do not get along when it comes to virtual memory access. I've gotten in the habit of shutting Vue down and opening it back up between major tasks. It's the only way I get anything accomplished in it. You'll get used to it. Maybe it'll be better in Vue 5 whenever that is. Yours, Monsoon

From my experience there is nothing you can really do to improve multi-tasking with Vue. (using winxp here) Open your task manager and look at the processes. Then start rendering even the most basic scene(new with no objects) at say 800x600 at broadcast quality. You will see the cpu usage for vue go to 99 and most like 100% for the entire machine.

I have found that multi-tasking is NOT an option with Vue. :)

Two computers will cure it. Vue is not the only program that does this. Almost all my programs that render will do this. Welcome to a serial world. Oh changin the cpu priority for Vue from normal to idle will make it more as expected but other glitches will show up. Two computers are best. Render farm ! Ya.

"Oh changin the cpu priority for Vue from normal to idle will make it more as expected but other glitches will show up." Are you just saying this or do you know what glitches will show up and why? There is noooooo way I can get a second computer.

Oh well I'll tell ya I wrote this huge reply to this tread and explained it all but it took so lonk to type it when I pressed submit it vanished. I copied it first just in case. Look I had this same problem with Mojoworld. Mojoworld is even harder on the cpu that Vue. It make the computer unusable while rendering. I had a program that showed the cpu usage. The link for it is posted here somewhere cause it was that link of how I found it in the first place. I don't know the name of the program. This is not my computer I'm using so I cannot look it up. In XP and 2000 you can adjust the cpu priority of most programs. You can't in ME and 98 without some extra program. The glitches. The screen refresh. Things in the active render will vanish from the screen but they're rendering just fine. File will save just fine. Just ignore it. Say it's in idle when a complete line is done. The line will save fine but it may not show it on the screen. In Mojoworld whole blocks vanish but they're there also when you save the file you just can't see them. What you do is set the program to idle. It will render at almost 100% cpu when it's in focus but if you start up something else it will drop to almost 0% while the other program is being used to do somthing. As soon as extra cycles are available it will shoot back up to almost 100% rendering but it will back off to allow other programs to run if needed. This is what most people expect the computer to behave like. Normal cpu priority will not give you that when it comes to rendering but Idle does. Search google for "cpu priority" with quotes for instructions on how to change it for programs. There is lots of links, you want only the links that show you how to set individual programs and not the entire computer. Other glitches. Crashing other programs while doing this may crash the render too. It's adds a bit of risk.

Attached Link: http://anothertaskmanager.cjb.net/

This program will do it in 98 and ME. I don't think you need such a program on 2000 or XP. The setting does not seem to stick. The settings. Every time you start up the program you have to reset it to idle. I think there is a way to make the short cut to the program auto set it to idle but I don't know the syntax. There may be other registry hacks that could do the same thing but I don't know how to do it. Use with care.

About the only way you can multitask with Vue is having a dualie board (at least I'm assuming so; haven't gotten one yet, and won't until I can 'justify' it). Even Rendercow will eat 99% of a CPU if you give it priority, so it can't really be blamed on the most common culprit in a Windows app, the GUI code. What -I'm- wanting to see is whether there will be enough demand to entice E-on to port Vue to X86-64. No problem with memory limitations there, methinks! And with those reports of the ease of the porting....

Thanks for the info, Pete. I used to play with priorities on my Amiga, though you really didn't have to on that. I'm really hoping Eon will address this. Have you ever used Bryce? As of Bryce 4 it went to idle time for rendering. You see no difference whatsoever when you're inside the program. None. Most people don't even realize it. While rendering you can CTRL-M to minimize the program and go on your merry way. Render speed is barely affected at all since the processor spends most of its time waiting anyway.

Thanks for all the responses. Many good suggestions!

Speaking of memory, could someone please tell me what the optimum settings are for virtual memory in Win2k...HD 30 gigs unused, AMD 1700, 512 RAM, 64MB GeForce 200. Right now they are set at (as per a friends recommendation): initial size: 1536 maximum: 3072 total paging file size for all drives says: min: 2 mb recommended: 766 mb currently allocated: 1536 current registry size: 26 mb maximum: 88 Thanks, Dawn

Good enough. You have a large min. 1.5 gig. Whatever I have mine set to 1 gig. Should be just fine.