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

I see now its trying to run from a backup of some sorts which is not working on my computer.  What in the world is going on. :(

Helmut hit the nail on the head with his pic he posted. :)

Yes I am mad and frustrated to say the least. :(

Was able to load same ship in Vue 5 inf 10 times and it got sluggish and slow but proably could still loaded another if wanted to wait around.    This is just not right. :(

Yes I did report to tech support..
http://www.e-onsoftware.com/support/ShowMessage.php?id=1174410267

If IBL is using this version to make another Pirates of the Carribean we may never get to see it. :(
 Gheez what a mess.

How sad.  I'll install later tonight and see how the update works on my system.

However, I do like th idea of posting problems about vue in the galleries.  I posted this one on C3D because they sold me a lame Sequoia tree model.  The maker of the tree hides in the shadows refusing to tell us if the tree will ever be updated.

66 views and only one comment.  Shows me lots read but don't want to say anything. :)

Actually... it's just me reloading the same page 60 times to make it look like someone is reading :)

...

Just kidding.

Maybe most people don't have much to add to the theme of Vue updates. I don't have much to add myself other than keep reporting issues to e-on and be patient.

There isn't much else to do about it really.

Just a quick chance to test the update - after loading the Golden Hind, moving it, deleting it, I have exactly the same results as for the last update.  I loose about 8% of resources that can not be gained back.  Will play/test more tonight.

lol .........@agiel.
 Ya you are right agiel not anymore to say as I sit here with steam coming out my swelled up head. :)  Glad I am behind a monitor. :)
I been trying to be patience for 6 months now and its been in testing for I'd  guess a year or maybe longer. :)

My last comment on it because just blowing in the wind if say anymore. :(

agiel.........Thanks for confirming what I posted. :)

Hi Iloco,

I too find Vue6inf more (much more) sluggish than V5inf for the same scenes...
Now, I have observed the BIG difference (on my system) is that the two sliders of the display options do not work in V6 as they did in V5: instant draw and background draw.

In V6 the display of meshes is always to maxi even if both sliders are set to the left on mini.
The primitive meshes are reduced in 3d views but not the imported meshes.

You can make this experiment:
In V5 , set the display options to wireframe, and put both sliders to minimum
create a 512x512 terrain (classic)
and bake it to polygons, pushing the baking slider to maxi.

Save the scene and open it in V6 (wireframe mode too and both drawing quality sliders to minimum)
do you see any difference?
I do... in V5 I can barely distinguish the terrain whereas in V6 the terrain is a big red block.
I signaled a couple of times this behaviour to tech support but in the last update it is still the same.

The thing that would be interesting to know is if it was any different with the "good" prerelease.
Maybe I'm wrong but this could be a lead...

Feel the same. I did not even download the latest patch. Just wait and calculate alternative solutions (Cinema 4D etc.) and hope I see some positive replies. Come on, it can't be that bad, can it? 

Cheers

Thanks Polax for your suggestion and I will surely try but will it have any effects on importing poser models and objs saved as vobs that eat up all reosurces when loading in vue 6.  Vue 5 inf does not  have that problem.
  This release has more of a problem for me than the previous one that I thsought was bad. :)

I just cant get my point across it is nowhere near how Vue 5 inf handles poser and other type models saved as vobs.     Its suppose to be a far better software than the ones we are leaving behind but I don't see it anywhere near that yet.  Will we ever........??

btw it is nice to talk with someone who is trying to help solve problems instead of it works for me so should for you and you got an operating system problem.  Why then does Vue 5 inf work so well.....?

http://www.e-onsoftware.com/resources/ShowUpdates.php?ProductTypeID=48

Note at the bottom of the page:

Known Issues- Poser import still doesn't work right (abnormal resource depletion, conversion errors). We are working this out with e-frontier. Thank you for your patience.

That's about Poser ONLY - since I'm at work - can't test obj/3ds/lwo etc et.

Polax sounds like you might have hit on something there :)

Loaded update, brought in what is now my Poser test file and resources dropped like a stone to 8%, I was also watching them go in the Task manager, like a clock counting down, got the resource warning, purged and resource came back up, yada, yada!!

Net Result: No change to previous update as far as poser import goes, ticket raised and answered inside 10 minutes, now that's a record and shows they were waiting for it!!

polax you are absoluty correct in your test between Vue 5 and Vue 6.   Where do you have your sliders set in vue 6 for those two sliders.    Curious.....?

