Anyone tried to adjust volumetric lighting in the final release?
I try a simple scene with a building from Poser 6, GR atmo that's it just to try it! Hit the adjust Volumetric lighting switch and POOF! crashes!

I wish I'd stayed with the pre-release version, at least that worked!!

Yes, I've raised a ticket!

What with Poser 7 not being right and now this not working right, there's not much hope of doing anything constructive is there!

Injustice will be avenged.
Cofiwch Dryweryn.

Are you PC or MAC?  I am PC... You could not PAY me to even try the GR....as said in other post can't even get decent time with spectral clouds.

Never got P7 - THEY RE WROTE the program on that too...not worth the head ache unless you animate (I don't)... P6 talks fine to vue 6....

Life Requires Assembly and we all know how THAT goes!

Hi Lyne, I'm on  a decent spec PC and yes I'm using P6 with Vue6 but this was from a P6 import and it wasn't big!
Crap innit!!

Injustice will be avenged.
Cofiwch Dryweryn.

Resourse problem are still in Vue 6 Inf Final.
  Not no where near as good as the prerelease build before the last one that gave so much problems.
 I agree fixer if I keep getting crashes and errors due to low resourses I am going to install back my prerelease and use the update that handled resourses better than the Final version. :(

ïÏøçö

I really don't understand why they release the final version with so many issues, what do the testers do?!! I have Vue 6 Esprit, should I install the final version when it's released in March?
I've been working with computers for a few years now & I get the impression that whether it's a physical or software problem, we somehow have to accept the fact there's going to be a problem, yet if you purchase anything else in life it is not acceptable. I understand there are so many configurations etc but it does drive you mad!

What pisses me off stormchaser is that they were told that the new update for the pre-release which had a different way of handling memory was causing problems, not just by me but my most peeps here at the very least, yet it looks like they did the same thing with the final release.
And you're right, it's not acceptable and why should it, the pre-release was actually a better bit of kit than the final, how can that be right!!!

Injustice will be avenged.
Cofiwch Dryweryn.

Personaly and this is just my thoughts is that e-on is listening to to many people other than the ones who spend the cold hard earned cash for the products.  Take it as you will but just my personal opinion.
 I f I were the Head of e-on id be looking into what has gone wrong with them since about Vue Pro 4.5. and start listening to its customers who are the ones who keep it afloat.   Something bad is wrong.
 Public Relations they don't know what the word means. :)

I can remember during the vue 4 period they had people who worked for e-on on this forum who were answering questions for people who asked.  Things have rally changed since then. :(

And yes it does bother me because I like the program and the use of it but not when it dont work and no feedback from anyone at e-on.    All their feedback is through 3rd party individuals.  What are they afraid of so as not to let us know what is going on.

I have to say I have had good communication with tech support so they are doing their job but i sometimes wonder if they are listening. :)

ïÏøçö

Can't re-create your problem on my system.  My systems stays pretty much on 84% resources avaialable with simple scenes.  Drops down to about 54% with the latest picture I'm working on, but this one has a ton of Dystopia buildings and Poser imports plus lots and lots of lights.  Rock stable so far.  All of the bugs that were bugging me before seem to be fixed.  

Anyone notice all the new textures and atmospheres we got?  I'm a happy camper.  The only thing I'm doing now is getting everything moved over from Vue 5 so I can un-install it.  

Now, at work I installed Vue 6 without having Vue 5 installed on that system.  It did give me some hassles with checking for a valid Vue 5 liciense.  I just gave up and said no.  MAYBE, that is causing a problem?  Did not really have any time to play with it a work - I only install it there to test it on a "crappy" system.  I don't really use it for work (more like play around during lunch).  Anyway, at home I did not run into that problem and Vue installed all happy.  If you continue to have problems, it may be worth the time to install Vue 5 Infinite, un-install Vue 6, then re-install Vue 6... 

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html

If it gives you a hassle use the vue 5 install cd and the hassle will stop. You don't have to install vue 5, you just have to put the cd in the cd player when the pop-up shows up.

thefixer,

 I am having huge crashing problems, with lights and with the plant library!  I can't open that atall without Vue crashing.   With the lights, its just radials but when I try and edit them, the scene crashes!    I have a powerful pc with 4gigs of memory and WinXP64.
I agree this is much less stable on my pc than the prelease one fix back was. Very frustrating!

This final release is slower than the pre release and I get the memory warning all the time and didn't with the pre release.

There is something wrong. If only one or two people are having problems then I would say that  it is user specifics. But when it is the other way as it seems to be, that is software.

I never had a crash with the pre release, I've had many with this final version.

I agree, that the final release have poor memory handling problem, which I didn't see in pre release version without the last update.
I got low memory warning for the first time since I started to use v6i, and this is suppose to be the final? I hope they don't mean "dead" by calling it "final".
Over all feel is buggy and noticeably slow.  It's disappointing to say the least at this moment.
I'm also thinking of going back to pre release without the last update. It was far more stable than this final version.

I did get it to crash with adjusting the light settings - but only after it was adjusted once, then go back and adjust it a second time.  This is a confirmed bug that e-on is aware of.  Hope the patch will come soon, this puts me at a stop for the picture I was working on.

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html

Peggy, I have had that too.   If you adjust the light then save, then reload then ajust again ect you can keep it working! Tedious, I know, I did it eight times in the pic I am working on for eight lights!!

cheers, Susan

Yea but what is really bugging me is that they've screwed this up so badly between the pre-release and this final one, I hardly had a problem at all with the pre-release especially with lights and now I have, WHY??
A simple scene takes my resource down to 52%, I can get it back up to about 72% by purging the memory but I have to do that virtually each time I move or add something, I never had to do that in pre-release, it Sucks big time!

Injustice will be avenged.
Cofiwch Dryweryn.

thefixer that is exactlsy what I and a few others reportred to tech support and they said they would go back to that prerelease version in the final but it looks like they forgot they told us that and released it anyway.
  Its a mess for sure. :)

I am having same problems again with resourses of which I didnt have with the version before the last one for prerelease.   Some one was passing along wrong information because its not fixed. :)

