I will start my own thread about Vue 6 new update and for those who don't like to reply to me wnat have to.

Here we go.

Dont any one go getting ther drawers in an uproar because I post this but I can load the USS Constituation from Kaol 1st and Faverals Medusa 2nd from Daz and get oem errors.   Now before yous start jumping the gun I did the same in Vue 5 inf and it loaded ok , no problem at all.

 With a default scene I loaded the uss constituation and resources fell to 63%  I purged memory and it came back to 64%,,,,,,,,,hmmmmmmmm,  Ok I now load the Medusa and I get the oem error on loading and when I click ok it says it can not find the medusa.    Remember  That Vue 5 Inf loaded both ships no errors or looking for a model.   :)   With previous build it found the Medusa.

Now get this.  If I take the USS Consitutaion out of my scene and load the Medusa it will load ok.............But the first time after loading the Uss constituation it gave me an OEm and  said it couldnt find the model. It then went on to my scene with one ship.   Are we now getting errors it can't find model and cancels that model so as to not crash the scene.
  Something don't add up.

Now it loads the Uss coinsitutaion as second model so what is going on with the sequence of loading.After loading second model my movements of the models re very sluggish and I am at 34%.  Purge Memory and I am back at 42%.   do preview render and resources fall to 32%.

Now I go and load Faverals Dakkar ship and get a available resources have fell below a critical level error. click ok and resources fall to 17%.  Let vue set and it falls another 1% to 16.   Purge memory and get back to 31%.

 Found a preview problem but have already reported it to tech. :)   Good Luck you people who use lot poser stuff in your renders.       I am a little disappointed to say the least.      Still not prime time yet for me........:(

I am curious what others who use poser figures think about this new update......?

This time around I will be watching and reading instead of posting what I think are problems.   I will contiunue to report to tech support......:)

Personaly and this is my opinion it is no where near what Vue 5 inf is..

ïÏøçö

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

I already reported it :) No change since the last :(

Just curious.... did you try the same experiment with and without OpenGL on ?

• agiel - www.linfa.net

What was that "preview problem" about, Iloco?

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

Here you go jc.  Sorry I did't think about posting the tech link.   I ahd it to them before and they said it would be fixed in this update but my ticket got deleted by some unknown reasons..

agiel I will give it a try with out open Gl. I always use open gl and it has always worked fine for me in Vue 5 Inf and Vue 4.5 Pro. 

ïÏøçö

I tried with openGl off & on - I only got from a 42-46% increase with still a crash...also had background draw off & undo's at 1...FYI.

Herein lies the problem - you load the item resources drop  - delete the offending item - purge the memory - you get nothing back...in fact when I tried at 1 point, Vue crashed while purging the memory :(

Also another keypoint - it works in V5I, smooth as silk :)

To be honest its much slower loading models uising wirframe for me than open gl hardwaresetting.
 It did load the 2n ship the meduse abut good gollie if we have to wait as long as it takes to loade we got big problems.  It never did get so I could move the second ship around and its name never did appeear in the right browser area where you see the models.   I used task manager and it had quit responding.     Sooooooooooooooo.

Quite frankly I am getting very disgusted with all this messs that is suppose to be a professional Final release thats been in the works for over a year or maybe longer.   I can care less what others think but thats how I feel...........:(

Why is it that Vue 5 inf can work so good and Vue 6 inf is no where near what it is......Soemthing is bad wrong somewhere. :(

ïÏøçö

Just an idea, but what happens if you use Vue Infinit 5 to import the Poser model, save as vob, and then use the vob in Vue 6 Inf?  Do you still have the out of memory problems?  

I'm working on a scene.  In the "good" pre-release, it was fairly stable around 45% resources.  When I open with the final release with patch, it drops down to about 29%.  If I wait a few minutes it goes back up around 32%.  A purge memory brings it up to about 60%.  I need to purge memory about every 15 minutes or so.  Even when the resources drop to less than 30%, I have not noticed any slow down.  Just makes ME nervous!

I don't have any problems moving things around, and believe me, there are a ton of high texture models in this including V3!  What I did do is convert everything to vobs first and then start putting everything together.

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

Yes peggy I have done that. You name it and I have expermented with trying to get Vue 6 work as Vue 5.    It has a curse on me.........:(

Why don't we need to purge memory in Vue 5 Inf is what I don't understand.   I mean I can keep loading stuff into it till it gets sluggish and I then save and restart if need be.   Usualy if I wait a few minutes the sluggish stuff will go away so I can play some more.   Not in Vue 6........:)

Yes I only use vobs as well........I just dont know......:)

That pre release seems to be the best attempt at giving us somehting that half works since we been beta testing Vue 6. 

ïÏøçö

I kept the prerelease in the Vue installed directory. I have the final release in another folder. E-on says to uninstall the pre release. Well you don't have to....I just made a temp folder, cut and pasted the pre release into that. Brought the final version into the e-on folder and ran the update. Then I just moved everything back. Both work just fine.

I'll have to expore it tomorrow....g'nite.

M

Here we go again. The ones that don't use poser stuff are going to tell the one that do that there is not a problem and it is your fault. Again. I see a pattern here. (Shakes head and walks away) Let me know when the final is really fixed and the rest get thier heads out of thier south end long enough to admit there is a problem.

I'm glad I saw this thread this morning, I tried a scene I'd had issues with before and the same old, same old, resource messages, dropped to 13% yada, yada!
And like you Iloco and others this scene was fine in pre-release!

Injustice will be avenged.
Cofiwch Dryweryn.

I wish we had access to the beta forum since we finding most the errors and crashes and as Cheers said we could keep up with whats fixed and whats not fixed.
 Would make it lot simplier to keep up with things instead of everyone reposting to tech the same old thing. :) 
 It does seem they could use some more help.........:)