I notice that vue 6 is very sluggish with that saved scene where as vue 5 isnt.   Strange that tech hasnt tryed to fix this. :(

My ticket hasnt been answered......

Personaly I don't beleive all this is a poser problem.   Playing with the experment that Polax gave has showed me there is a problem in Vue 6 thats not in Vue 5. :)  Really Interesting.

@ Iloco: Both sliders 'Instant draw' and 'Background draw' in Files /options/display options/ 3d view display quality          are set to the left at minimum position  in both versions.

Certainly it is not the only problem, but I believe it can add significantly to the difficulty of using Poser imports (or vobs made of them)  because the problem apparently only applies to meshes not primitives.
And Poser objects are meshes.
In the experiment suggested, you can replace the baked terrain by a Vicky (or Mike..) figure
On some systems, the resources can be eaten up because of this display thing, depending on the strength of the GPU. With older video boards, the CPU would inherits of the overload, eating resources.

But the ideal, as I said above, would be to find out if  the good prerelease exhibited already this strange behaviour.

Yes I do understand you and see you are correct I think in you assement of it.

What I  meant for the sliders is where do you normaly set them to work in vue 6 when making a picture.    I have my display options set to opengl hardware and the Instant Draw to about 75% to the left toward Better.   Background draw is about 85% to the left toward Better.

Curious how you set yours for normal use in Vue 6
 

Iloco, I never use OpenGL !
I am used to Wireframe...it is an old habit from using really low specs computers :) :)
 and the settings I use are almost the same as yours. Depending on the complexity of the scene, I sometimes reduce the Instant display quality and even disable Background draw.

Thanks. 
I have been using opengl every since we got it to work in Vue 4.5.  I guess its how one gets use to his working in vue.   I can see your point for how you use display options. :)
 My eyes are not what they use to be and with opengl I can see the things I am working with much better. :)

A few observations about what's happening.

I did a clean reinstall of Vue 6 Infinite and re-built all my collections - the good news is that I do not have my crash on file browser popup anymore and i can finally do some tests.

I loaded the NeonChrome scene from the Lighting Challenge at CGTalk - a 26 Mb obj file.
Everything was smooth working with that scene - the obj file is untextured :)

Then I loaded a scene I worked on last winter (The Wake) and I noticed the same resource problem that was reported.

After loading the scene, Vue immediately reported that my system resources had dropped below 25% and was switching in Degraded mode.

However, I have 3Gb of RAM, which allows Vue to benefit from the 2Gb available per application on a 32 bits system. The thread used by Vue was taking 900M of RAM at that point ... which to me, means around 55% of available resources .... far above the 10% reported by Vue.

So, after playing with it, I am getting the sense that maybe the problem comes from the was Vue calculates available resources.

I will report that to the techs.

Good deal agiel. 
Maybe we all work together instead of how it has been we can get a lot of things fixed that might help everyone. :)

I also noticed that when I load the same scene in Vue 6 in wireframe mode, Vue reports 49% of resources available instead of dropping down to 10% immediately.

That could also point the finger towards something in openGL previews.
The same scene opened in Vue 5 Infinite gives me :

• 29% of available resources in OpenGL mode (instead of 10% in Vue6)
• 58% of available resources in Wireframe mode (instead of 49% in Vue 6)

I checked that issue with Instant / Background Draw sliders as well - they definitely are not behaving the same way they do in Vue 5.

Both issues have been reported officially.

bet you it's related to texture maps, and OPENGL memory leaks.
and maybe compression routines.

BINGO
tested complex model 680k polys.
loaded normal around 63%

saved uncompressed, only 1 procedural material, instead of 50 odd materials, none of which had a texture map over 512x512 and only 8 to 10 texture maps in total , iirc . I take one texture map, but alter colours mix distribution etc,to give multiple materials,  so only resources for 8 to 10  x 512  texture maps should be used, which is nto very much at all

loaded this version in at 89%
2 gig machine. I had turned off OPERNGL it's just on wireframe.
So, it's not just OPENGL, it's wya Vue is handlign texture maps and maybe materials in general.
possibly also compression routines. but I haven't tested that to be sure too tired and sick.

Polax (and everyone else) - thanks for reporting the slider issue - I thought it was just me that was doing something wrong to have them not working.

The reason I haven't contributed to this thread is mostly because I feel both really really lucky, and really really dumb.