ïÏøçö

Well I really hope everyone here that is having this issue has bombarded them with reports, I know I have!!
It's a pity they don't bother to come to forums like here and actually see what peeps are saying, I mean how hard would it be for them to check out forum posts at the major sites like here and C3D for instance!!

Injustice will be avenged.
Cofiwch Dryweryn.

**This is really not on! I have 1GB of memory (I know I need at least 2) so upgrading to the final release of Esprit is scaring me. If I have these problems you people talk of I've got no chance. At the moment my program is manageable.

thefixer - Never has your sig been more appropriate!!
**

LOL, yea absolutely, I have 2 Gig on my system so really shouldn't be having resource issues!!

Injustice will be avenged.
Cofiwch Dryweryn.

It is so bad it actually crossed my mind that maybe someone sabotaged it, and I am only half joking!!

Have had one problem only here, with the final release. The crash when changing sunlight setting several times - like if i set the shadow intensity level 4-5 times in a row. No other crashes, no low resources, never a memory warning (have 2GB) on a P4 Intel motherboard. Have spent many hours working on scenes with never a problem.

And i'm using all the high-speed OGL (OpenGL) render and GUI settings, fast redraw and such.

Imported a few Poser figures (made in Poser 6), but not staying connected to Poser - and manipulated them easily, no problems there.

I had been getting a few OGL related crashes with my Intel onboard graphics chipset on all the pre-release builds - so i finally got around to buying a GeForce 7950 display card and all crashes (except that one mentioned above) immediately stopped.  

I'm happy and productive with the final release.

JC what are your sys specs?

Also do have the Jungle Queen made by Daz? If so load it & please tell me what happens on your end.

I know a few are going to say its the best build thats ever been put out but read what problems a lot of people are haivng and I dont think they are streching it at all.
 All I can say for those that it is working great for is I envy you and wish I could say the same. :)

Resourseces for me is as I have said and you are welcome to visit me or I can send screen grabs as I have done to tech support. :)

When one prerelease version works good with resourses and then the final dont then there is a problem and I dont want it blamed on my machine when I know what it will do. :)

ïÏøçö

Ok, my own experience confirms what you guys are seeing - the final release is less stable than the last pre-release. Had the program crash from just moving Poser figures around the scene and general memory issues - flushing the memory doesn't seem to work as well as previous builds.

I fall for this every time - when will E-on learn....when will I learn!!!

Agreed Stormchaser - all I can surmise is that E-on's beta testing program and how E-on go about issues that arise is flawed. I don't know about their process, but the results aren't consistent! There must have been plenty of bug reports during the pre-release, and E-on have shown that they have fixed many, but others come up. From my experience with beta testing all I can think is that we have a program that needs a re-write...then I think about the mac version that is only two versions old and the problems some of the guys have with that.

I think that when they fix a bug it just breaks something else, which = complex or bad code...or both!

 

Website: The 3D Scene - Returning Soon!

Twitter: Follow @the3dscene

YouTube Channel

--------------- A life?! Cool!! Where do I download one of those?---------------

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

Guys and Gals who can see the tech support tickets I have filed another to the first I report when it was in prerelease.  Feel free to add to if if you will.  the more the better chance of getting it fixed. Attached is link for registered users to see. :)