Is e-on listening to its customers or its inner circle that is close to it.   Something has got to change and fast or its reputation is down the drain.   I would hate to see this happen to a companys whos software I have really enjoyed using when it worked as it should.........

I would love to see Vue back as it was when we bought Version 4, 4.5, 5 inf.
   Thats when started having problems after that will all the added stuff I an lots others didn't buy vue to have in it..................Will praobly never see those days again but Hey I can wish cant I.
Vue and only Vue is all I want.    I know where other stuff is and what I want to buy. :)

ïÏøçö

On my mac, I still can't import props eg hair, water bottles, belts etc attached to my daz figures into vue 6 final update. I'm very disappointed as I thought I identified the problem (I can fix it by removing the backslashes in the PZ3 .obj path for the props) and I told eon some time ago and they seemed grateful. Was i wrong or something? I would have thought it would be a really easy thing to fix (especially as vue recognizes backslashes in the texture paths of the PZ3 with no problem at all.) Any mac users out there having this problem too? BTW instant reproducible crash if I try and import the pz3 without ticking the collapse identical material box Love esther PS yes - i've reported both these problems to eon since trying out this new upgrade of the upgrade! PPS I'm using poser 7 but haven't applied the poser 7 SR1 upgrade as yet (too scared)

MY ONLINE COMIC IS NOW LIVE

I aim to update it about once a month.  Oh, and it's free!

WEll its the little things that are adding up if people read all the post and take note of them.

For example in that Render ranch thread it was said that e-on tech was working so Freds Render Ranch would work with the copy protected models.   Now how much time delay will this take when they could be working on fixing bugs in Vue for us.     I ahve nothing against Fred at all but after reading that little note it kind got with me that they have time to veer off of vue and do other things because of the copy protection.      It reminds me of Washington Politics.  You either in or you out. :)

I can not get anyone to answer me with how many man hours is lost to coding new updates and the new CP models when they are copy protected.  It has to add up if only takes say a few minutes of time unless they have it so its automated.

I wish e-on luck and the sooner all this mess is fixed the better.   I miss haivng a new version that I can work with and not get errors and low on resources.    I really got to hand it to tech support for hanging in there but wonder when burn out will take place. :)   Has it already.......??

ïÏøçö

Must be they have more updates in the wings because the reply I got from the techs was that  such and such an issue is fixed in 'above build 290146'.  This is build 290081.  I don't quite get what that means except for a longer wait.

At the top of the "what's Fixed" portion of e-on's site they say that the patch is BETA.  Sorry it didn't help everyone, but some of the problems are fixed.  Have a little faith, it's going to get better.

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

I have always heard faith can move a mountain.  I think we got a big one we trying to move..........lol.
 I read a beta but keep wonder why more betas when there are still bugs.   Was it to satisfiy us for another few weeks..........Don't add up. :)

ïÏøçö

Interesting that they ask for a model upload to test. Not like this is actually tied to one or a few models.....

So what, are they trying to blame some of the models for the mem problem? Those numbers that monsoon posted, I hope they skip a few numbers when they label the SR1  SRs or it's going to be a long wait for a proper fix. This just keeps getting better all the time. Doesn't give a person much faith in what's going on, does it.

No it doesnt after 6 months of beta testing and we still getting beta updates after a final release.
  
You know a lot of the people will say there is only a few who voice their opinion and I guess they are right.  I know of lots of forums where there is people who speak up that don't do it here.
  I know a lot don't like to be questioned about it works for me but so should for you.
 I say prove it with doing what we do to get errors and oems. :)

Would anyone buy a new car and get it home and say the computer chip messed up or went out so it was useless and you called the dealer and they say well you will have to live with it.    I think not or at least I would no go for a reply back from dealer like that. :)

ïÏøçö

I'm really close to saying F*** it to the lot to be honest, Vue6Inf doesn't work properly, Poser 7 doesn't work properly, I mean really, it's taking the piss!
The thing that really pisses me off is that the pre-release 288741 worked great, so what happened!!

With pre-release working like a dream I could still use Poser 6 with it so I was a happy chappy, now I'm back to using only Poser 6 which is where I don't want to be!!
I prefer working in Vue6, the lighting and render engine are better than Poser.

Injustice will be avenged.
Cofiwch Dryweryn.

If I didnt like vue so much I'd done left but there is nothing I have found I like as well.
Back before Vue 6 and all its changes is when it has gone down hill But O know no one listens to its customers but I bet they listen to a few whom If I were the CEO would fire in a heart beat.

 I use to have 25 employes whom worked for me so I am not as dumb as my Duh avatar suggest.   

Honesty and Truth have always prevailed and Ido have faith it continue will so we can get what we want. :)

I know how you feel thefixer.....:(

ïÏøçö

I don't have Koal's USS Consitutaion, but I do have the Golden Hind.  His ships are beautiful, but resource hogs!  They also import with lots and lots of extra stuff that you may or may not want in your scene.  For example, both the furrled and full sails are on the ship when I imported it.   It has details right down to water buckets.  On my crappy work computer with only 1 GB of memory I can import the ship with everything.  My resources drop from 79% to about 52%.  Purging memory doesn't really get me any more resources back - this model is just plain BIG at 571,034 polygons!  I converted it to vob, but the resources still remain the same at about 56% to 62%...

Vue is not acting unreasonable for such a huge model.  Adding another large ship without getting rid of some of extra stuff may not be possible.   

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

Here is a picture of my system details, just in case someone thinks I have a supercomputer...

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

I see your point Peggy but with pre-release I was quite happily doing scenes with many millions of polygons in with no resource issues at all, in one which I posted at C3D and was used by them, had Kaols Sea Traveller in it which is another huge ship plus Queen Annes House plus the Wharf by MDM and a water plane and a spectral atmosphere!
Can't remember the actual polygon count and I'm in work right now so can't check but will when I get home but it was multiple millions without issues.
Now the same scene with final release plus update can't hack it, you tell me why, because I've changed nothing on my pc in that time?
It would be easier if it were a change I'd made because at least I could undo it, I can't undo this!

Injustice will be avenged.
Cofiwch Dryweryn.

I see the same  as thefixer.  I am using 1.5 gig ram with about same specs as peggy.
  It is just plain simple not as Vue 5 inf with its resource and memory issues.
Why is it suppose to be a better piece of software when it can not do what it previous versions did.     All one has to do is compare versions or build as thefixer.
   I dont know the answer but I thought we were going to get more than we have got so far with Vue 6 Final. :(   Disappointed big time. :)

ïÏøçö

I'm surprised to hear that the memory issue is still there.
I did not see about the update till this morning.
I went back to pre release 288741 last week, and it's great.
I guess I don't need to bother with this update at all.

I am wondering if by having 32 bit and 64 bit and now vista is having a lot to do with this.  Just a thought.
 Maybe they need to concentrate on a version for each operating system is this is going to be how it is.   Something is bad wrong and its not been improved. :)

