My vue 5 works perfectly, renders sharp (with my own settings) and fast.... it is THE vue to have...(infiniate)... but aside from my newly installed "final" vue 6 taking forever to render spectral clouds I honestly never had it crash on me...I think I will stick my flying fairy in there, add some plants and REGULAR clouds...and see what happens...now that I found a way to make the aa NOT BLUR the pic...

I just hope they get 6 as good as 5 in a year or so... ;)

I was freaking earlier today. My Vue6skinshader was not working. Then I remembered I had un-installed  Vue before I installed the final version. It works now. Hey, at least I didn't blame e-on for that one. LOL

I'll say a few things here as I have been very vociferous over the final release problems as I have certainly experienced them!
Firstly, there is a HUGE memory problem in this final release, no question and their tech support have admitted it to me and Iloco at the very least, that is a fact no question!

I did a scene yesterday, spectral atmo, 2 terrains [1 with eco-system], 2 poser imports [V4 and a building] and 1 spot light.
I had to constantly purge my memory to get the scene done and I mean constantly, every rotate, move or adjustment zapped my resource to 15% or worse. OK fine I got the image done and posted it, then someone pointed out an error in the image so I went back in to adjust it and this is where it gets scary!!!  Opened the scene again and straight away on epening I got a resource has dropped message and when I checked it was down at 8%, now on opening a scene that is scary in anyone's language. I never had this on the pre-release which incidentally I was very happy with and even opened a ticket to tell them that too so I'm not a whiner for no reason or for the hell of it!!  There is a problem with the final release!
Now my specs are P4  3.4GHZ HT, 7300GS Nvidia graphics, 2 Gig RAM, 350Gig HD
Not a shit system by any standards!!

All that said dstephany, when that memory leak is sorted [hopefully] then version 6 of Vue IMO will be a fantastic bit of kit, no question but if it doesn't get fixed it will be consigned to the waste bin!
Also if some aren't getting problems I don't understand why, you may well be one of them if you were to buy it, maybe you'd be one of the lucky few who doesn't get a problem and I mean few. It's not just on this forum that you'll see complaints, it's other forums too!!

Everyone who claims this....or any....piece of software....has no issues, please clap your hands. (listens to the mournful sound of the wind through the audience as no one makes so much as a fartnoise). Good. That's settled. There is a difference between 'I'm not having that problem' and 'There are -no- problems'. And before anyone gets defensive, re-read the thread. Maybe even change the names around, so you aren't seeing your words by you, but your words from another 'person' (actually, to be most effective, print this out then alter the author names, then put it away for a week or three. Then read it, and see how it reads. Might be surprised....) Let me ask those who are having such troubles; Downloaded, yes? Restarted? Yes or no. Next. What is the actual bit count of the final download? Mine is 698,619,233 bytes in size, or 699,527,168 bytes on disk. I got this in one download over cable. Does this match what your vue 6 infinite install folder weighs in at? Did you uninstall the pre-release before installing the final? Did you run a registry cleaner (or manually delete all the eon regkeys) before installing the final? Did you delete or move all the V6 pre-release files from the eon folders in my documents before installing the final? I won't try and get into all the other factors that could be making any one installation worse than the others. I've tried, usually to be met with a rousing round of 'But My System Can't Be The Problem Because---!', and it frankly isn't worth the static. I keep a list of the -order- I install things in, because that can have a tremendous impact on how stable =everything= is. I daresay far too many just pile things in willy--nilly, and couldn't be bothered to clean up an install or uninstall, despite the decade plus reality that Windows couldn't wipe its own ass with a harem of one hundred seventy two scatophiles to help it and a virgin rainforest's load of toilet paper to practice with.... We now return to our regularly scheduled program....

the fixer did you gt a repoly back from tech on your tech ticket about the resourse issue.

Here is mine.  Quote:
Hmmm that's pretty strange, because the code for evaluating free resources is now exactly the same as before, there is absolutely no difference. Are you sure the scene you are editing isn't really eating up resources because of heavy content?

Now that said Let me try and prove there is a problem in a simple way.

I have Vue 6 installed on my best computer and getting low resoruses as in the final beta.
Using a scene I get down to 6-8% resourses and  purge doesnt bring it back to anywhere near what it should.    Everything is very sluggish and so slow to work with in the final version for me.

Now I have a backup computer which is no where as powerful as my graphic computer with beta before the beta final so I can compare different versions of vue releases.
  I can take the same scene that I have a bad resourse problem with and not have it on my 2nd lower grade machine.  Resourses only fall to 79% compared to 6-8 with Final.

  I think what I see and do speaks for itself and I dont want any of the geeks to say I am whining when I can back up my words with pictures or anyone is welcome to come by my house for a visit and we shalll talk for a spell and do some comparsions.  