As you can see in my tech ticket they said it would be fixed in final but its not.  Something is wrong somewhere. :(

ïÏøçö

Is it the majority having problems and the few working okay? Or the reverse?
I don't see hundreds of complaints, although there are thousands of users. It's normal for those not having problems to not post.

Would be great if no one had problems and i do feel for those of you who do have bad ones - i've been there too - in fact, as a PC Consultant (and web developer/marketer) i deal with PC problems constantly.

Anyway, my system specs:
I assembled it 2 years ago from:
Intel D915GAG motherboard
Intel P-4 3.0 GHz
2GB Ram
BFG GeForce 7950 GT OC display card with 256MB video RAM
2 - 120GB Seagate SATA drives 
SoundBlaster X-Fi audio card
300 Watt power supply
3 Extra fans
Windows XP Pro, SP-2

I maintain it with:
PCTools Registry Mechanic
Trend Micro PC-Cillin anti-virus
Diskeeper
PCTools Spyware Doctor
Norton Save & Restor backups

Custom settings:
Windows cache (hard drive virtual memory), display 3D settings

When tech supoport confirms its a problem then what more can we ask for.
 As you say if its just a few of us don't we have the samee rights as you and those others who say it works great for them. 
As a few have said something not right somewhere. :(

I know most will blame it on our systems but this doesnt hold water with me period.  Not when a prerelease didnt give the problems we few are now having.

ïÏøçö

Where did i say Vue 6i had no problems?
Where did i say that those who have problems should blame them on their systems?
Someone asked for my system specs and i reported them.

However, SOME people obviously WILL have problems related to their systems. System issues certainly will not account for all problems. For example, i had Vue 6i crashes caused by my Intel graphics chipset. When i switched to a new GeForce card, those problems were resolved. And Vue 6i warned me that my display chipset was not on the approved list when i installed the program.  

System specs aside, the fact remains that on my system that runs 5I like a charm and to a lesser extent so the VUE6I pre-release, FINAL is a disaster as I have stated in another thread here  
http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2686639. 

So tossing barbs back and forth here is useless and pointless. The fact remains that there is something drastically wrong here, and for the life of me, I can't see how it could be system related.

I agree tossing barbs is useless steve.  I only complain with a valid reason the same as you.
 If my application was working as it should I would be playing with it and not posting in hope of it being fixed. :)
 Posting is a waste of time for me when I would rather be playing in a Vue version that works. 
 I do enjoy working with it when it works as it should but is a night mare when it isnt. with its errors and crashes when its low on resourses :)   If we all ahve to get a new system with 8-10 gigs of ram then e-on needs to change its specs on what it takes for Vue to work as they are misleading.

I still have vue 5 installed and I have no problems with it as I do with the final release of Vue 6.
 I also got the good prerelease installed on my laptop and it works much better than the final release for me. :)

ïÏøçö

ilico,
 I dont believe it is anything to do with ram.  I have 4gig, Core2Duo Intel, winXP64. NVidia Geforce graphics card, and the scene I am making is not very complicated.  it was crashing all the time.   I am now rendering it in Vue 6 prerelease, and I am having no problems at all.

That says a lot doesnt it.....:)

ïÏøçö

Just stopped in to see what's been solved...<<  LOL

...but I am definitely with you, Traligill...unfortunately (or maybe not) I can't locate my working 6I update...having uninstalled the pre-release to get the Final...so I'm still in 5I and tooling along quite well... '-)...

Steve

I had another "non helpful" response this morning from tech support: "Does this happen with just this scene, yada, yada" so below is my response!

Quote!  I didn't get a chance to save it but it was very simple scene so I will try to reproduce it, I have to say though and this isn't a personal attack so please don't take it that way but, your PR people need to visit some of the top forums like Renderosity and see the amount of problems this "final release" has caused, the pre-release was much more stable and it's not just me saying that, it's pretty much everyone that's using it, your people need to start listening to their customers.

You changed how this release handles memory management didn't you and that is what is causing the problems, you did the same thing with the final update of the pre-release which is why everyone rolled theirs back to the previous, you need to get rid of that new memory management, it sucks!

Injustice will be avenged.
Cofiwch Dryweryn.

Just done a scene with one building prop and 2 terrains with eco-systems, resource dropped to 19% which it never did with pre-release with bigger scenes. I got it back up to 70% by purging but really with 2 Gig RAM I shouldn't have to!!

Injustice will be avenged.
Cofiwch Dryweryn.

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

This is exactly how it happened with the final prerelease final.   this tells me they did not fix as they said they would even after confirming there was a resourse problem.

From techs own reply back to me. QUOTE: Hi William,

As the whole on-disk data swapping strategy is based on this remaining memory evaluation, we suspect that Vue swaps data onto disk way too often now.

