Hey all. I'm working with Vue for 2 years now. But only with the d'Esprit line. One week ago I orderd the Professional. Yesterday it came. And I installed it. But than it happend. The Vue 4 Prof is crashing so often ... it doesn't matter what i'm doing. My longest working time was 5 Minutes before it chashed.... I'm really angry ... what is the Problem ? I have the newest update ... and the Vue d'Espri is still working fine .... Does anyone has an idea ? thx a lot My Comoputer: Intel 3,0@3,3 NV FX5900 Ultra 1 GB RAM Win XP

First idea is that you are overclocking your processor ...

Have you tried to switch off OpenGL for a test? Maybe Vue don't like your Graphic card or driver for it. Here in the Backroom there is a thread with a list of "good" graphic cards - maybe you have a look there too!

Also, you haven't installed the new SP-2 for XP have you? There are some -bad- issues and alterations with this puppy, including imposing stack limitations and altering how installers and programs can function (MS seems to be securing your computer against everything...including you). And which chip is that being OC'ed? Some of the P4 steppings get...rather unstable....when they get pushed.

I read somewhere that when using OpenGL make sure you not overclocking your graphics card as it becomes unstable very quickly .. even if using only the utilities supplied by the manufacturers. As the graphics cards are not being used in the normal way they are more prone to errors that do not show up on a normal 3D benchmark conditions.

Neverfinder Where did you buy your version of Vue Pro ? Did you install the same copy on multiple machines on a local network ? You should report this issue to e-on's support. A few people have reported similar issues, but their behavior cast a doubt on the legitimacy of their copy. Vue Pro has a copy protection mechanism that WILL make a copy crash without warning after about 5 mins. It is very well possible that your configuration has something that triggers this mechanism. The problem is, the couple of people who reported the same issue did not want to cooperate with e-on to track down the problem. Maybe you will be more lucky than them and be able to put e-on on the right track.

I found (on a mac.. but that may not matter) that if you install Vue when another version has been there (demo, D' going to Pro, etc) that it sets off the stupid copy protection!! Now this is only a guess but... I wiped my hard drive once, didn't fix it... wiped the drive with overwrite (have the computer write 1's and 0's over it to distroy any info on there) you install the new version and it seems to work, well better.. (though i have to say... nor one crash in the last month or so) I'm guessing again but there might be a "hidden" file somewhere with the serial #'s for E-ons stuff... and they get all cunfused, so it thinks it's a stolen copy.... make since? I suggestion.. back up everything, wipe drive, reinstall system, install Vue... bet it works :) (hey think on the bright side, it's making you back up which you shopuld do anyway and reinstalling like that will defrag your drive, and it'll get rid of any "bloat/spy" ware you may have and not know it :)

You're on the right track. However, with Vue Pro, there are no hidden files, nor are their any registry entries (except the path to the program) (unlike Vue 4). The files that are used for verification (in Windows) are vuepro.reg located in C:/windows, and Vue4Pro.eon, located in the program folder. Like thomllama suggested, "if" you have a legitimate copy, completely uninstalling the program, deleting the vuepro.reg file and removing the entire install folder (you can move your objects, materials, and other add-ons to another folder, then move back after re-install), and then doing a reinstall of the program will usually solve your crashing problem. Every time you open Vue Pro, Vue4Pro.eon checks your vuepro.reg file for any invalid serial numbers and if it finds one, it will trigger the crashes. It's also possible that you made a typo when entering the serial and the program is not recognizing it as valid. (you can open vuepro.reg in notepad to verify). I've also found that sometimes you can simply delete the vuepro.reg file, and when you attempt to open Vue again, it will ask for the serial number and once you enter the correct one, it will make a new vuepro.reg file. Hope this helps.

Make sure you go to e-on's site and get the latest updates. Actually I found 4.53 to be the most stable of the bunch. Had some issues with 4.54, so went back to 4.53 when I reinstalled.

I agree with ShadowWind, I have also stuck with 4.53 as it has not given me any problems since updating, to quote an old saying, "if it isn't broken, don't fix it", why update to 4.54 if 4.53 works just fine.

sirrick, Wish I had known about VuePro.reg earlier. Wouldn't have had to bug e-on to get my serial number back when I lost the registration card like an idiot. Learn something new everyday. ShadowWind

One note on Windows XP SP2.. I found out last night that with service pack installed Vue will crash after a while. My problems went away after turning off Windows XP Firewall. It maybe possible that other firewall will cuase Vue problems. Stewart

I'm also running Win XP with XP2 (final RTM) installed, but I have the XP firewall disabled (using Norton Internet Security, and I have eon blocked from accessing the net), and I've experienced no problems with crashing. About the only time the program will crash is when I attempt to import multiple, large pz3 files, basically stressing my system to it's limits (AMD 2200+ running at 2.0Ghz with 1Gb DDR Ram, Nvidia GForce MX 5200). I have open GL and background draw enabled with the default settings. It's a shame that Eon has to build in anti-piracy protection, but I do understand why they have to do so, I just which they'd choose another method as I feel that their current method can cause problems for registered users.

My issue my not be all related to the firewall.. I remmeber at the time I was trying to render a large resolution screen 3000x2250 and Vue ran out of memory.. Oddly enough even after error and reloading the scene in Vue, it still had the memory allocated. It just seem to run fine after turning off the XP Firewall. System is 3.2Ghz P4 with 1Gig of ram with 6800GT card. Before SP2 it ran fined with same configuration.