Same ole Same ole is getting old. :)

ïÏøçö

If it carries on much longer I'm going to uninstall it and put the pre-release back in with update 288741 because that rocked, I'll give it one more update to see if it improves but that's it, enough's enough!!

Injustice will be avenged.
Cofiwch Dryweryn.

thefixer there is one thing I am wondering about with the prerelease is will it have a time bomb it in soit quits working after a certain date. :)
   Thats how a lot betas are done so to force the testers to buy or upgrade the product. :(

ïÏøçö

I'm always getting confused with the versions...

I had bought Vue 6 Esprit (not easel, infinite, super-dooper or wahtever) pre-release about 3 weeks ago and downloaded it. I got built 288792 and was generally quite happy with it. Now i got the final release notice in my email and downloaded the new version. I now got built 289779. Yet i didnt have any problems, but i have to admit that i did NOT import any poser stuff at all (A shame, got Poser 5, wasnt cheap and I dont use it) so far.

As an extreme test i made a scene with 3 million polygons and over 11.000 objects. I dont know how many polygons your ship models have, but for my computer 3 million polygons is when it starts getting real slow (2 GB ram, 3 Ghz windows Vista 32). From what i fell regarding speed it might be a bit slower, but thats probably not objective, its just feeling, i cant tell it in numbers of system resources or so.

My question: Are we all talking about the same build numbers, or do i only have "bad" built versions? Are these problems only affecting infinite or is that for all versions? Are the built numbers the same for all versions (easel, esprit, infinite, etc)? I have the botanica, ecosystem and lighting module - are these also affected by the update? Or will there be separate "module updates" for esprit users?

Vue content creator
www.renderarmy.com

@estherau - I'm using Vue6ESP-Final on a dual G5 with 10.3.9 and have a similar problem importing some objects if I use P7. If I use P6, Poser scenes import fine with all objects intact. On the plus side this version of Vue6 seems much better at finding textures then the pre-release version. On that version Vue6 would ask the location of just about every texture in a Poser scene. Two steps forward, one step back ... BTW, I installed the P7 SR1 and have had no problems at all with the update.

Thats a good question maybe someone else can answer.  I use Vue 6 Final so would be curious as well.

 I do think you get your updates from a different place than the Vue 6 Final users get theirs. :)

ïÏøçö

Iloco

 

I am running Vista x64, and it is way different than Win 2000, or XP. It handles memory different, all kinds of new stuff that is not compatible with previous versions.

 

On the e-On site they tell me not to download any patches as they will not work with Vista. 

 

So I am between a rock and a hard place.  Only e-On knows what is going on.

jankeen.com

Its a mess for sure....:(

ïÏøçö

*As an extreme test i made a scene with 3 million polygons and over 11.000 objects

*You see to me that isn't an extreme test, I have done scenes that have 2 or 300 million polys in easily in pre-release especially if you start doing eco-systems with some of the more poly hungry plants and stuff, but then with so many different variations who knows what is going on. My system is similar to yours with 2 Gig RAM and a 3.4 GHz processor but I'm running on XP home!

Injustice will be avenged.
Cofiwch Dryweryn.

That didn't take long for someone to tell you that it's the model and not the software. Totally ignoring the fact that these models worked in the pre-release.Yep, going to be a long and frustrating wait and see if this ever gets fixed.

I'm back using the pre-release again. This is getting to be total BS having to uninstal the fixed final and re-install the good pre re-lease.

Quote - *As an extreme test i made a scene with 3 million polygons and over 11.000 objects

*You see to me that isn't an extreme test, I have done scenes that have 2 or 300 million polys in easily in pre-release especially if you start doing eco-systems with some of the more poly hungry plants and stuff, but then with so many different variations who knows what is going on. My system is similar to yours with 2 Gig RAM and a 3.4 GHz processor but I'm running on XP home!

 

Which built number is the best then? Is this 288792 (my first one) better? Or did i miss the good one without any chances of getting it? Well so far i didnt have many problems, one crash on a boolean operation, but i already had these in vue 4...

Vue content creator
www.renderarmy.com

I love not being a Poser user.  :)   :)   :)

-Ryan Spaulding
 VueRealism.Com

RyanSpaulding wrote: *"I love not being a Poser user.  :)   :)   :)"

*Your lose and very poor taste posting that, just to rub it into user who do like to use it and spent big money on a software that advertises that it is suppose to work in. Not Funny.

No, I'm with RS, on this one.....

beryld, didn't you start this with a gratuitous, loving and fully supportive comment about non-Poser users at the beginning of this thread? That first comment was in such good taste, and of course, it was fully required and added to this subject immensely !