What it will take to get this fixed I have no idea with so many biased vue users who says it works for them and don't care one iota if it does for us is beyond me.       I could wish them bad luck but I am not that type person.  Just give us who do have problems some slack and help us get outs fixed.   Is that asking to much since yours is working perfectly as some have stated.

DAleB I ahve done all the above to eleiminate all the problems I could before doing any install.
  I manualy clean my registry as the cleaners usualy give more problems than they solve.  Some will disagree but so what thats normal.

Read how I have two computers set up to compare versions.  should speak for itself.
I know the routine and was beta tester before the last go round of which being so outspoken I knew id never be invited back but hey no problem at all from me.

I appreciate your post of help and wish what you said would solve my problem but it hasnt as I have done what you have said to do...     Been there done that so many times its practical routine anymore. :)

Although a good system, a P4 HT coupled with a 7300 will barely meet the Vue 6 Specs.  The 7300 has basic OpenGL support, so your card may be running 1.5 or less rather than the 2.0 that is current.  HT is notorius for memory leaks because many applications do not use the HT technology effeciently, which can cause excessive memory usage and crashes.  

Vue will not be able to successfully bind all of these older and newer technologies into the software, and therefore some are going to suffer.  There are too many different computer builds and drivers to make it all work flawlessly.  I am not making excuses for Vue, I have my problems also. 

No one is seeing the problem or wants to see it..... The beta build before the last beta build worked great for me and others.  The last beta build had bad resourse problems and lot of user wwnt back to the previous version that worked fine.    E-on tech said they would go back to that versions resourse coding so we would have it in Vue 6 Final.   We dont see that as has happened because its still a big problem for some of us.
  Why is it some builds work fine for all and some as now have problems.   I am not blasting e-on or anyone but just using facts and talk about it. :) 

@keenart: You're missing the point completely, the pre-release worked fine on my crappy system as you seem to think it is so answer me this, why have I got such a reduced performance in the final version from the pre-release?  Just answer it, you can't, because it shouldn't!!
As for a P4 HT only barely meeting the system requirements, quote form e-on:

• Windows 2000/XP/XP64/Vista,
• 2GHz Pentium III or better processor,
• 1GB of free RAM (2GB recommended),
• 200 MB of free Hard Disk space,
• 1024x768 in 65K colors/16 bits (24+ bits recommended). 

Oh! a Pentium 3!!  
Please if you're going to add something to the thread, make sure it's a proper informed addition not a load of codswallop!!

@DaleB: Yes I did uninstall pre-release first just as they said on the mail, [wish I hadn't now!] I've been around computers a long time, since tape drives and ZX spectrums and before so I do know what I'm doing.

Sorry, but this is so frustrating, I had a pre-release that worked great, no problems at all, now I've got a pile of crap, what changed?
Nothing at my end so it must be a problem their end, period!!

Here is the thing & a good point to show mem purge NOT working.

1. Load terrain - texture it(256x256 non procedural no displacement or bump) resources at 92%

2. move terrain - res. drop to 89%

3. add a water plane - res. stay the same

4. Add a poser item - rescources plummet to 64% Vue come to almost a halt not being able to move/rotate/scale etc etc efficiently

5. Delete the poser item & then purge memory - res. only recover to 66%

#5 being the most important clue here I should have recovered back to 89% the original scene minus the Poser item - but no. It did do this in Pre-Release 2nd to last patch.

I have undo's set to 1/background draw off/Stop keeping history at 70%.

dlk30341: If you'd actually managed to rotate or move that Poser item you would have seen your resource drop even further, mines gone really low and I'm sorry to bang this same drum but it never did on pre-release, simple test for all of you, re-do a scene in final that you did in pre-release and see the difference in performance, hell I  loaded one before and got a resource message just by loading a previously saved scene, WTF is that about????
I had to purge the memory straight away after loading or I'd have got another crash!

**I never had these problems with pre-release and neither did others on this board, why is that so hard to understand!!

**

I have been waiting to see what others would say of the final release before downloading it. Now after seeing all the problems I will definetly will wait before I download and install the Vue 6 Final Release. I don't need the hassle of all these problems when I use Vue for my business. I believe E-ON will fix these problems and releases another build. I am currently using build # 288741 and it is quite stable but I will not be downloading another version until I now it is working properly. I hope E-ON focuses on fixing Vue 6 Infinite before working further on Vue 6 or Vue 6 Easel etc. I believe E-ON is doing there best to fix the problems. After all it's in E-ON'S best interest to keep their customers happy. If they don't get these problem's fixed in a timely matter, then they could potentially lose a lot of customers. I use Vue 6 Infinite for my business and I need software that works!

**LMcLean the version you are using 288741 was the best build so far that e-on has given us.
  The next version is full of resourse problems which that version you are using does not have.
Same with Vue 6 final for me its like the last beta update that has resourse problems.

Stay where you at and you will be hapy till they get a fix for us.  I am hoping it will be fixed before to long.   I will be very happy if they solve that problem. :)
**