We have therefore decided to revert back to the old behaviour, to ensure a better memory handling. This should fix this huge performance difference you have noticed.

Best regards.
John Canver

Attached is the tech ticket so you can read with your own eyes.   Why say one thing and do another and not fix the problem is beyond my way of thinking. :(
  It gets very disgusting when someone tells you something and then don't do it.

ïÏøçö

Eh!!

Injustice will be avenged.
Cofiwch Dryweryn.

Opp's. I was reading the thread and hit the reply button by mistake. Still working on my first coffee. LOL

beryld - Are there any resource problems with the coffee? If so, just send e-on a ticket, they're bound to sort it out like they did with the Vue final release!

No. Unlike the e-on brainfart, I keep my resources stocked and I don't replace the good coffee with the new improved instant coffee.

I was hoping for good news, looks like I will have to go back to the second to last pre release until e-on gets thier act together. That version worked fine for me.

I posted an image tonight that I did with the "final release" and it was a bummer to do! I had to make an adjustment, purge memory, rotate, purge memory, move, purge memory, etc. etc. 
I had to do it like this because my resource kept dropping under 15% on 2 Gig RAM and xp managed VM.
Took ages to make the bloody image and then a 4 hour render, wasn't happy with the end result but hey after that much time and effort on it I had to post it [LOL]!!!

Injustice will be avenged.
Cofiwch Dryweryn.

I'm not at all pleased that my dissatisfaction with Vue 6 appears to be a widespread feeling.

I've been a Vue user since Vue 4, going on through Vue 5 Infinite, and finally to Vue 6 xStream (Hoping futilely to take advantage of not only Vue 6's admittedly attractive features, but also Vue 6 xStream's ...er... as they term it..."integration" with Cinema 4D - which in fact seems to be only by the broadest possible interpretation  functional for much of anything useful.)

Unlike many, I had few enough complaints about Vue 5 Infinite - the usual bugs I put up with, and being relatively inexperienced with other complete package 3D applications, I sort of assumed that they were simply par for the course when dealing with the largely hidden technical complexities of 3D work. This is hardly the case, I've discovered, after purchasing Cinema 4D v10 Studio - itself considered "buggy" by long time C4D users, a program which I've only managed to crash when doing things which are inconceivably stupid. Maybe some day I'll stumble across these oft complained about bugs in C4D. That I haven't found these notorious bugs in C4D says a great deal about Vue 6, which as often as not, for me, at least, and others, apparently,  terminates itself with a lockup or crash.

So, at this point, from time to time I check e-on's site for Vue 6 xStream updates and try to keep it current - which is largely the limit of my interaction with the program. It pretty much occupies space on my hard drive as its main function.

Purchasing Vue 6 xStream may not be the most worst mistake I've ever made, but it is certainly the mistake that is most unquestionably a total mistake I've ever made.

That I've jumped ship from Vue to C4D certainly does not mean that I'm trying to convince others to do so. Not at all. C4D, for a program touted as "professional," and "high end," entirely lacks anything resembling Vue's very cool and versatile ecosystem feature, and its only DOF option is an entirely unacceptable post-render depth map based DOF, much like  Vue's quick and cheap depth map DOF option, but without the admittedly slow, but lovely and subtle ray traced DOF which is an option in Vue. Compared to Vue, Cinema 4D is pricey. The most basic version, sadly lacking many of the features which make for a complete 3D program is more expensive than anything in the Vue Infinite series. Cinema 4D Studio, while not as costly as Maya or Max, is very, very  expensive indeed.  But no more so than a good HD TV system, and since I can find no good reason to spend large money on &%$#@ TVs, I can justify its purchase to myself, at least.

I'll most likely return to my installation of Vue 6 when the desire to create a landscape strikes me. This may be a while, however, as I seldom do them. If there is something for which I absolutely require an ecosystem, thousands of little rocks or something, I guess I have little choice. The spectral skies and cloud systems are certainly impressive, and I'll keep that in mind when I need spectral skies or impressive clouds. But for everyday use, nah. E-on's lost me. Perhaps someday they'll understand that cool features don't really make up for a frustratingly unstable application.

"La meta es el olvido. Yo he llegado antes."
Jorge Luis Borges,Un Poeta Menor,Oro De Los Tigres

I must add to this because what I'm hearing others say is VERY disturbing to me. First of all, I do not own Vue 6 Infinite yet but I was about to order it today in fact, until I noticed this thread and started to read all the postings. I want to briefly explain my own history with Vue. I start using Vue 4 a number of years ago and was THRILLED by it! It was such a welcome relief from Bryce which to me, was not nearly as intuitive and easy to learn as Vue 4, plus it had a lot of cool features and in general was a much better program, I thought. Then, I made the leap to purchase Vue 5 Infinite last May and was TOTALLY disappointed!! Even with all the patches the program never performed for me nearly was well as Vue 4 did and so I stopped using it. Well now I'm in a real dilemma about what to do with Vue 6. On the surface, it seems like a great program and the Pre-Release got a really good write up in 3D World, Issue 87, but as many of you have already pointed out the Final Version does not seem nearly as good. I for one do not want to go back through what I already experienced with Vue 5. Please feel free to comment on this post if you wish. Thanks!!!

Except for a bug when editing light settings (e-on has said it will be fixed), I have not had any of the above mentioned problems with the final release.  My system resources are staying stable and things are working very well.  The only time I see a slow down is with one file that uses a volumetric atmosphere.  That scene gets painfully slow to move things around.  Change the atmosphere and it goes back to normal speed...  Don't know if that is a bug or not, but so far I am happy with the final release.  

I'm not sure it a widespread dissatisfaction, those who are happy with Vue are not as likely to post as those who are unhappy...

LVS - Where Learning is Fun!  
http://www.lvsonline.com/index.html

Are people also having problems with the way poser conforming (transmapped) hair is being rendered in Vue 6? It seems to be really screwed when compared to previous builds.

Cheers

 

Website: The 3D Scene - Returning Soon!

Twitter: Follow @the3dscene

YouTube Channel

--------------- A life?! Cool!! Where do I download one of those?---------------

Peggy what is the specs on your computer if you dont mind saying. :)

