I do not know if this will work, but this was given to me by Tech:

Go to your account page, towards the bottom of the page is your Order Summary. Click on the text of the appropriate pre-release order and that will take you to the Final down load page. Make sure you un-install the pre-release before you install. Also, save any objects or scenes that you want to keep and add to the final version.   Then download the new Patch and install.

This may or may not work, but is worth a try.

OUCH!!!

If you are going for the "Big Mac," you may be saving for a long time, they are not cheap, $5000 the last I saw. 

More Power!!!  That is an interesting thought, maybe someone will open a thread with a small sample image that we could all render, and see what the times are according to the Systems.

As far as the Tech Support goes, I doubt I will get a second response for a long time.  Usually the first response is within hours, and the second within weeks.

Yeah, been in computers a longtime also. 

Need the Vista, but do agree if you do not need it, wait.

Good info about the auto-update, as too many viruses get downloaded at the same time.  I like to download, put the file in the Temp folder and then run the scanners, just to be sure, before install. 

So with the Mac, how has Vue been behaving?

BAR-CODE

Although I am third generation US, my g-g-grandmother was Dutch; we may be hard headed, but I have never met a stupid dutchman yet!!! Right? 

In most cases the Microsoft basic drivers will work fine with Vue, if you uncheck the test this Video card each each time Vue opens.  The Microsoft drivers, as you say are very basic, and do not use OpenGl higher than 1.1 to 1.2.  The current 7600 drivers I have use OpenGL 2.1, and newer cards higher features.  I was told that OpenGL was actually testing around version 3.  So depending on the quality of your card, the OS, and the drivers you are using you may get mixed reactions with Vue.  

I think all of this will take time to sort out, as NVdia Tech told me they had six years to work on the drivers for WinXP, and that is why they work so well, so they need a llittle more time to work on Vista.

rocco,

I posted before your post.  You might be able to stop Vue from crashing when opening, by right clicking on the Vue.exe file, select Properties on the Menu, then select the tab Compatibility, and checking the Compatibility Mode for Win XP.  Then down on the Dialog also check Run this program as an Administrator.  Vue should stop crashing when you try to open.  

AS far as the memory leaks go, this seems to be caused by rendering.  Whether e-On used the SDK from Poser to write code for some of these higher OpenGl functions or not may be affecting the prog.  Vue will have to resolve these issues along with the video card companies.  

When Rendering I found that under certain conditions Vue stopped using the CPU at maximum efficiency, stopped swapping out to file and immediately started gobbling up the memoy, until there was a crash. Changing driver versions makes a difference, but no settings in Vue made a difference.  This is probably related to the way higher functions of OPenGL address the use of onboard and shared memory.  These issues will have to be worked out by e-On, Poser, and NVidia. 

Right now the only thing that is available to anyone is report all of the issue to tech to both e-On and the Video Card Manufacturers.  Microsoft is getting plenty of info so they do not need to be contacted. 

I have other 3D apps and they do not have the problems under Vista that Vue does.  Most of the problems seem to be Python related.  However, without installing the patch the retail works fine.  

As far as the Nvidia drivers go, Nvidia 97 drivers worked fine on Vista, with the exception of Vue.  However, contacting NVidia and joining the Beta program, they have used the information I have sent them to update the Beta drivers and almost all of the problems that Vue exihibits under x64 Vista are gone.  Again, the major problem with Vue is that you cannot apply permissions or priviledges to the *.eon files, only the exe's and they are nothing but redirects for the shell.

I contacted tech last night and they sent me e-mail that confirmed this patrch is for the Final, and the Pre, which should be uninstalled and the Final installed before installing the patch.  Unfortunately, they did not answer all of my question, can the Retail also use the patch.  So I have resent mail with a better explanation and new question about the patch and Retail.  

Since Subsurface Scattering is the only real problem left with Vue for me, a serious memory leak that locks up Vue and the OS, I will continue to work with NVidia to see if they can change the OpenGL to get Vue to work 100%.  e-On explained to me that the use of Subsurface Sattering uses the highest requirements of OpenGL and is intensely threaded to reduce rendering.  So either NVidia or e-On have a bit of work to do to get this corrected on Vista.  Ironically, I have the same problems when using WinXP, which are different NVidia drivers. 