If there were no poser users I think both daz and e-on would loose a lot of money with their products.
 Isn't both suppose to work together the same as 3ds and other models.   I personaly see no difference.   I do see a lot of non poser users missing out on a lot of good models that can be bought at daz and used in Vue.   IMHO only. :)

ïÏøçö

haegerst: For me the pre-release version 288741 worked the best, I had no resource issues with it, period!

If I compare the final release with that one, it's a bag of spanners!!

Injustice will be avenged.
Cofiwch Dryweryn.

For me, with pre-release version of Esprit, i just could not render a pict larger than 1024 wide (memory issue...). Now with final, i am able to render in hi-res. So the final is best for me, cause what is the stuff if you cannot get a useful render?

My Store

Well, you proved my point very well for my first statement. That's OK, keep your heads buried in a hole and only pull them out to make a comment on something you don't understand what is going on. Late inposting so that goes out to the non poser comments.

I don't know how well the other versions work. I'm using Vue6I. Did you import a Poser scene into your version and did you have any mem problems like we have with the Vue6I final.

I don't want to be one of those who say "it works for me".  Let's try to figure out WHY it doesn't work NOW.  Saying it worked for an older version isn't going to help.  

This patch was a beta release.  It did fix some bugs, some are still there, maybe the next one will make it work for you guys and screw it up for me!  

All we can do is hang in there and work together to get info to e-on's tech support.  

Peggy

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

Very well said Peggy.   A reply with some common sense. :)

ïÏøçö

I suspect iloco is on to something about addressing each OS. Running under WinXP64, Vue6 with the new beta patch is working "decent" for me. At least Poser figures are no longer a problem (without resorting to the old vob work-around), and opengl/display problems are less. Actually, on my system, it's the best release yet. Certainly not perfect, but improving.  Otoh, I had tons of problems with the next to last pre-release everyone else seems so pleased with. 

Hmmm, that next to last pre-release didn't do well for me on my old W2K system, either. In fact, I've already removed it. Guess I'll try the final with the patch on the old machine just for laughs. If it'll load more than 1 or 2 Poser figures, then there's something else going on.

Can we all please get back to the facts - PLEASE!!!!

OK - I was importing the US Constitution - I tried in 2 formats

OBJ = 38,032 KB MTL 7KB

This same item converted to .VOB = 94,501KB :blink:

I thought I hit upon something here - but no.  As you can see saving as a .vob tripled the file size - WTH - I thought .vob was supposed to help things out...but in the end this made no difference whatsoever, the results were the same.

Importing either way has the same affect. Resources drop to 63% ASAP - I delete the ship - purge memory & only get back to 66%. If I add yet another item Vue either crashes to desktop or crashes while I'm actually trying to purge memory. In V5I - I drop to 75% & when I delete I recover back to 88%( I always start with 92-93% open) Purging in V5I get me back to 80%.

Something isn't right here...I  import an item at 1/3 rd the file size & still yield the same result - something is amiss.

The viewports dramatically affect the resources. Use this knowledge to help keep resources at a safe level. I watch the PF useage in the task manager and purge my memory when the PF reaches the 1.5 gig. After a second or two the PF drops down to 400MB. The vue resource % may not be accurate. This update is a step in the right direction. I been working with vue final's last update and I wouldn't dream about going back to the prerelease. There are too many things that work better for me to do that.

You may have the dreaded Memory Leak, where threads are not being processed, or purged correctly. 
Usually the only way to get out of this situation is to use Task Manager and Shut down the app.  If not, with the memory tied up in bad threads, your app will crash. 

jankeen.com

Its  a same we have to revert to so many things to get a piece of sofware to work when the previous release of Vue 5 inf doesn't require it and goes ond on like the battery bunnie not needing all this.
 I see people still don't get it all......... It

Tech said it would be reverted back to how Vue 5 inf coding worked so we would not have the memory and resource issues we are still geting but I can see they have not done it with last update..

I loaded one poser model last nite and my reosurces dropped to 43 % and then when added a spectral atmosphere it dropped to 19 % and Vue got so sluggish I was not able to continue.  Two items and Vue is useless if going to add any more.     I say once again Vue 6 is not ready for prime time yet...........:(
  
For those who are using instances then this will not effect you as us who are using obj and vobs.
I

ïÏøçö

I'm trying to get one done now, 4 lights, normal atmo, 72 objects and 345,000 polys and it's choking!
I have to keep purging memory because it's dropped as low as 9%.
Sucks!!

Injustice will be avenged.
Cofiwch Dryweryn.

What I don't understand is the prerelease before that last release for beta worked with out having memory and resource issues and tech said they were going to revert back to that.
 It seems to me they havent even tryed to give us back something that did work and now don't work.
   I will never fall victim to a pre release version of Vue again.as we were duped into this one and now still got a prerelease when its name Final and now getting beta upgrades for a Final.....Gheeez who ever heard of such stuff.
  Some body is not testing this software as it should be if we the customers can find such simple things as it will not handle resources and memorys issue when the prereleases would and Vue 5 inf would.
  And I don't care about hearing excuses it works for me.   Sure it does if you don't use it as I want it to be used and that is like Vue 5 inf. :)   

ïÏøçö

They're asking for all the poser files in the scene now, which means they'll need the lot not just the pz3. A pz3 is useless to them without the obj's and textures that it's looking for!!

Injustice will be avenged.
Cofiwch Dryweryn.

Same with a ticket I have with them.
 They will be asking for our comptuers the next time around........?

ïÏøçö

More work but have you tried to use the Administrative Tools and search through Event Viewer.   

At the time a crash happens, look through all of the Logs in Application, Security, System and so on, and click on an event to find out what caused the crash.  This could tell you what module was causing the trouble and give e-On more info.

jankeen.com

What causes the crash and problems should be fond by e-on.   Why do we have to do it all for a final thats been in developing since early last year or before.
  And to answer your quetion Yes I have done all that you have asked and more. :)