ïÏøçö

*"I'm not sure it a widespread dissatisfaction, those who are happy with Vue are not as likely to post as those who are unhappy..."

*And maybe there are more that are having problems and are afraid to post. Say something bad and your a monster.

So far, I'm finding the final release to be far better than the pre-releases. That's not to say I haven't found a bug or two (maybe 3). I should mention that I haven't played much with Poser imports yet (maybe tomorrow). My major problems have been with lack of support for my graphics card, NVidia Quadro FX3400, but even that is a little better with the new release (I can finally use that gizmo thing, and do some limited panning).

Still not happy, but I sure am glad I'm not crashing every 2 minutes.

Exactly Beryld.

DigReel I understand you and I dont think a lot of people are using models and meshes and materials some are that are haivng resourse problems.
  Its hard to be behind each and every computer and do the same on it you do yours.
The problem with resourses is what and how a person is suing the Vue application.   Sure simple easy to use default vue stuff will not give many problems.
  Hope this makes sense and others see some do have problems and some do not.  A lot is involved but when a person can compare releases and see a problem it has to be in vue the application.
  I am sure lot the problems is hardware related but when one uses different builds and one does better than another than its Vue related.     Don't you agree with me.........I know a lot want.

ïÏøçö

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... ;)

Life Requires Assembly and we all know how THAT goes!

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!!

Injustice will be avenged.
Cofiwch Dryweryn.

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. 

jankeen.com

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!!

Injustice will be avenged.
Cofiwch Dryweryn.

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!!

**

Injustice will be avenged.
Cofiwch Dryweryn.

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!

Injustice will be avenged.
Cofiwch Dryweryn.

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!

jankeen.com

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!!! 

jankeen.com

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.

jankeen.com

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!!!

jankeen.com

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! 

Injustice will be avenged.
Cofiwch Dryweryn.

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 

Injustice will be avenged.
Cofiwch Dryweryn.

LOL, X-post Beryld

Injustice will be avenged.
Cofiwch Dryweryn.

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.  

jankeen.com

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.

Let pics speak instead of me.  Attached is one model imported into Vue 6 Final from a saved pz3 rrom Poser 6.    It dropped to 39% on import. Now look and you will notice its only one model.  How can anyone add more and work. Anyway it crashed right after saving the final render . with an out memory message and the other one that I didnt get screen grab before it crashed.   Now I can load this same model into Vue 4.5 and Vue 5 and still load more stuff to work with. It is the rdna church for those who want to try it.  

ïÏøçö

The out memory error that is so famous before a crash.

ïÏøçö

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!

Injustice will be avenged.
Cofiwch Dryweryn.

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.

Ok people here is same model used in Vue 5 inf.  No problems at all with adding stuff and could added lots more.  this is what I am used to doing.  So no one can say it was the model.

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

ïÏøçö

rendered pic at final setting.

ïÏøçö

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. :)

ïÏøçö

For crikey!!!!! This is NOT a system issue. Please for for the love of............ re-read what EON tech support has said - will quote again:

" 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."

Sorry for the saracastic tone - but come on.........It's NOT the machines. 

So please - keep reporting to EON - even though they say they are aware & are fixing - the more that report the quicker they will pin point the last memory leak.

Thanks paula for well explained comment of what I have been seeing also that others dont see or understand. :) Or don't want to see and understand.