Yes, agree with Iloco, that build [288741] was easily the best build by a long way, the one after that was the first one to have these resource issues that are now showing in the final release!

I created a small scene using Spectral GR for my atmosphere. I worked all morning manipulating the lights. etc. and did not have a crash. I closed it and worked some more and did have one crash, but I am not experiencing the same problems as the others. My resources did not falI lower than 92% when I did check them. I am using XP Pro. So far it is workig as well as the pre-release without the last update. I just installed it this morning so I need to work on it some more. I am not using anything from other programs except billboards from Xfrog.

That's prolly why Paula - you aren't using anything from other programs!  Most of us frequently use outside resources.

I caved & installed it last night & the resources where a nightmare to say the least.  I've never dropped below 75-80% in any prior version(that is with last patches applied)and that was with scenes packed out.  Now I can easily plummet below 60(with only a handful of items) - lowest I saw last night was around 27% & I crashed.  Purging mem did barely anything if anything at all at times.

On the upside - renders are faster when using displacement & SSS & transluceny has now been added for alpha leaves.

Okay, I am not trying to take sides or pixx anyone off, but I do understand the problem very well. I used to be a programmer in days past. Vue does not have a desire to put itself into bankruptcy!  

It takes months to write new code and test, not days. AND, it won’t happen unless you help them solve your problems.

I hear what John was saying about the problem with the OS, swap files, virtualization and so on, and how these changes are not working writing code for Vue and as a result they are trying to work out a different scenario. You can blame that on VUE if you want to, but it goes back to the OS. XPspI, XPsp2, and Vista, Poser are all different coded software and make other software companies change to meet the demands. 

The biggest mistake that e-On made was trying to release before Vista, now they are caught between a rock and hard place trying to clean up all of that code and make it work within and for all of the other software packages. 

A 3 gig Pentium does not have anything to do with it. It is how the software is used to access that CPU that make the biggest difference. HT is old technology now and some progrs no longer fully support HT. I had several progs that told me I have to shut off HT for the software to work correctly, and I got rid of them.

I had a really nice AMD setup, and VUE simply would not work, crashed all of the time, and nothing I did, changed drivers, adding patches, or otherwise would stop the crashing. I just installed that same VUE on an Intel with Vista and it works like a dream, no crashing, and now I can have my 5 millions polygons and move freely around my scenes.  But, if I import a Poser figure, the problems begin again. Why is that Vue’s fault, what the Hexx is in Poser that is making Vue crash???

I understand your frustration, but do you understand the frustration of VUE. Help them solve your problems, because I want Vue to stay around for a long time!

Soooooooooooooooooo.  Now we all got to get a new system with vista before we get any satisfaction from Vue.
  E-on better change specs and in a hurry.   I dont have the money right now and not going to build a new system just to run vista and Vue.
This is a bunch of bull if it holds water.     Suck us into buying and changing horses in middle the stram don't play well with me. :(

If what you say is true they have tricked a big majority of us in to this by getting our money first and then altering plans that effect a lot of us who have supported vue for a long time.    Hmmmmmmmmm starting to add up now but next go round if this is true my money want be supporting anymore.      

Quote " But, if I import a Poser figure, the problems begin again. Why is that Vue’s fault, what the Hexx is in Poser that is making Vue crash???

Because it didn't happen in Pre-release(build 288741) - that's why.

What is the build number of the final release?  I'm not sure I have the latest one.

Yes, it may have worked in build X, and now not in the new build Y. Vue probably made last minute changes to the software, for whatever reason, or for those OS’s and are now facing another compatibility issue. 

So, now they need time to resolve those issues, with your help. Poser is having its own troubles, and I would not be suprised if they will try to bvecome a competitive force against Vue.

Wow!  Maybe I could just put a few snippets of code into my software and wreck hovac with my competitor, just like some of the big companies do.

Basic programming; you all have a dark side!!!  Chuckle!!! 

289768

Vue & Poser are not competitors :blink: - One does landscaping/one does people.  EON & EF have a good working relationship & always have, so I dont think your theory holds water. I'm not into conspiracy theories - so won't feed that one.