Otherwise, Vue actually works pretty good, for as intense an app as it now is.  They have really dumped the goodies into this version.  I will keep carrara but doubt I will go back.

Thanks for the tips.  I am running the retail as 32 bit on Vista x64. 

I checked the folder and file permissions and all are Archive. Interesting thing though, the file dates and version numbers of the retail and the contents of the Patch are the same, even though the build is different. That is making me scratch my head since; most of you are saying you patched the download, versus the retail.  

The Vue exe file will load, after setting permissions to Administrator and operating system to WinXp. But, I get crashes, lock-ups and all of the video driver problems I finally got rid of when using the 97 drivers. I do not have all of those problems with the NVidia Beta 158 drivers, so something is amiss.

Guess I will have to ask tech on this one or wait for a patch that says “for retail.” 

Based on the information you have provided, there are two possibilities, provided your graphics card has more than 64 megs of memory;

1. Your motherboard B+ circuit is showing a sign of age, in which case replacing the motherboard is the only solution.
2. The other possibility is the Power Supply itself. It is not uncommon for a power supply to lose viability on a machine that is consistently used for Rendering 3D graphics.

The graphics card should not be the issue, unless Vue is consistently crashing means bad drivers. Otherwise, a general slow down of system and applications usually indicates overheating, damaged CPU, Memory, or lack of an adequate supply of power. The CPU and the OpenGl software coupled with the memory and sometimes swapping out to disk are the main source of Rendering. The graphics card simply displays the results of the Render to screen, but does not usually do the Rendering itself.

Therefore I would swap out the power supply first. Find out what wattage your motherboard, CPU, and Graphics card require, i.e. 350 watts, and add an additional 10 to 25% more wattage and get the latest 20 or 24 pin power supply. Which ever pin configuration your motherboard requires? 

If the power supply is not the problem, then it is time to upgrade the board or better yet the system.  

Again, before you try all of the above, I would back up your Vue Materials Folders, and uninstall and reinstall Vue.  In addition Check the Administrators, Events Viewer to see if there are any Errors or warnings concerning sytem or application problems which may be related to the Operating System..

bar-code; do you have the download or the retail version of Esprit!

I have the retail version of Esprit, tried to download the update and install and it corrupted and disabled Vue.  So I reinstalled Vue and have not tried to install the patch since.  I wonder if this patch is for the Download final version only?

A free Memory Test prog you can find at www.memtest86.com takes several hours.  You should let the computer warm up to see if as Victoria says, you are having a heat problem, before testing the memory.  

When booting look to see what the CPU temp is If you have setup info.  Should be 120 and less to 90 F after two hours operation.  150 to 200 is hot, and may cause the computer to lock up.

As Victoria mentions, clean everything, even the Power supply if possible.  If you cannot reach the inside, use compressed canned air with a long soft haired  artist brush.  

For the CPU, get new silicon heat dissipating paste like Artic Circle, the better quality the better heat dissipation. 

If none of the above and defragging the hard drive does not work, then back up your Vue materials folders and then reinstall VUE.

Yes, Thanks, that will save me a bundle.

That is the very same question I would like to know, since I only need the Botanica, which I have and the Eco-system, which I have not purchased yet.  So If I buy the other modules, I wonder if it turns into Pro, if you have them all?

Somehow I doubt it, as there should be a difference in Product Keys.  And when I compared the difference between Esprit with all modules and Pro, there was a price difference.  Also the same for the sidegrades so it seems that e-On wants to keep the two seperate as far as price goes.

So instead of buying the Eco module, I will wait a month of so and buy the sidegrade to Pro, and save a few bucks, and get Infinite next year.  The difference between a sidegrade from Esprit and Infinite is monumental not so bad from Pro to Infinite.  

The other question is do you get credit for the modules you bought with Esprit and then sidegrade to Pro, maybe it works in that capacity. 

It is a bit confusing, but you are not really buying modules, just the license, or Product Key to the module. 

The modules are installed along with the Vue version of the application, in the Folder named Modules; they are just dormant until you click on a module install file. Then you are required to add the Product Key you previously purchased, which is sent to you by e-mail. 

Hope that makes sense.

You would probably be better doing a sidegrade to Studio Pro now, rahter than buy all of the modules seperate, which is a little cheaper down the road.  That would give you a step up, for less money if you wanted to go to Infinite later.