ïÏøçö

I posted the below in my "Totally confused..." thread, after having thought that things were really starting to look up due to some assistance I received from James (timefighter)...assistance that was much appreciated and does have a big impact on performance until any Posers are added...and just wanted to offer it up here as well to illustrate the severe memory leakage issues I am still experiencing...

Hmmmmmm? Still experiencing big time resource problems here. Just loaded in a recent file, "Rude Awakening" here in the Galleries, that I had done in the "working" second to last update of 6I. When working with it there, if I remember correctly my resources were somewhere in the neighborhood of 60-65%. Upon loading it into 6IF, the resources instantly go down to 11%. After letting it sit for a good 5 minutes, the resources will go back up to ~31%, but once I select anything (which in and of itself) is a 2-3 minute ordeal, they plummet right back down to 10-12% and it becomes quite painful to do anything with the scene.

Methinks this would be a good night to catch up on some reading '-)...

Steve 
off to find a good book, not CG related...LOL

Oh! Very sorry.

I didn't realize i wasn't allowed to mention that Vue can crash because of system problems - not that i ever said that was the cause of this particular problem.

Its best to stay on topic so everyone is not confused. :)

I showed it wasnt a system problem in my pics with comparison of Vue 5 and Vue 6. :)

ïÏøçö

Yesterday I mentioned that (aside from graphics) I wasn't haven't any real problems in the new release. Also mentioned that I hadn't tried Poser figures yet. Today I DID try Poser figures and it's worse than ever... even with 10 Gigs of ram under XP64, I can't get 2 pz3 files into one scene. I CAN load as many vob files I want, even into a scene already weighing 1.5 GB. I think this confirms what a couple folks have reported about pz3 leaks (leak? more like the Hoover Dam bursting).

Until e-on gets the memory bursts fixed, I'll keep using the age-old work-around of saving everything out as vob's... PIA, but at least I can build my scenes in the meantime. And what longtime Vuer isn't used to using work-arounds? For me, even with work-arounds, Vue6 is far more effecient for building heavy scenes... and yes, it does require 64bits to do what my clients want.

Mind you, I still want those leaks fixed! ;-)

Digreal - I my experience - I did report this to EON.  The offending Item I had was imported as a PZ3 - then .obj - then .vob - made no difference on my end - all had the same result :(.  But at least we know they are working on it & aware of the issue.

That's strange, dlk. I don't seem to have problems with vobs. Must have to do with the different coding for 32 & 64 bit. I do have everyone's favorite pre-release installed on my 32 bit machine. I'll have to see what happens there. Tomorrow, tho... right now I'd rather go watch a Voyager rerun. :-)

Same with me on vobs and pz3.  No difference. :)

ïÏøçö

SOunds like a good plan Digreal :)  Have a nice evening :) I don;t think it has anything to do with 32 vs 64 - has to do with Vue not purging mem properly, as tech stated - they are still looking :)  All we can do now is help them out to nail down the last bit of mem leakage :)

I just did some test with vobs and I too have problem with vobs.
After a few vobs and v6i become very slow.

Please repot it to tech support. :)

ïÏøçö

 I'm working on it right now...

Thanks the more that send reports the better chance of getting this issue fixed.   I hope all others who are reading this thread and with the view count as high as it is I am sure there are many will do the same if they have resourses problem. Or any other problem as well.

 I am really gald some came forward to help us prove our point and not all saying its not a problem as we now see it is a major problem.    Thanks everyone who has helped and is helping. :)

ïÏøçö

I don't see why some peeps can't get this simple fact into their heads:

Scene in Vue6Inf Pre-release ======  No issues with rotating, moving, resources etc.

Same scene in Vue6Inf Final-release ======= Issues with resources affecting moving, rotating etc.

Now why is that 2 lines so difficult to understand????

Nothing changed on my system between pre-release and final, nothing!!  Therefore, logical conclusion, something changed with the software, not bloody rocket science is it!! 

Injustice will be avenged.
Cofiwch Dryweryn.

I thought this other low memory issue might be of interest to some. This is a copy and paste of the message I sent to e-on's tech support. To me this shows the memory leak or whatever it is has a wider scope than just imports.  (For those who didn't read my former posts, I have 4 gigs of memory  on a system way beyond Vista requirements.)  Also the purge and history flush commands don't always work.

When I opened the file to render it had resources of 89%. The file was strictly Vue except for 5 alpha planes of trees. There were 12 objects and 1 light. The atmosphere was spectral. There were 5,305 polygons. I rendered at Ultra with Multipass enabled. I used 2400 x 1800 at 300 dpi.

I rendered this during the night. I saw it took a little over 6 hours. In the morning, I fortunately was able to save the images because immediately after, I got a low memory warning. The memory was at 22%.

