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!

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

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

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

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

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.

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!

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

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

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!

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

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!

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

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

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

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

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.

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

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

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.