Not wanting to sound hateeful but Why didnt the beta tester find these problems before they release the patches.
  If all they are doing is using simple to be made scenes with instances and bill boards instead of models as most users are doing then they are missing a lot of the problems as it seems to me. :)
 WE need to find why they can say they dn't have a problem when lots of others do.  Lets all be on the same playing field as I see it.
  Also when we see some pics posted are they using a beta that we as regular users dont have acess to.  Lots to be consider with all of this since its still in beta. :)

ïÏøçö

Well, not sticking up for anyone, but when I used to work for a company, and we released our new Word Processor for Beta testing in house, after six months of hard work, there were 256 bugs, on the 17,000 computers tested.  We fixed all but 11 within three weeks.  Those 11 got shipped with the Word Processor, for which we put out a patch later.  

As a programmer you really never know what is going to break the software until it happens.  The real problem gets you when you patch something and then that patch breaks the system for others.  

Trust me when I say I burned out after four years and got out of that job.  No way would I want to be in e-On's shoes. 

jankeen.com

I agree with you 100% and wonder how much of the problems now are related to burn out with programmers and even the beta testers.....?

I for one could not handle it as some of the tech does. :)

ïÏøçö

I used to send the log files to e-on also until one of their techies responded with "this doesn't really tells us much so don't send any more"
The fact is, these log files almost exclusively pointed to something happening within Vue 6 because it's name was there for all to see, what it meant I have no idea but from their response, not a lot!!
I'm trying hard to help I really am, I want it back working as it did!!

Injustice will be avenged.
Cofiwch Dryweryn.

This is just not right. We paid for a working program. Will I install the beta? Well got the email for it this morning and the link isn't working so came in here and read this and don't know if I would install it if they do get the link to work. I'm SO sick to DEATH of companies banking on our loyalty to a product and spewing out crap and THEN acting like it's our fault. Oh your model must not be just right for it to work. No more Vue for me. I'm still ticked about the fact that apparently the image resolution ability of matchmover is not as good as the pro version. Why do I say that? Because I just got an email telling me if I upgrade it I will get the higher image resolution I was told I would get in the first place!!! Bad e-on and anyone who defends this.
Marque

Just a comparison Vue6 Esprit "Final" vs Vue6 Esprit "Beta"

Loaded a scene with just 1 poser figure , polycount 178940. This scene worked well in the beta version of Vue6, build 288792.
Rendered the scene in preview full screen (1024X800). This toke a whopping 35min 06 seconds to finish. Memory usage 1.4GB , monitored with windows task manager.
Re-installeed the beta version of Vue6 and rendered the same scene, also working in wire frame mode. Render full screen in preview, Time to render 1min10sec. memory usage 537 MB.

Pc : Pentium4, 2.4GHz, 512MB Windows XP

This says it all

Wim

Personaly and this is just an opinion is the tech said they would put it back like the beta that was good and I don't see they have done it all. :(

ïÏøçö

Yep. they lied.  They have not done what they say they would do. They are listening to the one side that doesn't use Vue the way we do. It gets tiring very fast with the did you do this and did you do that when the fact is, there is a mem problem that they don't want to address. Even though they admit that it is there.

Sending them a pz3 is not a good option. First you need the object and materials that were used in it and it is totally against copyright to give them these objects. Are you going to tell me that e-on does not have a copy of Poser to make thier own pz3's and use Poser content. Is this why the major F up? I call BS. 

I have vue 6 pre release and I have downloaded the final version and the latest update to the final version. Should I wait to pull the trigger on the final version? To update or not to update that is the question.

I regret fully at this point, taking off the pre-release and installing the final, period!!

Injustice will be avenged.
Cofiwch Dryweryn.

Quote -
Not wanting to sound hateeful but Why didnt the beta tester find these problems before they release the patches.
  If all they are doing is using simple to be made scenes with instances and bill boards instead of models as most users are doing then they are missing a lot of the problems as it seems to me. :)
 WE need to find why they can say they dn't have a problem when lots of others do.  Lets all be on the same playing field as I see it.
  Also when we see some pics posted are they using a beta that we as regular users dont have acess to.  Lots to be consider with all of this since its still in beta. :)

Well iloco, to me, you are sounding hateful. I was one of the beta testers and I and MANY OTHERS find Vue 6 works just fine for me. I do see there are a handful of users here who aren't happy, but there are others who are. I don't appreciate you denigrating the hours I and other beta testers spent submitting bug reports, outlining on websites exactly what's wrong, and working our best to help Vue deliver a good product. And this is the thanks I and other beta testers get from those of you who won't even bother to send in a scene file.

It's obvious you have no respect for Vue. That's fine and up to them to deal with. Disrespecting others who are here and have tried to help is no way to conduct oneself in a community.

-Chipp

 

Hi, I do appreciate the work of the beta testers. I do think though that e-on should have asked more people to beta test - us. People who use poser and vue a lot. There are big problems and "I do see there are a handful of users here who aren't happy" if you look at all the people who want to use poser and vue together I think there are many many more than a handful who are finding the software really difficult to use because things aren't working as they should be. Here's a small example. I have a mac and poser 7. When I import a pz3 it won't import any props, so my figures come in bald. I asked at either eon or cornucopia and lots of people said they were just getting instant crash on trying to import a pz3. I don't get the instant crash because i know I have to tick the box that says about same materials on import. However I also discovered that the reason the PZ3 doesn't import the props, is because poser 7 saves the obj paths for the props in the pz3 with backslashes but the path for figure .obj with : the paths for textures have backslashes and now vue handles that fine but not for those prop .obj path. This seems to me like it would be an easy fix but vue are blaming it on EF "The paths handling is not done in our code, but in the Poser SDK, so we can't fix it ourselves. We hope the SDK developpers will be able to fix this (it is by the way quite strange that the poser file was saved like this...)" Well who knows, but the e-on advertising says poser 7 and vue 6 are compatible and they are not at present. Some people use these softwares to generate their income, so can you see now where all this frustration is coming from? I should have thought thenot importing of poser props with poser 7 could have been fixed by now, surely. Love esther PS I must admit poser 6 used to work beautifully with vue 6 until poser 7 came along.