I tried to both purge and flush the history and it did not make a difference. Those two commands obviously did not work.

I have been writing articles for Renderosity on Vista for the past few weeks and I tested extensively Vue 6 Infinite pre release not using the last update (I used the update before the last). I never had a problem. I did renders for over 24 hours. I did not check memory because there never seemed to be a need for it so it is hard to compare.

Thnaks paula for that information. It is exactly what problems I have had since the previous update to the final one for beta release. Vue 6 final has some bad resourse and meory issues.
 I am so glad this is confirmed as I seen it and hope e-on finds the problem and gets us back on the right track so we can use vue 6 with all its new features.   I hope it will load and render objects as vue 5 inf did.  I could really make some complex scenes with Vue 5 and not crash. :)

ïÏøçö

I just now received this from tech support at e-on. It is in reference to my posts about Poser import and memory loss:

"Hi Paula,

We have indeed just fixed memory handling issues regarding poser import (and also with opengl textures, especially for ecosystems, when background draw thread is disabled). Next upcoming update should eventually sort things out.

Best regards.
John Canver"

I got the same paula.   I hope we get an update pretty soon so we can make images instead of posting in forum and tech support to get our problems solved.

Here is what he told me.

QUOTE:   
Hi William,

Some fresh news: we found two memory leak problems:

• one specific to Poser imports.

• one related to OpenGL textures (especially for ecosystems) if background draw thread is disabled.

Both are now fixed. Next update will include the fixes, and we hope it will fix all the bad memory handling behaviours you currently observe. Thank you for your patience and help.

Best regards.
John Canver

ïÏøçö

I also got similar response from John Canver.
So, let's wait for the update.

Like the new avatar Iloco!!
That second reason worries me a bit because I never disabled the background draw!!!
I hope that doesn't mean there's a third one that they haven't found yet!!
Oo-er!!!

Injustice will be avenged.
Cofiwch Dryweryn.

Thanks thefixer,............  I think to myself thats how i am seen by others a lot times.  
 I agree I never disable background draw.  If its there and is suppose to work I want it to work.  If not remove it. :)

ïÏøçö

Not by me my friend!!

Injustice will be avenged.
Cofiwch Dryweryn.

You know what I mean.......................

ïÏøçö

Oooo, I go have a snooze and wake up to some good news. Maybe I should sleep more often.

I don't disable background draw too.

I'd like to try and get a better handle on what seems to be happening here. The impression I'm getting and please I'm disagreeing with anyone, is that ALOT of people are experiencing problems with the final version of Vue 6 Infinite. Ok, so if thats really the case can someone please direct me to where the bulk of these discussions are ? Because I visited the link supplied here to e-on's support center 
http://www.e-onsoftware.com/support/ShowMessage.php?id=1169983945
but it seems like a vast majority of the posts there seem to be coming mainly from only two people, namely William Hutton and Debby Kohlgraf. So what I'm wondering is if there are tons of other people having problems why aren't they coming forward as well ? I know I sure would be if I was one of them. Anyway, those are just my thoughts and again I'm really not trying to make anyone mad. Thanks!

Well I can say there have been lots others come out the wood work so to speak about the problems.
 If you look around you will see people like cheers, paula sanders, beryld, thefixer and more that have been talking about the memory issues.  And O yes e-on tech has confirmed wht we been talking about.    So if it were only one or two who do all the talking why did tech find the problem and confirm.    Remmeber it only takes one to talk about and report a problem and if e-0n tech confirms then I think it was worth talking about. :)

Do more clciking on threads and you will find more than me William Hutton and dlk30341 doing the talking.

WE have accomplised aot the last few days by getting the problems confirmed by other members and now tech has confirmed the memory and resourse issues.    There a few other problems I noticed today reported by monsoon that I hope will be fixed ASAP also.

 Hope tha helps answer your question..... We are all happy that a new patch is suppose to fix our problems we been discussing. :)

ïÏøçö

In addition - not everyone posts there direct links to EON tech replies.  So you might want to search at EON tech threads to find the others :)

I provide so people can see I'm not BS'ing anyone when I quote :)

Lets hope the P7 SR1 that has just been released doesn't break the new fixes.

Bite your tongue, beryld, I have just installed it!!!!!    I think I will have a tantrum if it interferes with any Vue stuff!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

