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

 I am constantly sending them reports if I think its a bug or a problem and they have worked great with me on every ticket I have sent.

So maybe this will help a few see we do have problems and that tech is working as hard as they can to get us going again like with Vue 5 inf and hopefuly better.

All dont use vue the same so please when you don't understand our problems don't say we dont have any. :)

QUOTE From Tech:  Hi William,

We have finally managed to get some big Poser object installers, so this is ok, we have some material for testing now. You therefore don't have to upload the objects.

In the mean time, we have fixed an important (and probably the most tricky so far!) memory leak regarding textures bitmaps. Now, using the big ship model for testing, there is no need to manually purge memory anymore after deleting objects to get memory back, as expected.

Still, it's possible that some problems specific to Poser import remain, so we'll continue our tests with the objects we got today. However, the fix we made about textures will also help for Poser, as the latter tends to use very big textures.

Best regards.
John Canver

Link to the ticket is attached.

56 views and no comments.  Thats good. :)

An Update from Tech in the same ticket.

UPDATE QUOTE: 

<pre class="WMmessagebody">
The e-on software support technician responded:<br></br>Hi William,<br></br><br></br><br></br><br></br>After analyzing further, it appears that the leak mentioned by John is <br></br>relatively minor and a problem that has existed since Vue 4 Professional. This <br></br>is obviously not the cause for the big difference in behavior between Vue 6 <br></br>pre-release and Vue 6 final that you have identified.<br></br><br></br><br></br><br></br>Initial tests with the objects that users have provided seem to indicate that <br></br>the cause for the problems with Poser imports may well be connected with the new <br></br>Poser 7 SDK that we are using in the final release (whereas the pre-release used <br></br>the Poser 6 SDK). We are working with e-frontier to confirm the problem. We hope <br></br>to have more information for you soon.<br></br>

Good work.  Vue is growing in power,so we can all make our masterpieces.

So, after all, it appears the problem might be a Poser software bug, and not one of e-on's creation. Incorporating a whole new Poser API is certainly cause for a few bugs.

This problem is not only with poser models but obj models from Renderosity .  So it may be more than the one issue with vue. :)

iloco,

Thanks for posting your correspondence with Tech support. I'm sure your finding out about the Poser 7 api helps others better understand what's going on.

Ok here is something to think about.  What about all the peole who dont have poser 7 and use poser 6 or even 5.
 A lot refused to upgrade to poser 7.  

I have to say Im liking the new fix for V6I. Im doing a new pic that has 12 poser objects, 5 lights, various terrains and misc objects - and in designing it, no crashes. Im rendering it to disk with GI at 9x11 @300 dpi and it took 2 1/2 hours. And yes there is still some memory leaks but its working (for me) WAY better than either the prefinal prelease or the final release.
That said I remember designing a pic in V5I (Sirens - in my gallery) that had 3 medusa ships, 3 poser figures and various misc objects with no problems. So V6I is not anywhere near the power of V6I.
However, I have a quad processor, 16 gigs of Ram and a 1 gig video card, so perhaps memory leakage doesn't really affect me as much as others.

I envy you but I am one those who dont have the cash to buy a new system with every new upgrade.
   You are probly right with not having issues as some of us are..
The specs for Vue are as follows at e-on site for those who want to buy vue.

SPECS:  Macintosh

• Mac OS X v10.3+,
• 2GHz PowerPC or Intel processor or faster,
• 1GB of free RAM (2GB recommended),
• 200 MB of free Hard Disk space,
• 1024x768 in 65K colors/16 bits (24+ bits recommended).

Windows- Windows 2000/XP/XP64/Vista,