MY ONLINE COMIC IS NOW LIVE

I aim to update it about once a month.  Oh, and it's free!

Oh, by the way, I love vue to bits. that is the really frustrating part. Love esther

MY ONLINE COMIC IS NOW LIVE

I aim to update it about once a month.  Oh, and it's free!

Maybe you should have beta tested it with poser.

Proves all my points , again.

Attached Link: Poser Import Example (semi-nudity warning)

I did beta test it with Poser.  And it worked fine.

I am extremely displeased with the final version.  One of the main issues I am having is that magnet deformers from Poser are no longer applied to the figure correctly.  I have attached a picture what happens when importing from the same Poser 7 save file between the pre-release (left, correct) and the "final" version (right).  I'm seriously thinking on reverting back to the previous pre-release.

¤~Giolon~¤

¤~ RadiantCG ~¤~ My Renderosity Gallery ~¤

My reply was not at aimed at you Giolon.

It helped me - several bugs that were really a pain are fixed.  The only problem I am still having is with network rendering.  

Will it work for you?  Install and try it.  If you have problems, contact support.

P.S.  I am fed up with this forum.  All everyone wants to do is whine about how bad Vue is.  Your not helping yourselves or anyone else.  Get over it, I really don't care if the pre-release worked for you.  That's old code.  What we have is the final version and any new patches that come along.  If you have a problem, document it, and send it off to tech support. 

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

I've been sending all my problems to tech support. Love esther

MY ONLINE COMIC IS NOW LIVE

I aim to update it about once a month.  Oh, and it's free!

Quote - Maybe you should have beta tested it with poser.

Quote - My reply was not at aimed at you Giolon.

I assume then it was aimed directly at me, and not any of the other beta testers.

While I did not beta test the Poser import, it was tested by other, more experienced Poser users than I.

I tested the parts I knew about. You can check out my website at:
www.altuit.com/webs/altuit2/VueStepbyStep/AboutStepbyStep.htm

for more information regarding how I use Vue. I've recently updated my Vue Python plugins which include a new 'Mirror' function. I also have a number of tutorials on terrains as well as Fog & Haze in Vue. I try my best to support this community.

 

No one is questioning your support to the community. That has absolutely nothing to do with the issue at hand. You as a beta tester post to a thread that is based on the poor mem problem with Vue when used with Poser. You say we don't have any respect for Vue. Respect has to be earned. You also admit to not testing with poser, yet you still felt the need to tell us we are in the wrong. and don't except help. But, funny thing is, all the ones that seem to keep telling us that and telling us it is all in our heads and it works fine for them, are not poser users. And you wonder why people get upset. I don't understand why that is such a hard concept for some of you to comprehend.

As for pointing at you and not other beta testers, you are the one that posted. But you can point the others to the threads if you want. I'm used to being labeled the bad boy. Sorry but I'm not afraid to say what I think unlike so many others. That may be a good reason why you and e-on think there are only a very few of us that have a problem. The others are scared to say anything.

Quote - You also admit to not testing with poser, yet you still felt the need to tell us we are in the wrong. and don't except help.

Absolutely, an untruth. No where did I accuse any of you as being in the wrong. I am certain each and every one of you has REAL problems with Vue.

If you would please reread my comments, you will see I was responding to the notion that beta-testers were not effective. That's it.

It's obvious beryld, you're just looking for a fight. I can't find a single post where you've said anything not negative. Nor have I seen anything which resembles helpfullness.

A quick search regarding your recent posts:

Re: Vue 6 Final Update Relevance: 100.0% My reply was not at aimed at you Giolon. Last Modified: Thursday, March 15, 2007 10:56 pm / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% Maybe you should have beta tested it with poser. Proves all my points , again. Last Modified: Thursday, March 15, 2007 10:19 pm / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% Yep. they lied.  They have not done what they say they would do. They are listening to the one side that doesn't use Vue the way we do. It gets tiring very fast with the did you do this and did you do that when the fact is, there is a mem problem th Last Modified: Thursday, March 15, 2007 3:52 pm / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% Well, you proved my point very well for my first statement. That's OK, keep your heads buried in a hole and only pull them out to make a comment on something you don't understand what is going on. Late inposting so that goes out to the non poser comment Last Modified: Wednesday, March 14, 2007 3:08 pm / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% RyanSpaulding wrote: "I love not being a Poser user.  :)   :)   :)" Your lose and very poor taste posting that, just to rub it into user who do like to use it and spent big money on a software that advertises that it Last Modified: Wednesday, March 14, 2007 2:43 pm / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% That didn't take long for someone to tell you that it's the model and not the software. Totally ignoring the fact that these models worked in the pre-release.Yep, going to be a long and frustrating wait and see if this ever gets fixed. I'm back usin Last Modified: Wednesday, March 14, 2007 2:17 pm / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% So what, are they trying to blame some of the models for the mem problem? Those numbers that monsoon posted, I hope they skip a few numbers when they label the SR1  SRs or it's going to be a long wait for a proper fix. This just keeps getting better Last Modified: Wednesday, March 14, 2007 8:08 am / Forum: Vue / User: beryld

Re: Vue 6 Final Update Relevance: 100.0% Here we go again. The ones that don't use poser stuff are going to tell the one that do that there is not a problem and it is your fault. Again. I see a pattern here. (Shakes head and walks away) Let me know when the final is really fixed and t Last Modified: Wednesday, March 14, 2007 1:13 am / Forum: Vue / User: beryld

 

