@agiel, Hi agiel, I just upgraded from Vue4 and the upgrade I purchased is the current build.

I'm in discussion with them about a refund, which they've agreed to mimus the $50 voucher I spent on Cornucopia but that leaves me with models I can't use anywhere else so I'm still out of pocket!

I'm seeking advice from our Trading Standards people on my next move, it may be that they will need to be involved.

I don't accept shoddy goods when buying clothes, food, cars or anything else, why should I accept it when I buy software!!

Quote -
So, you can't use the 'Performance' tab of the Windows XP Task Manager to look for memory leaks (but, if you are using a special program designed to monitor WindXP memory usage, that's different).

What you can use, within Vue itself, is the resources value in the options window. I check this from time to time, and it goes relentlessly down just from ordinary actions. When it gets below 15% I have to save, quit Vue, start it again and reload the scene. Otherwise Vue crashes.

Switching off Open GL slows the rate at which resources evaporate, but the wireframe display is very hard to read, and it becomes impossible to place things accurately.

Thanks for that Phantast, going to start checking there.
Just noticed in the e-on Vue 5i/pro forum that they said the developers can't find any unfixed memory leaks. There is also some interesting info about ZoneAlarm and Windows XP security settings sometimes causing crashes (not memory errors). Topic is "Crash, crash, crash ....crash", lol.

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.

That's interesting. I'll try the same.

So, i guess you have reported the above to e-on through a support ticket. What did they have to say?

Ran a similar test. As i expected, your Vue (or PC or OS or all) has problems which mine doesn't. I'm using latest build of Vue 5 Infinite, WinXP Pro SP-2, 2GB memory. Page File setup (virtual memory): C: = 100 - 2048 MB, D: (an identical 2nd drive) = same 100 - 2048MB.

1. New scene. 74% resources reported.
2. Load 1 Poser 6 V3SAE + NativeAmerican clothing (26.3MB) each. Don't have any huge Poser figures. 64% resources. Loaded same again for 2 figures. 64% resources.
3. Moved 1 figure. 63% resources. Moved each figure in turn, for a total of 15 moves. Stayed at 63% resources, never changed.
4. Deleted 1 figure (causing it to be stored in my 5 levels of undo). 54% resources.
5. Undid deletion. 34% resources. Deleted other figure. 35% resources. Undid deletion. 34%.
6. Swapped figures in and out of storage by deleting/undoing several times. Same resources.
7. Imported 2 more of same figure. 37% resources (Vue seems to be recovering some resources)
8. Loaded 5,000 unit square plane. Applied checkerboard material. 39% resources.
9. Created an Ecosystem on the plane material, populated with 38,109 V3s (same figure, but in .vob format). 34% resources. 7, 050,485,761 polys reported. Vue is still reponding briskly and no problems.

I also have the latest build and Windows XP SP2, but Home not Pro. I have one Page File 2046 Mb. And 2Gb RAM. The two pz3s I loaded are both about 66 Mb in size, so it was a much higher load than your figures. The higher the resource load, the more rapid is the decay just from ordinary moves.

You still lost resources deleting figures; you went from 63% with your two figures down to 34%. Try getting back to 63%.

1. Closed my Vue memory test scene (since i thought i was done testing). Just opened it again. Resources now 55%.
2. Set number of undo to be stored from the previous 5 down to minimum of 1. Closed Vue and opened to same scene. Resources still 55% (maybe this only affects the next scene created?).

Phantast - what are the sizes of the textures on these poser figures?

Ahh tomorow my weekend starts,back to using Vue again who knows maybe i will create something good this weekend. Looks like i crreated quite a good disscusion. Thanks all for posting on this thread. Looks like some good stuff came to the surface!

Greetings . I used Vue4 and had no problems what so ever  now I just started using Vue5 Infiniti and I have no list of layers  how can I fix that please .

Also where do I put those Addons that we can get such as plants,trees buildings and such I have no idea where to place them or in what folder they would go Help please anyone!

With 5i you have to create layers yourself. Down the bottom theres a folder icon..that's add new layer.

As for addons, you can put them anywhere you like. Vue first looks for them here though -My Documentse-on softwareVue 5 Infinite.

I was cursed with Vue 5 crashing constantly when I bought it. The following advice from "surveyman" on this forum almost completely solved Vue's problems for me:

"Check your 'Swap File' size and location. 'Right-Click' on 'My Computer' and select 'Properties'. Select the 'Advanced' tab and select the "Settings" button in the 'Performance' section. In the 'Performance Options' dialog box, select the 'Advanced' Tab. At the bottom there should be a "Virtual Memory" section, select the "Change" button. Swap File is properly called Virtual Memory in Windows.

In the 'Virtual Memory' dialog box, look at the "Paging File for selected Drive". That will tell you where the Swap File is located. Ideally, your Swap File(Virtual Memory) should be 2.5 times your physical memory. Change your Swap File size by specifying the drive your Swap File is on, clicking on the "Custom Size" radio button, and typing in the 'Initial Size' and 'Maximum Size' as "3000mb" (close enough to 2.5x). Yes - they should both be the same number - this prevents the Swap File from constantly re-sizing itself and chewing up memory and HD time. When done, click the 'Set" button."

I then defragged my HDD and ran Registry Mechanic and since then (over a year ago)  Vue has only crashed a couple of times and never at the expense of losing any work. I agree e-on's support is crap- the Vue 5 "manual" in particular is absolutely pathetic. It should have the above Swap File Size advice printed in BOLD dayglo letters on the front cover.

Jackson

Thank you for your quick response  it helped big time thanks again

Setting your Windows XP pagefile (swapfile) to an arbitrary multiple of your physical memory amount is often recommended, but is not the best practice. It's a kind of geek urban legend.
It's great that people offer helpful advice like this, but unhappily it's also quite easy to spread advice which is not the best, with the best of intensions.

For an expert discussion of Virtual Memory and and best practices, see:
WinXP Virtual Memory

I'm a PC consultant, as well as a 3D graphics writer and web services guy. My free PDF brief on setting up and maintaining a Windows XP PC is at:
Free Windows XP setup/maintainence brief, in PDF format

_jc  'Art Head Start' e-book: Learn digital art skills $19.95
'Art Head Start.com Free chapter, Vue tutorials, models, Web Tutorials Directory.

Thanks everyone, I've found a lot of useful info in this thread.

For those who believe that most of the crashes in Vue are due to PEBAC, you are so very sadly mistaken.  Here's my system and here's what I've been doing:

P4 3.2 Ghz Processer, 3 Gigs of RAM, nVidia GeForce FX5500 256mb, 2 200 Gig SATA drives with LOTS of free space.

I right-clicked on my computer, went to manage and then looked at what services were running and what they were tied to.  Based on that, I found which processes I could shutdown that would not interfere with OS performance.  So, aside from what Windows needs, nada was running, just Vue 5I.  When I go to final render, I can't tweak the settings for more detailed rendering too high or Vue runs out of memory the second I try to render.  Sorry, but IMHO, that is an issue with the app, not me.  Now, I am will to say that there are setting tweaks in Vue that I am unfamiliar with that might be helpful to me, but expecting the app to function within the boundries of the settings provided, I don't find to be too much to ask.

I like Vue, I will continue to use it and I may upgrade it, but for these guys to believe there are no issues with memory and Vue is a bit on the silly side.  I think you can get amazing renders from this and can even make images that look like a painting, heck going through the gallery here proves that.

One thing I did learn today is to check the resources and save often.  And hope someone at E-on catches on to this and finds a way to fix it.