Quote - Just noticed in the e-on Vue 5i/pro forum that they said the developers can't find any unfixed memory leaks.

Is that right? They can't? Well, they don't seem to be looking very hard. Here's a little demo (this is the latest 5.09 release I have). I have an undo level of 1.

1. Open Vue; empty scene. Resources = 75%
2. Import two Poser figures (big ones). I now have polys 492,901 from 16 objects and 33% resources. OK, I can live with that if it stays at 33%.
3. I'm now going to start moving the figures round. Just dragging them with the mouse and counting the moves. I get to thirteen and up comes the warning that resources are now critical. I check and resources = 24%. Thirteen operations that add nothing to the scene, and 9% of the resources have leached away. And that's not a memory leak?
4. If I keep going I'll continue to see the resource level drop at the same rate until Vue crashes. I'll try something else. Delete one of the figures. Resources = 20%. WHAT!!! I've reduced the scene and now I have less resources. And e-on can't find a memory leak?
5. I now select New Scene, declining to save the old one. I now have an empty scene again. Resources = 54%. So where did that extra 21% go, then? No leak?
6. I tried repeating the experiment but changing the figure in the box "Keep track of operations until resources drop below" from 25% to 50%. Now I get 31% instead of 33% and after thirteen moves it has dropped to 26% rather than 24%.
7. The flush history button does nothing to increase the resources.

Now don't tell me I have to have purple RAM or some obscure BIOS setting, I'm an artist, not a computer technician. I have a new PC and it's set up the way the maker set it up. If Vue can't run correctly on what must be a pretty standard system, there ought to be a big warning on the box or something. When I buy an expensive piece of software I expect it to work.