• 2GHz Pentium III or better processor,
• 1GB of free RAM (2GB recommended),
• 200 MB of free Hard Disk space,
• 1024x768 in 65K colors/16 bits (24+ bits recommended

If the specs are as they are stated we dont need a system as high powered to work with vue.
  I'd love to have your system but I dont work due to some health problems and have to watch how I spend my money.  

iloco, I agree that my system is not the norm, but even MY system was crashing like crazy with the final release.  So in comparison, the latest release for me seems the most stable.

I just bought the Medusa ship -  50% off at DAZ.  Their madness sale is causing me to go broke!  Two other really great models that I already have - mideval tavern and Stonemasons backstreets are also 50% off.  If you follow Dystopia stuff, Feng's noodle shop was released this week.  Going to give Poser a spin tonight and get the ship ready to sail into vue!

16GB???  Dang, here I was dreaming of the day I upgrade to 4GB.   

Thanks 
I appreciate your feedback about a problem i also meet

Quote - Ok here is something to think about.  What about all the peole who dont have poser 7 and use poser 6 or even 5.
 A lot refused to upgrade to poser 7.  

iloco,
My guess is the Poser 7 api encapsulates all of the different Poser versions. I can't imagine it wouldn't. So, eventually, when they get it fixed, it will work for whatever Poser version you have.

best, Chipp

Quote - 16GB???  Dang, here I was dreaming of the day I upgrade to 4GB.   

Me, too! I'm using 2Gb and 1Gb machines, and test on another 768 Mb one as well.

Quote -

After analyzing further, it appears that the leak mentioned by John is 
relatively minor and a problem that has existed since Vue 4 Professional.

Hmm, memory leaks since version 4 and still not corrected. Hmmmm, I'm not sure what to think of that! A known bug being left in, and what about the effect of numerous little bugs that may have been left in? I think this proves that Vue hasn't gone through a complete rewrite as touted by some!

Still at least they are working on it...oh and I'm using Poser 6 and having resource issues, so I don't think it's completely a Poser 7 issue.

Cheers

Quote - Still at least they are working on it...oh and I'm using Poser 6 and having resource issues, so I don't think it's completely a Poser 7 issue.

The Poser 7 SDK probably encapsulates all versions of Poser. So, it would be consistent with having problems in Poser 6 as well as Poser 7. IOW, if the api is broke for Poser 7, it could similarly be broke for Poser 6.

Peggy_Walters, the real test is hopw many Medusa ships can you pit in your scene.

Have you noticed that none of the bump maps come in?

Ah got the  bump maps in.  I loaded the non Medusa P6 by mistake.

Something about the Medusa ship - she sunk my Vue.  It imports, but after a minute or 2, boom - OOM.  The Golden Hind (both made by the same person), which is just as much of a resource hog works fine.  Go figure...  Even if I create the vob in Vue 5I, it still crashes Vue 6I.  Don't know what it is.   I'll look at it some more tomorrow - getting late.

Peggy do you have the Aurore)faveral)?  If so try that one as well if you would please.  I tried that one this AM - & Vue crashed to desktop with recources at 37%.

Thanks :)

Don't have that one - I have the Golden Hind and the Warroak Kit.  Both of them work fine.  I have a bunch of Stonemason stuff - they all import fine and have more polygons and texture maps too.  I think something it weird with the ship models, but I haven't a clue as to what it could be.  Also ran into problems with Feng's Noodle Shop and not having it import the walls. 

I had the same with the noodle shop - there is a thread here about it( I reported to teech support).  The Noodle shop is a prop - IIRC a lot having trouble with props not importing.  I'll try some Stonemason stuff & see what happens on my end.

When you say "working" does this mean no resource drop? Or just coming in with all part attached - I have those ships as well that you mentioned.

Golden Hind comes in fine with all parts and not too much of a resource drop - normal amount for the size of the model and maps.  I'm able to move it and render with no problems (although did not try a high res render, just play).  I can ungroup it too with not OOMs.  Even works on my computer with only 1GB of memory.  

Stats:

Warrock Kit - Import  = 59% res. drop - delete & purge res. recovery only to 67%

Golden Hind - Import = 58% res. drop - delete & Purge res. recovery only to 61%

StoneMason backstreets = 68% res. drop - Delete & Purge res. recovery only to 75%

Stonemason Urban Sprawl = 64% res. drop - Delete & Purge res. recovery only to 72%

Stonemason Warehouse District = 78% res. drop - Delete & purge recovery only to 81%

This was done one at a time - closing & reopening Vue - res. started at 93%

Something is amiss. I can't recover squat during a purge - I should be able to purge & recover back to close to 85-89% as in the past. Aside of the other obvious issues :)  I did have collapse identical mats checked - with one undo - all other setting reduced to minimal.

Puter stats:

Win XP Pro(sp2)
4g of ram(tech has mine set to use 3g for apps) and yes it does work before any ?'s start
66G of free HD space
Nvidia 6800 Ultra
Only thing in background is PC-Cillan which uses little space

What setting do you have for the undo/redo?  I have mine set to 1.  There is also another button on the File Options page to flush history.  That helps me get back a few percentage, not really enough to make a difference.  After all my flush, purge, etc, I get back most, but not all -  about 10% of my start resource level can not be recovered.   Why some models suck it down to OOM levels and can not be recovered from is what bothers me.

Hi Peggy :)

I have undo set to 1 - I vary between 1 and zero(depending on what I'm doing - scene wise) - I would leave at zero but I have a bad tendency to move my camera in bad ways LOL.  Flush history does nothing for me whatsoever :(

I guess my point in the above post is not so much sucking of intial resources(which is horrible compared to prior versions and needs to be fixed) but the fact once you delete said item you can't purge back even close to an empty scene - even thought the scene is in fact empty :blink:  See my point? Aside of that imagine loading any of the above items(tons of others with same affect) & wanting to do a COMPLETE pic - would not be possible under these conditions.  Add a few peeps & your toast.

I've posted this several times but have yet to get explanation - so maybe you can help me out here.....Why when I convert something to .vob does the file file size triple(in some cases plus) in size?  I thought converting to .vob made things lighter on Vues system. So, by surmising - converting to .vob is not a good a thing at this point.  I don't get it :blushing:

Debby, file size does not have much to do with accuracy of the model. Maybe you do a comparison of the different formats of  pixel images. BMP versus jpg, versus tif versus ... You see the same content with VERY different file sizes. And all behave in Photoshop or Paintshop Pro the same. I think this is simply the case here too.

Thanks - I was just stunned to see the size get so huge:blink: I was thinking no wonder Vue is/was having a problem - I almost reported as a potential bug!