"It's obvious you have no respect for Vue. That's fine and up to them to deal with. Disrespecting others who are here and have tried to help is no way to conduct oneself in a community."

That's what I read. I"m sure your going to say that was at someone else but it is really directed at anyone that is having this problem and has anything to say about it.

Not looking for a fight, just telling you what I think. And very ####### frustrated. I bought under the advertizing that Vue 6 would work properly with Poser.

Did posting my posts make the sun shine brighter for you? Better than? Maybe you should have posted all the good things I had to say about Vue before the final release. No, that would not be right, would it. Oh well, it makes you look good.

Chipp - give up, this is something you can not win. There are always people that, when something does not work for them but for others, know exactly that the others are wrong. No need to look for their systems. I gave up arguing a while ago, will not change anything.

When I read how much experience some people have with Warez sites that I can not find via Google or whatever i am not surprised btw that some systems have problems.

So let's concentrate on doing images Chipp. And other interesting stuff. You do such great work at the moment.

Main reason why I posted this here and have not wrote an im to Chipp is to get notifications about this thread. This is so good entertainment.

PS: No need for others than Chipp to answer to my remark - to play the same game as some here. So don't waste your time.

One day your ship comes in - but you're at the airport.

Hi Wabe,

People who read this forum end up forming opinions about Vue. Many times these opinions lead to purchase decisions, whether to upgrade or buy products from e-on. These purchase decisions affect e-on's ability to afford to fix bugs, add features and new versions and ultimately survive in an increasing competitive and tough 3D industry. Sadly, I have used other great products which for one reason or another, did not fare well economically and are no longer available.

I just would like to make sure for those who visit here, there are other opinions about the quality of the software. Thankfully, beryld pointed out in his last post, how he has spoken favorably about Vue in the not too distant past.
 
To me, that is important.
Thanks so much for your concern.
-Chipp

 

* If you have a problem, document it, and send it off to tech support. 

*We have all done this many times Peggy and we're not whining we want an app that works, that's all, is that too much to ask for our money.
It worked before, it doesn't now, that's a fact, not a few of us whining!

For the record: e-on said that they had changed the way the final release [the last pre-release update also] uses and accesses the available system memory from the version 288741, they said it,not me, not Iloco, or anyone else and it "seems" that, that is the biggest single most reason for all the problems.

Injustice will be avenged.
Cofiwch Dryweryn.

Chipp, wrong answer I'm afraid.

You will hear now the freedom of speech thingie (again). And that this is not an e-on forum. Maybe some will even unmask you as devilish e-on sales representant. Be warned.

I think people who are interested in buying the software simply should look into the galleries. A lot of arguments are there. Absolutely NO Poser imports into Vue 6 can be seen there.

One day your ship comes in - but you're at the airport.

Attached Link: http://www.renderosity.com/mod/gallery/index.php?image_id=1358578

Actually Wabe you're wrong, there are many of my images in this gallery with poser peeps in, one with 6 poser peeps in [this one], but they were done in the pre-release version, the final version won't touch these files now!

Injustice will be avenged.
Cofiwch Dryweryn.

thefixer, my last image - posted in the gallery here - has 35-40 Poser 7 imports into the final release, build 290081. Ok, four different ones only but then copied until I got all I needed. And all as regular meshes, no instances (ecosystems). PLUS, two ecosystems, one even with the bulky conifer from Cornucopia. And that is a heavy model.  No problem at all here. Am I wrong in doing that?

One day your ship comes in - but you're at the airport.

Chipp I can see the truth hurts.  I did not name any names and I know how beta works and thats probly the reason I was not  asked back into the special group who do the testing.
 
  I did not name any names and I can see you are very frustrated.    I do have memory and resource problems with vue  and you can take it or leave and call me what ever you want but I have not bashed Vue because I liek the program.  Just saying I am having problems with it and poser.

Sure anyone can load a bunch of simple scenes and bill boards and make a scene look like its got a lot in it but PLEASE DO AS I HAVE SAID.  Go back to Vue 5f inf and use it and dot he same with Vue 6INF and there is no comparsion.  Vue 6 INF will not do what it does.

Little groupies taking sides is no good and shows most are acting like children.  Lets all get to why our Vue is not working with Poser models and see if this cn be fixed.   Enough harm has been done since C3d store went online with people taking sides for and against.   We know e-on don't listen to a lot off its customers but a select few so its time to move on.

Chipp I do agree its a black eye on e-on when potiental people read the threads and do not buy Vue.   That is not what I want and what ever you believe is up to you.  I don't care what you or anyone thinks if I have a problem I will discuss it and hope it gets fixed.
 For those who dont have problems why take the time to lash out at us who do.  Don't get it since you so happy with your working version that is not like my version that will not handle poser models. :)

ïÏøçö

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

Wabe you just dont get it all.   Some of us are having problems while you don't.   Can you admit we may be haivng problems instead of showing how you can load up a scene with all those instances to make us look bad.  Go back and get those ships and models we have been having problems with and then tell us you dont have problems.   Lets do it on a fair playing field and use the same as comparsion as tech keeeps saying.  they got to have the exact same models to recreate the problems. :)

Load the Uss Constituation by Kaol and then the Medusa by Faveral and try and load another if you can get that far. :)
  this is in a default atmosphere with nothing else added. :)

And for those who think I and others are not reporting to tech I have attached a link to a ticket you can keep eye on to see what is happening. :)

ïÏøçö

I've seen the image Wabe and no disrespect intended but the figures don't look that resource heavy, probably very small compared to a V4 or 2 or 3, if I'm wrong please put me right and I'm sure you will [LOL].

OTOH maybe you could supply us that are having problems, your computer specs and maybe your actual work flow for creating such a complex scene in Vue6Inf so that we could see how you can manage it or if your computer is a far superior one with 8 Gig of RAM or something!

