Forum: Vue


Subject: The "memory" issue [Again!]

thefixer opened this issue on Jul 15, 2007 · 46 posts


agiel posted Thu, 19 July 2007 at 12:02 PM

Jugoth - let's see...

Vue was one possibly the first third party programs to feature Poser import. This was the main reason why I switched from Bryce to Vue around the time of Vue 4. I don't know of any other software who had that level of integration at the time.

In your list of software who can handle large Poser scenes (excluding Poser since it is their own content), neither Bryce or Carrara are using the Poser SDK to import Poser content. That integration is not easy to accomplish but eventually it will allow to do much more than alternatives (such as using the poser shaders).

Ok... so Vue has bugs.. so does 99.9% of complex software written over a long period of time. Not every company has the funding and the capacity to promise a software for years and deliver it when it is completely ready (how long have we heard about terragen 2 for example ?).

Memory leaks are not like plumbing. In modern software, you can't always trace back every possible interactions between components and find the source of a leak. Leaks have to be proven, with repeatable situations and extensive testing to even be sure where they happen in the first place. 

Looking at the gallery, it seems to me people are doing quite well with such an 'atrocious' software :) Maybe I am missing something...

You could say I am defending Vue again. I could reply I am doing my job as a mod to bring some perspective to extreme views. I will repeat it again, e-on is not my pay master and I do not have a direct phone line to let them know each time I do my job here.