I just rendered a scene at 3600 x 2400 consisting of over 3 billion polygons. Yes, that is accurate. Will have to take a screenie. I also used AO in the scene.

I haven't tried anything with the ships, as I don't think I have them, but I feel I am really lucky with VUE 6 in some ways.

Granted, I get my own weird bugs. For example, if you chance the softness of the sun from 0 to something, then right click on the light settings button without tabbing out, it crashes everytime. If I tab out first, then it's fine. Weird huh?

I run a 32 bit system, average system, so not sure why I don't get a lot of the issues other get. I just wish I could figure out the issues I do get that nobody else seems to.

I put my money on Agiel. He is THE voice. E-on will tremble before him.

Warangel: Interesting, can I ask you if you import heavy Poser scenes or not?
If you do, do you leave them as Poser obj's or convert them?
Do you use the Poser Shader Tree when importing?
TIA!

Please lets not let this thread be one those where mine works so yours should also.
  4-5 people in this thread have confirmed there are problems and  tech support has confirmed there are problems.

Instead of havng a thread it works for me when it dont for others lets do as we been doing in previous comments and see if we can find the problems as Polax gave a good test to see there is a big difference between Vue 5 and Vue 6 display settings and how they effect Vue 6.  
agiel also is onto something that might help us.
Who would have ever thought to run that test that polax mentioned.   I know I wouldnt have. :)

Lets stay on topic if we can. :)

I have my suspicions that the Shader Tree could be causing issues too, which is why I'm asking!

I just want to add my two cents and also see if anyone else has had this problem. When I installed the new update and then imported a Poser model, I was unable to move the model using the mouse in the Top Window only all the other windows worked fine and I was able to move objects in this window before installing the update. Anyway I did post a ticket on e-on's website so hopefully it will reach a technician and get resolved.

Do you mean to use a pz3 file or a saved poser file that is a vob.
 Mine works using a saved poser model as a vob. :)

Warangel - after viewing your gallery I can see the scenes you make are quite simplistic(no offense) very few Poser imports etc etc is what I mean by that :) Some are even just 1 character(portraits) - No wonder you don't have any problems :blink:

If you are doing more complex images please do share here so we can see exactly what you are doing :)  Also please share your settings in options in Vue so we can compare to what we are using, in addition - your computer specs would useful for comparison purposes.

Also - are you using PZ3/3ds/obj/LWO/shd for importing purposes...are you eco'ing/painting anything...are you copy/pasting? All this info would be useful so we all can mimic your results & post to EON tech support :)

"Purge memory" seems broken.

Polax has shown the sliders for Display Options are broken

I've shown the fault we're mostly all having is related to materials. Something is really screwing up materials, probably based on texture maps. They are using vastly more memory than they should.
50 materials, lot procedural, rest all using the SAME few 512x512 or 256x256 texture maps, should not drop resources by 25% more, on a 2 gig machine!

Now here's another strange one, the Purge memory is working ok for me with the latest update, if it weren't I couldn't do my "test scene".
Bring in Test scene, resources down to 8%, purge mem, resource back up to about 65%
Beats the shit out of me!!!!

You know, I really wish I could have my money back. Certainly could have spent it better, atleast until they get this mess fixed. It is just amazing that e-on would release such a buggy product. You would think they would care about image!!
 I agree with silverblade, a major issue is here with the way V6I reads texture maps. Seems Any sizable model imported with high texture maps really slows it down, and not just pz3's. Pz3's import for me fine for the most part, no weird texture or geometry issues. Some do take a bit to load and some will just crash it immediatly (but will open in V5I). Using multy models in scenes will for the most part, make things so sluggish its not even worth the effort. In my  mind its, not really an issue with poser, take your pick, 5,6 or 7 versions. Its an issue with V6I.

Polax I did the same test in vue 4.5 Pro and got about the same results I got in Vue 5 inf.  So it does look like vue 6 inf is off par compared to earlier versions. :)  Very Interesting results you have found.

Just received an answer from tech support:

//////////////////////////
Hi Paul,

We have fixed this problem, instant draw will be properly degraded according to quality slider, like before. thank you very much for your report.

Best regards.
John Canver
////////////////////////

sure good news! :)
When they finally adress the Poser specific problem they are working on, we might see a better Vue ;)

Great News................Thanks. :)

XLT news Polax - Outstanding work on your part for finding the issue :)