I'll say it again and John canver at e-on will back me up on this, I just want to be able to use it like I did before, it's not an anti e-on rant as some would have you believe, it's merely a desire to have something that I paid good hard earned money for [like the rest of us] to work like it did before, I'll ask again, "Is that too much to ask for?"

Injustice will be avenged.
Cofiwch Dryweryn.

Ok, here is a screenshot - talking about truth.

And yes, I switched the background characters to boxes to make things faster in display. Now show me the billboards in here please. I really would like to know where I have used them. Btw, 5.5 billion polygons in here - talking about simple scene. Render time - if anybody wants to know - 30 minutes approx. on one machine only. Not too bad.

The major difference that would make the discussion a lot more relaxed are two tiny little words. And they are "for me". Nothing else. So a report sentence should read "Poser import is not working for me".  And not "Poser import is not working". There are tons of proofs that this is not true, even when this hurts.

But enough, in fact I do not have to proof anything really, I am here to have fun.

One day your ship comes in - but you're at the airport.

iloco, thefixer and others.

I am very sorry you are having such a hard time with all of this. I suppose complaining on these forums helps you feel better about it. I know when I'm having a hard time with something, I like to be able to talk to others about it as well.

I am not trying to be snide, but, saying the exact same things over and over won't get the problems fixed any faster. I suppose if something was causing me to generate so many negative posts in a single thread, I would consider going back to Vue5.

On a more positive note, there's a great thread Pam's (forester) got going over at Cornucopia on modelling. She's talking about creating chairs. There's certainly something there to learn for everyone. Below are a couple of quickies I've created in Vue. The one on the left is created only from 2 letter 'h's and 3 _'s (underlines). The one on the right (aluminum one) is created from an upside down letter 4 with boolean cube subtractions for the legs, and a single underline.

Sometimes it's pretty cool what one can do in Vue with the text editor alone!

 

Sorry, forgot that all the knights in my scenes are M3s with high res skin materials. Henry if someone wants to know in more detail.

Thefixer, maybe we can find a better place to discuss Poser import specific issues, this here is a general thread about Vue 6 Final update.

One day your ship comes in - but you're at the airport.

I wasn't asking you to "prove" anything Wabe, I merely asked you for some help in understanding why you can do that and others here can't, clearly you're not willing to do that!

I'll ask again, can you supply us with your computer specs to see if that is maybe the reason, do you have more RAM than most for instance, do you run a MAC instead of a pc, anything that might give a clue where the problems are!

I'm sure I'd rather be having fun with Vue6Inf as well instead of coming here!!

Injustice will be avenged.
Cofiwch Dryweryn.

I got a feeling wabe is on a power mac with lots of ram and now we either have to upgrade to use vue 6 or get out the ball park.
 Something is happening that I can't understand but FOR THOSE WHO CAN NOT READ I have problems that I dind't ahve in the  prerelease next to the final one in Vue 6 beta and Vue 5 INf.
 Is it to hard to understand that.   Yes call me a liar if you like but at least I know what I have and have had.   Simple to those who don't kow or want to understand and help us who are having problems.

Chipp I do know there is more to Vue than Just using poser items.  If vue is not suppose to use poser models then why add it as part of the advertised product.  I do my thing and dont try and tell you how to yours when using vue.  I am just having problems trying to do my thing. :)

ïÏøçö

Its a thread about vue 6 final release alright and isnt importing poser pz3 and working with them part of what Vue is all about.
 Why some think not I don't understand.    Even the pic wabe posted had poser images in it to prove his worked so why isn't it about  vue and poser working as its supposed to be designed to work as it does for some and not  others.

I heard all this when vue 4.5 had a bad meory leak and everyone said we had a problem and they didnt.  Well it turned out there was a big memory leak and then no one had much to say. :)

When tech says its a problem then do you believe them.............Must not as I see it. :(

ïÏøçö

It is understandable why problems arise. You have three layers in a system: (this is very simplified, and it is far more complex)

 

1. The software layer which makes a request to the Operating system. The Software is the Guest of the System.
2. The Operating System, which controls and processes all of the software requests and then sends them on to the Hardware. The Operating System is the Boss.
3. The Hardware layer is the slave of the system, and does what it is told to do by the OS and just returns stuff back to the Operating System, or/and the Software.

Software is written based on the most current code, which has a lot of Libraries, and so on, to support all of the requests that must be sent to the OS and Hardware. Unfortunately all of this is changing from month to month. Think about it Microsoft adds new updates each month, and that is not just to the operating system but also to the SDK’s. New drivers must be written and old one’s made compatible with the new code, but sometimes they do not work and break a system. The Software gets caught in between all of these changes and must adapt, by writing new code that makes the software work.

 

My AMD won’t process MMX instructions according to the way Intel dictates, so some software packages that support MMX will not run on my computer. However, newer software versions will, since patches have been created to solve the problem.  

 

My supposition; So Vue puts out a beta based on the current code that supports the current OS. Someone says that does now work on my system, so Vue goes back and rewrites the code. Now they put out a new release and it breaks more systems. It happens because sometimes you cannot write enough code to make all systems work together at the same time and include the new changes. So you have to keep trying to patch the software until you can get everything working for everyone. Unfortunately that takes a lot of time.

 

All e-On can do is try to gather all of the information about all of the problems and different system configurations and keep writing code until they get it right. 

 

I am back to Vue 5 until all of this gets sorted out. 

jankeen.com

Very reasnable reply and with using a lot of comman sense in writing the reply so that anyone that wants to understand it can in simple terms.   This is the kind of replys we need instead of it works for me so whats your problem.
 At least a few people know what is going on and understands us who are having problems.
Very refreshing to read your reply keenart.
  It gives me a little relief that there may be a chance we may get somehting fixed that is working for some but not others. :)

ïÏøçö