dstephany: The link your clicking on is an individuals [i.e. Iloco's] tech support ticket and as such it is highly unlikely you will see other's post to it, most will open their own ticket.
As Iloco has already said, e-on have admitted there is a problem and are hopefully working on getting a fix out as soon as possible.
As I already said, I wouldn't let this issue put you off buying it, Vue6 is a superb piece of kit, I loved using it as the pre-release, in fact it has taken over from poser as my app of choice and as a 4 year user of Poser that is saying something!

Injustice will be avenged.
Cofiwch Dryweryn.

Attached Link: http://www.e-onsoftware.com/support/Forum/board.php?fid=3&cat=2&e=2197&s=2222

I'm not sure if you have to be a member to log in here, but "dstephany" if you want to see complains go there...

First of all, I want to thank everyone for their KIND responses and not getting angry. With that said I posted a message to the VUE sales/support center and they responded back almost immedately!! I thought everyone here might enjoy seeing the messages so I'll cut and paste the information and also provide a link in case you'd rather view it in its original form. Again, thanks! We do have a wonderful community here on Renderosity!!

My original message......

I currently own Vue 5 Infinite and Poser 6. I was considering upgrading to Vue 6 Infinite until I heard about all the recent problems associated with it. I was wondering if somebody there could either reassure me that upgrading at this point in time would not be a mistake or if it would be better to hold off a bit until things get resolved. As for my computer, here are the specifics on the system I'm using...Dell Dimension, Core 2, 6300, 1.86GHz, 2.00 GB of RAM and 229 GB Hard Drive with a NIVIDA GeForce 7300 LE graphics card.

Their response......

Hi Douglas,

Any and all problems are being address and will be solved. When you order is really up to you. Thanks very much for your interest.

Best regards.
Todd Ahrens

The link.....

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

It was a good reply back from them.  At least they ackknowleaged there were porblems and being worked on.
  Thats good for PR. :)

ïÏøçö

So, is it safe to download the final release yet or is it better to sit and wait for a while still :(

Tech has said they hope to have us a patch this week for the memory and Resources problems.
   You might want to wait for that to be included in your download.
Then again you may want to download and if you dont use many poser figures or models in your images you should be ok till the resource and memory problems are fixed. :)

So many ifs and ands when questions are asked like this.  It all depends on how you use Vue.  If making simple scenes with default  vue stuff you would proably be ok.   So many said it worked for them versus so many who had problems.    I think it all involves how and what you do with the application. :)

ïÏøçö

I just had another thought. It seems like all we've been hearing so far is about problems people have had who downloaded VUE 6 and installed it over previous pre-releases. 

I'm not saying this would necessarily make any difference but it would be interesting if someone were to try installing it from a Boxed version and see if that would make any difference. I'm sure the same "bugs" would still be there but I'd just like to heard from somebody like that and get their reaction.

I did a clean install.
 I have said so many time that tech support has confirmed the problem,   I will say it one more time its a problem in the Final version.  

What is the difference in a boxed version from a download if both came from same set of files.
  I agree a download might get corrupted but why has tech confirmed it if it were not in the final release they have to work with. :)

ïÏøçö

I think your misunderstanding me. I'm not denying that there is a problem with the Final Release at all. I don't think there is really any debate on that. All I'm saying is it would just be interesting to hear from someone who has tried installing it from a boxed version just to see what the result was. I'm sure its probably only going to confirm what we already know but it still would be interesting to see. However, since I just ordered a Box version online I guess I'll be able to give my own report shortly. Then I can join the rest of you!! Wish me better luck, if you want!! :)

Clean install for me too. I can't see how there is any difference in box to DL. Same file, just burned on a disk for you.  Looking for excusses where there are none. Tec admits to the problem, why is that hard to understand. Ordering a box set now may not have been a wise decision. Once you open it you are stuck with the bad version and even when the fixed version is released, your still stuck with that bad version as your main box disk. Now that is something I can't understand. Oh well, it's not my money.

I have done a clean install of the second to last pre-release and everything works as it should and soooo  much faster. All it will cost me is a new disk and the time it takes to burn it when the fixed version is released.

I did a clean install too of the final version and although it works a tiny bit better with simple objects as soon as I bring in a poser human being the whole thing isn't worth trying to move the object around in it at all.
My other complaint is the time that it takes to render a spectral cloud and if that sort of thing is never improved I doubt I will be able to use those beautiful clouds because I do not have more than one computer nor the time to let a computer run a render about long.  The clouds were one main reason I bought this version.  Oh well just have to wait and see.

Life Requires Assembly and we all know how THAT goes!

I have to agree with everyone. I keep getting memory problems with the final release and I have a mother of a system! Quad processor, 1 gig video card and 16 gigs of ram - and I still get crashes and at times im down to 14% system resource.
Im glad for the forum here, otherwise I would have never known that others were having the same problem Im having.
I hope they fix this in the inevitable final release patch.

I just downloaded the patch for Vue 5 Infinite. It will be interesting to see if they ever got that program to work.

Download my free stuff here: http://www.renderosity.com/homepage.php?page=2&amp;userid=323368