**keenart, what gets me is tech support said they were going back to the good build and use that code for us in the final.
 You can read it in my tech ticket I have given I think in this thread.  Now who we going to beleive when someone says something and it don't work as they said it should.
  Its very annoying and agravating to not see the changes we were use to in one build of the prerelease where it was working so well for us.   I guess the higher end vista users need it more than us paultry low end hobbiest.  :(
**

Precisely my point, Why is Vue trying to put out bad software? It won’t get better unless you help the techs to solve your problems.  And Poser is becoming a competitor, wait and watch.

I am trying my best but a lot think its whining when I quit whing some odd 45 years ago.  At 62 I feel I have passed that stage in my life.

   I see your point and hope it does work out for all of us. Not just a few but all who spent money for the software.:)

*"Poser is having its own troubles, and I would not be suprised if they will try to bvecome a competitive force against Vue."

*Can someone tell me how that conclusion has come about? Here, all this time, I was under the impression that e-Frontier, who owns Poser, had invested their own money into Vue for the compatibility of both apps.  Has this been another fable?

I am your age as well, and I like to whine also, it makes me feel as though I am getting something done!!

As far as Vista goes, I do not believe Vue has any choice in the matter. If they do not make their software compatible with Win XP and Vista, which are all together different OS’s, they will not be able to stay competitive and will loose market shares as a result. I do not think they can afford to ignore the potential market, as they have to pay all of those programmers.

Vista is totally different than Win XP, SuperFetch, ReadyBoost, and other technologies are almost always active in the background changing app positions, change cache requirements, and many other new activities that all of the third party software companies are going to have to deal with. And, 3D software is the hardest hit of many of those apps. I believe this is what John was talking about, which you can blame on MS. They have their work cutout for them, because you change one snippet of code to make compatible with XP and then Vista trips, and visa versa. 

Get this: an e-mail from tech support; Adobe just informed me they would not update PSCS2 to make it compatible with Vista. They stated, since they have released the beta for CS3 I will have to upgrade to get Vista compatibility.   

I am going to go take a nap!!!

I just created four basic models  2 from Poser 6 and 2 from Poser 7. One from each has strand based hair and the other transmapped. The models are nudes. 

My OS is XP Pro. I have 4 gig of Ram on an amd 64. The memory usage was bad. Here are some of the figures. I started out with 90%. 

Jessi tr hair 76% purge 78%  deleted her - no change
Sidney tr hair 61% purge 68% flushed history 67% 

The strand based hair was a total wipe out. While it imported, it was so slow, I gave up and the resources droped to 42% for jessi and 38% for Sidney.

Each time I started fresh at 90%.

It seems to me it would been eaiser  and maybe should still be done to cater to the older xp/2000 people with a version and have one for the higher end people.
 Siince you are a programmer would this be possible........

THANK YOU PAULA and yes I am shoutoing so you can hear me.   This is what we been trying to show some people all the time.  Vue 6 Final will not handle lots of meshes as older version did.
  If I were to load what I use to do with Vue 4.5 Pro it would choke it and crash on loading a scene.

Thanks for the 6 replys so everyone be sure and not miss your comments...................lol

Ok guys - John from EON HAS comfirmed a leak with PZ3's & said it was fixed today.  Still working on where the other leak is coming from, so the more that report the faster they will nail it down!

I want to add here - that I was having the same problems when using .vob format & .obj & 3ds so this is NOT just limited to PZ3.s

Paula - I hope you reported to tech support :)

Wow! I'm impressed you did that test 6 times Paula! 

Are you sure dlk30341 ? There are those that insist that it is us and our systems that are the problem and that there is no mem leaks. Oh, and still looking for the other one?

dlk30341: "Fixed today"  Does that mean there is an update patch yet or not???
I have a message form tech support in my inbox but I can't access it here at work so I'll have to wait until I get home to see what the reply is!
Nice to know that they've admitted to a problem though, glad to know some of us weren't going daft after all 

LOL, X-post Beryld

Quote " We have identified and fixed potential memory leaks regarding Poser import today, but if the problem is not specific to Poser, another problem might still be there. We double checked the code for free resources evaluation, and it is indeed working like in Vue 5 and early Vue 6 builds, so the problem is not related. This is therefore probably some memory leak regarding undo/redo history or something like that."

End quote :D  see for full discussion - must go towards the ends as thats where the new acitivity is.

http://www.e-onsoftware.com/support/ShowMessage.php?id=1169983945

ROFL at beryld :lol:

Roflmao at **beryld.    Good one.  My system is the same as when it was working good with a beta prerelease. :)
**

