With reference to my earlier post about suspecting the Poser Shader Tree causing the memory issues in Vue6Inf, I received this from John Canver this morning!

**Quote:
***Hi gwyn,

Indeed! We finally unraveled this naughty memory leak, which is linked to the Poser Shader Tree bitmaps, which are never released by the Poser SDK. E-frontier is fixing this issue right now, so we hope to release a fix soon. Thank you very much for your deep testing, this is much appreciated :)

Best regards.
John Canver

*At last some light at the end of the tunnel!!

Great detective work!

Lets keep our fingers crossed  :-)

Thanks for the info thefixer.   I hope it solves our problems with vue and poser models. :)

thefixer - Great stuff, I'm glad your findings regarding the shader tree were true. Fingers crossed we get the fix soon.

This is really odd but seems to be confined to V6i since I don't seem to have the memory leakage problem in V6e when using the Shader Trees.  I'll be posting a new image in just a bit that I did yesterday.  The figures were composed and textured in P7 and then imported into Vue for lighting, environment and rendering.  I'm pretty pleased with it.  I watched my memory and it never dropped below 46% even with the huge shader trees for the two humans.

Like he say's :  Injustice will be avenged.
Otherwise we sent in THE FIXER....

Chris

Victoria: I have seen differing performance levels of different Vue programmes before, I don't know why it happens.

I had Vue5E a while back and it was a bag of spanners for me, couldn't do anything with it if the poly count went above 1.5 million, I was so annoyed I threatened them with our Trading Standards, anyway to cut a long story short we reached a deal on an upgrade to 5Inf to see if that was better and it was, much, much better. Now ask me why it was better on the same machine that Esprit wouldn't work on and I have no idea!!
Fact is 5Inf was brilliant and Esprit wasn't!!!   Beats me!!!

You seem to have a similar issue only reversed happily for you!  :-))

Does this mean large scenes would work better or faster if i upgraded from Vue 6 Esprit to Vue 6 infinite? Large scenes with several million polygons slow down my Vue 6E a lot. I should search my Poser 5 CD, its been ages since i played with Poser. I've never used it much, i must admit i got no idea what the shade tree is and whether its in my Poser 5 or needs a newer version.

**No, I'm not saying that at all!

**It was just an example for Victoria of the peculiarities between the differing versions.

It may be that I had a corrupted version of 5E, who knows, it's off my system now anyway!

If you're using millions of polys anyway then that was something my 5E wouldn't do so the issue isn't the same.

I don't even know if 6E uses the shader tree, I'm not familiar with that version of Vue!
:-))

Quote - Does this mean large scenes would work better or faster if i upgraded from Vue 6 Esprit to Vue 6 infinite? Large scenes with several million polygons slow down my Vue 6E a lot. I should search my Poser 5 CD, its been ages since i played with Poser. I've never used it much, i must admit i got no idea what the shade tree is and whether its in my Poser 5 or needs a newer version.

The image I just posted was a tad under 250 mil polys, 521 objects and 2 lights.  I have the Ecosystem module for V6e and I love it.  I will upgrade to V6i sometime in the future but, for right now, V6e is working just fine.

Gwyn, I know what you mean about V5e - it wouldn't handle large scenes on my system, either.  Thankfully, V6e works much better for me.  I'm happy you found the issue with your memory leakage ... keeping my fingers crossed that e-on gets it all sorted out for you now that they're playing nice with e-Frontier.

Quote - **No, I'm not saying that at all!

**It was just an example for Victoria of the peculiarities between the differing versions.

It may be that I had a corrupted version of 5E, who knows, it's off my system now anyway!

If you're using millions of polys anyway then that was something my 5E wouldn't do so the issue isn't the same.

I don't even know if 6E uses the shader tree, I'm not familiar with that version of Vue!
:-))

Gwyn, 6e uses the shader tree just like 6i ... it just doesn't have the memory leak that 6i does, I guess.  The new image uses the P7 shaders extensively for both the V4 character and the Apollo character and I didn't have an issue with the pz3 coming in or rendering correctly.

Thanx for the info Victoria, appreciated and hopefully now that we know what's causing it, between them they can sort it between them PDQ,  and I can't wait!   ;-))

Ahh, i dont count ecosystems as polygons. I know its basically the same, but the way Vue handles these is different. I am currently rendering test pics of my new plants. The current scene uses only 1 object, a terrain with an ecosystem consisting only of my plant. The scene has over 250 million polygons (!!!) and i can handle and render it fine, a bit slower than an empty scene, but really not "slow". But when i load complex objects as my Vue house with around 2 million polygons, vue gets so slow, its a pain to handle.

I know that sounds strange, but "ecosystem polygons" dont seem to stress my hardware as much as other ones. (Not even close)

*I know that sounds strange, but "ecosystem polygons" dont seem to stress my hardware as much as other ones. (Not even close)

*I have wondered about this for a long time.  A 2 million poly model will cause heartburn for my machine, but I have made solidworks ecosystems with 1.5 billion and they work fine.  Does anyone know the reason for this? 

Sorry about going off the main thread topic.  I am using V5inf. 
XP,AMD Athlon1.8ghz, 512ram, 64meg geforce.

Eco-systems use alpha planes/billboards - they aren't real geometry unless you tell it to use such.