I was surprised I did the test so many times. I hit the button ONCE. Sorry about that. Even I don't want to lok at my own messages so often.

I did a test with poser on my Vista Ultimate 32 bit machine. The specs are similar to my XP pro Machine. 4 gig of memeory and an AMD 64. I have unchecked in the import any reference to poser so I am  not using the Poser shader tree, etc. Again, when I open Vue memory is 90%. There is one major difference between Vista and XP Pro (32-bit) both with Sidney and jessy Strand based hair imports in the same amount of time as does transmapped hair. I did not test the quality. The specs were as follows.

Jessi with transmapped hair (tr) 80% purged memory 83% 
                                                            deleted mem dropped to 81%
                                                            purged and flushed returned to 84%

Jessi with strand based hair started at 47%. I closed the file and reopened it. Memory showed 50%

Sidney with transmpapped hair 66% purged memory 67% 
                                                            deleted mem dropped to 69%
                                                            purged and flushed returned to 79%

Sidney with strand based hair started at 42%. I didn't go any further.

I will send both of these to tech support.

Actually they do that, by using different DLL’s, API’s, etc. for different OS’s. Some work for XP and others work for Vista, some for 32 bit and others for 64 bit. So, you might say they are writing four different programs to meet the needs of all users. The major problem is that each OS build is different and has different requirements.  So once Vue gets all of the code set to work with OS build X, and along comes build Y, everything can change. 

To add, the reason I put so much emphasis on tech support is fundamental. If one person has a problem and reports it to Vue Tech, and 200 other people see that problem was reported by reading the posts in the forum, and do not make a report to Vue Tech, they have just defeated the idea of tech support. 

It is like this, if as the Software Design Engineer, I get one complaint about a glitch, and there are actually 200 out there that I do not know about, then this one report gets last priority, while I am fixing other bigger problems. I wish everyone would understand how important this report system really is. The more complaints about a problem, the sooner the programmers will focus their attention on the problem.

I have to tell you VUE have missed their expected release date, and that is costing them major retail bucks every day they cannot afford to lose.  

Thank you for the good news dlk30341, so it was not me or my machine.
Thank you Paula Sanders for the test, my v6i behaves the same way.
As e-on acknowledged, final version was handling memory like v5i did.
I also appreciate thefixer for starting this thread, iloco and all others for pointing this problem out loud.

Believe me, I get no pleasure at all from starting threads like these, I would much rather have software that does what it says on the tin!

I have thoroughly enjoyed using Vue6Inf, at least the pre-release version and I hope in the very near future to be doing so again but as it is now it is virtually unusable for me I'm afraid!

Your welcome LAM2 - no it wasn't ANYONES machine as we can clearly see :)  Most people hear have medium to high end machines.  It is the rare occasion and I do mean rare(maybe once a year) I see this kind of thread when a person announces oh but I only have 768mb of ram - then I could understand crashing.

thefixer, I understand what you are saying. We all love to be able to work with v6i, and we already know how great it could be from the pre-release experience.
Let's hope that e-on give us stable v6i asap.

A pic attached when showing the work scene and another of final render. :)  I find this very Interesting .

I think most everyone is aware of this, but maybe some newbies have not heard:
The Vue 6i minimum memory requirement is not 1GB memory.
It's "1GB of free memory". That is, 1GB left free after your operating system plus everything else that loads at operating system startup (don't know how that works on a Mac). Some people have a lot of programs and utilities constantly running and using memory, many of which load themselves automatically when they start their systems.

Again, something about different people's systems that can cause Vue faults for some people and not for others.

Now, before i get labeled as an e-on apologist, i am not saying that the particular problems reported here are because of this - i doubt they are - but if you have 1GB total memory, it's something you should be aware of, because one can certainly have more than one problem and from more than one cause.

JC - I am not accusing you of being an e-on apologist. I was not having any trouble with the final release and couldn not imagine where all the problems were coming from until I decided to run tests with Poser. As far as other problems, I have not experienced any, but look at my Poser tests. The memory problem is bad. I have 4 gigs on both my XP pro (32-bit) machine and my Vista Ultimate machine. On importation of any figure memory drops and will not come back subsrtantially. It varies with each figure. These figures are as plain as possible.

I believe in reference to importing objects  we are speaking about problems that are not related to specific systems and if we keep discussing systems, we will just muddy the issue. Other problems might be system related.

I am very well aware of that jc.    I think the pics pretty well speak for them selves.
   I agree with you on more memory is best but some with lots memory are having issues as well.  :)   I think we all want Vue 6 to work as Vue 5 and before did but when one release worked great and then a new one comes out and don't then how can it be a hardware problem. :)  Thats the issue. :)