Hi everyone...me again :-) Both on the E-on site and in my manual it says that Vue 4 Pro will save images as PSD files, but I don't have that option in the dropdown box. I checked for updates in case it was a new feature, but it tells me that mine is the newest version. I've also had it crash on me a few times - can't be my system as the computer's only a couple of months old and it's not an illegal copy before anyone mentions the anti-piracy thing ;-) Any help or suggestions on either would be appreicated. Gill

I don't have this possibility either in my drop down list and in fact it is written in the book. As I don't have Photoshop, I did not miss it, but I will immediately write to e-on. As soon as I have an answer, I will come back here. Please be a little patient. Guitta

I"m in the middle of a render, so can't check for you right now, but later I"ll see if I can save a psd file. I don't save images in that format, so have never tried before. As far as crashes, well, I get that too occasionally, but not as much as when it first came out! Could you provide your machine specs? That might help. Also, is it only crashing when you do certain things? I find if I'm tearing through the material editor fast, Pro doesn't care for that and will sometimes hang and crash on me.

Try to disable OpenGL and see if it always crashes after that.

Thanks for all your responses :-) My system is Windoze XP, P4 2.66ghz, 512mb RAM. The RAM is the only thing I'm concerned with as although I used to run my old computer on 64MB (which ran Bryce, Vue and Poser all with very few problems!!) I may well upgrade the RAM on this one to at least double what it is now. A couple of days back it was crashing while rendering to disk so I started it again and rendered to screen instead. It managed it that time. Was rendering on Final at 1152x864 120dpi. I did have a glowing material in there. Previously it's crashed while I was in the plant editor and afterwards when I tried opening it again, it crashed as soon as the programme opened. It does seem very intermittent and doesn't seem connected with anything in particular. I WILL try your suggestion gebe, and disable Open GL. As for the PSD option, I use that when saving out of Bryce as I find it gives the best results, and even in you don't have Photoshop you can still open PSD files in some other programmes (like PSP). I'd be interested to see how this thread spins out. Once again, thanks everyone Gill

I just disabled open GL so will see how it performs over the next few days. One thing that I did notice which is why I'm posting again is that when I used the render in main view option with Open GL enabled the image got all 'jaggified' for want of a better expression but it doesn't with it disabled. I attached a screenshot to show what I mean

Well, after disabling open gl I was about an hour into creating a new scene tonight. Went into the plant editor to reduce the polygon on a rural maple and kerrrrrrrrrrrrash!! Of course, I hadn't got round to saving it so I just lost everything - got to start over :-(

Crashes and lockups -- whenever I do ANY kind of serious animating -- seem to be the order of the day for Vue. It's called Professional, but I don't find things like the constant crashing (or locking up), or massive slowdowns when using the timeline, etc. very professional at all. You're not alone, believe me. If my other software, -- like After Effects, video editing apps, imaging software, etc -- were this unstable, I'd NEVER get anything done. I've gone back to the rock-solid Bryce 5 for the important stuff.

Oh, and did they ever fix the replace object bug anyone?

Thanks,
Tim

Vue's implementation of OpenGL has caused problems with some graphics cards. There's been endless discussion about this in the forum (do a search on OpenGL and see what you come up with!). I was used to working in wireframe with Bryce, so turning off OpenGL in Vue and Vue Pro was no big deal for me, and greatly helped the stability of the proggies on my machine. That said, timoteo1 has a point about saving. I do incremental saves of a scene, with a slightly different name each time. Often when Vue/Pro crashes, it corrupts the scene file. If you have the option checked to make a .bak (backup file) of your file, you can usually reopen it that way. But to save yourself aggravation, best to do fairly constant saves just in case. I also put things in layers, cool in Pro because you can create as many layers as you need. Group items within the layers as well. I have a gig of RAM in my machine, and that has helped me with larger scenes, but I don't know how much it has to do with the stability of the program, other than the point folks make about "you never have enough RAM"!

I have been very quite with my problems with Vue untill reading this thread, I have been having crashes like a lot of other people and without anything in particular that causes it that we have pinpointed at e-ons tech support. My problem with everyone turning off Open Gl tells me if its an Open Gl problem then e-on is the one who needs to find what it is and why it is not working. I paid for that feature and would like to have it to work. Do we all buy one viedo card just for Vue. I have one question...........Why does other appllications that use Open Gl work with out problems and with out having to disable Open Gl or buy a special Viedo Card that is known to work with Open GL. :o)

I don't think that OpenGL is the problem. I now have that feature turned off and it still crashes. I know manufacturers want to protect their software as much as possible but could it be that it's the anti-piracy thing that's causing it? If they've written something in the programme to cause it to crash if it's being used illegally, could there be a problem with this part of the programming that's causing intermittent crashes for bona fide users? If it is then maybe they should look at another way of doing it.

As I have no crashes, it's difficult to speak about. But if you all who have crashes would for a while write down every crash, when, why, what error message. If you could write what exactly you have done before the crash, the size of your scene, the number of polygones, the number of lights and so forth... I could transmit it. Is the crash repeatable or is it just randomly? I really cannot understand, because for most users Vue Pro works without problems. I have it installed on a Pentium IV - 2,8, 1 G RAM, a Radeon 9700 Pro on Windows XP Pro. The only crashes I can reproduce is when my scene becomes over 100 MB big and when I try to add more then 1 object at a time. I need then to save each time, shot down Vue and even the computer to restart and add a new object. This is a memory problem, not a Vu ePro problem. I would then need 2 G Ram.

Well to start with my version of Vue is not illegal or a pirated copy. I am against the anti piracy bit that is put into software as it only hurts the innocent that will pay for the application. A pirate will always be able to get into a piece of software. Always have and always will. You could very well be right that something in the software is causing all our problems for the ones who are having problems. I know Poser 5 took it out because of various reason. I wonder if that is one of them. gebe you were lucky enough to be a beta tester and was able to turn in your errors and crashes to e-on from your computer. What about the many many others that have a different configuration than yours. That is where the problem lies. My problems are random so it is hard to duplicate it when it does happen. That makes it hard when trying to explain to e-on or anyone else. That is reeason I have been quite with my problems and keep hoping that the problem may be found. If my problem would do the same all the time then we might be able to pinpoint my problem. :o) I turned off back ground draw and still get crashes. I will continue to wait for an update that maybe one day will take care my problem. That is the only choice I have it seems...:o)

We beta testers had all different computers graphic cards, OS and so forth. The reason must be somewhere else. Often a simple reinstall helps.

I have reinstalled Vue numerous times before trying to solve my problem. It is the only software on my computer that has been reinstalled numerous times. Yes I went through my registery and made sure it was all taken out. I disable my firewall and virus scan and anything that might been running in back ground during the install. Most all my other software has been installed one time and have not had any problems at all. There is no doubt a problem somewhere with Vue but finding it seems to be the problem and may take a stroke of luck to pin point it. :o)

Oh, BTW I can make Vue crash every few minutes if I want (but only in heavy scenes with many polygones, many objects)in doing the biggest error:-) If I don't wait until Vue has finished the task I just asked for, but ask another task immediately while Vue is working on the previous. And as I don't understand why Vue needs some time to do the task, I just ask it twice or more and then maybe even another one. LOL This may be great with a 4 Giga machine, but not with a 2.8 or less:-) Can this be a reason for your crashes?

I have a 2.5 ghtz Pentium 4 with 1.5 gig of ram using a nivida geforce 2 viedo card with 64 megs of memory that works with all other open gl. I am using windows 2000 with everything in background disabled that can be disabled and my computer operate properly. You may be right and we all need a faster machine with lots more ram. I don't have the answer.....:o( I wish I did so we the ones with problems could work in vue without having so many probems that we should not be having. :o)

I have to Echo iloco's sentiments. Vue crashes at random for no particular reason. I would say it happens more when I'm animating, but I'm ALWAYS animating basically. I have tried turning off the background draw. I have tried disabling OpenGL ... nothing works. Vue sometimes just disappears, or simply stops responding. I use LOTS of other extrememly complex software, and none of it crashes like Vue ... in fact, most of it (if not all) simply does not crash PERIOD. After Effects, Edius, Particle Illusion, 3DS Max, Imaginate ... even POSER! The list goes on. All work OpenGl apps work flawlessly. This happens with the simplest of scenes. I was animating a ball rolling down an incline. I made some changes through the wizard a few times, and on the third change Vue just crashed out of the blue. Just when I'm really liking Vue Pro, it locks up or crashes, and I get this feeling in the pit of my stomach that I've wasted a lot of money and more importantly, my time with E-on products. It's very discouraging. :(

Well, I think that a lot of people experience crash with Vue since the v4.0 May be the antipiracy is one reason. I have been in touch with the e-on support in order to try to solve my crash pb, but how could you describe a problem when you load a file, you do an action it carshs, you reload, do the same action it works? If really the pb could come from the antipiracy code, they should go on the same way than Curious Labs. I agree with Timoteo, it's very frustating, because vue is great soft, but we need to be able to use it on a more reliable way :(

First, I will answer to Gillbrooks' first question..Loading PSD in Vue Pro... In fact, I've lost all my hair trying to save or load a PSD file... I reinstall Vue several time, and don't saw any PSD choice in dropdown menu... But there was the PSD.Eon file, so I thought that it should work... But one day, I didn't care about it anymore... And some time ago, I magically saw that I can save PSD files:) I don't know how it is possible, it is magic:) (the picture prove that is is true)... Finally I always save Vue pics as PSD, it is more convenient... In my experience, I never saw a software that doesn't crash or don't have bugs... With 3ds max, sometime, it is like vue pro, it shuts down. I'm saving a scene, and... it shuts down. I'm moving a point, and... it shutsdown! Sometimes, I think it just want to make a joke. Vue Pro act in a same way. It works fine and sometime it wants to make a joke and it close the scene. Illustrator is sometime very hard to bear too. Sometime you pixelize something, it works fine, and another time you pixelize the same thing in the same condition and it doesn't work... there is artefacts on the pixelized pics, or another good things... Sometimes it crash too, often when the deadline comes;) It seems that pro soft act like that... They have their good points, and sometimes there are unbearable. I generally reach to do what I want, it takes me some times, but I do. With Vue Pro, I'm able to use it normally, and it crash sometimes, but not as often as it seems to occured with some (a lot of;) ) users... I don't think it is the antipiracy system that makes Vue crash... I prefer to think that it is all this thread, background draw thread, render preview thread, etc... Thread is not a good thing;)

Gillbrooks can save psd files too now:-) Guitta

Yes I can and I thank you for that :-)

VuePro still has problems on my machine as well, although after the patches it's settled down to a single issue, though I haven't played around much in the new editors to find the bugs there. I think what you use, and how you use it is a possible reason why some have problems and others don't. Some may not hit that little piece of code that is messing up. Random occurences can be difficult to find, but it's almost always the software, and not the hardware, background tasks, etc, in the end, though software companies would rather pass the buck. Then strangely enough, even though no hardware or habits have changed, but the software surprisingly works after the next update. Hmmm. I think there are some valid complaints here.

As to the Vue Pro crashing, my personal experience is that it is some sort of memory leak in the resource table. One can watch the resource memory shrink down and down and not from adding objects, lights, etc. Eventually the memory gets too low and the system crashes. Now depending on background tasks, the crash can come in various guises. On mine, it seems to kill all the menus until the pointer is over them and makes requesters come up as ghosts. If I save and restart, I can sometimes continue with the requesters working, but the menus are still disappeared until the mouse goes over them. It takes out windows at the same time, since windows has to use the resource table to. Rebooting resets the table, thus it works again until the next incident. While I'm not totally sure, it seems to rush this process when using the undo, which I do alot, being not as young and healthy as I used to. In my latest battle with the bug, I did a couple of undos in order to reset a piece I had moved and that is when it started acting up. It ran fine before that. I have noticed this connection a few times. It doesn't surprise me that this particular bug cannot be duplicated as there are a lot of things that use the resource table, so it could be anything that can trigger taking Vue over the limit. If I were E-on, I would start with the undo. I know they've already done one patch to the Undo system, but maybe there is still more to do. As I've said before, I think VuePro is an excellent program if they can smooth it all out.

The amount of polygons or lights don't seem to have any effect on this, though it may happen quicker in high polygon pics, though it actually seems to do it with less than more.

My machine is a:
P4T Motherboard with P4-1.8Ghz
512 Meg of RAMBUS
ATI AIW 9700 Pro with the latest Catalyst drivers
It's on a 60 gig partition by itself with at least 3 gig of swap space on average (windows controls the space).

It's entirely possible that background tasks that use the resource table as well, would make the crashes more frequent, but it is not those tasks that are killing the table. Any suggestions would be most welcome. I tried shutting off OpenGL, though I winced at the thought of not using a major feature that i bought it for, but shutting it off didn't help anyway.

ShadowWind

ShawdowWind, you have expericed the exact same problems I have but was able to explain better than I. The problem you have just stated is what my problem is also. I have to agree with you and your observation on what is happening even though there will be some that will not agree with us. :o) I am not up on the techical part of how things work but do know when something is not right. I like Vue Pro and what it has to offer. I only wish e-on could find and get the problems squared away for us the users who are using it.

Great point Shadow! I forgot all about that, but I too notice it occurs more often when doing undos. It just now happened with a simple ball object, no lights except sun. I was trying to change a keyframe point. I drug it somewhere and POOF! I restarted Vue and was doing something else fairly basic, hit undo a couple of times and ... CRASH. Also, I recently had to reinstall Vue Pro because it simply refused to launch. I hadn't done anything major to that machine, and had not touched Vue Pro for some time. It just stopped working. Isn't that bizarre? It makes me really start to wonder about the whole anti-piracy scheme. That reminds me of something a program using that technique might do, no? If anyone from E-on is reading this ... why not just remove it with the next patch, so that we can at the VERY LEAST eliminate that as a suspect? PLEASE!

While my heart goes out to my fellow Vue'ers that are having this trouble, I am glad to hear that I am not the only one having this problem. It validates that it is indeed a problem that hopefully gebe can get e-on to look at. Since the undo seems to be a culprit, maybe that will give them enough info for a bug hunt for their next update. I hope so. I would be glad to work with support at e-on to find this bug out and stomp it. While I don't know their code obviously, being a programmer, I have a lot of experience on getting a scenario narrowed down.

Timoeteo,
Could you maybe elaborate on what POOF and CRASH means in your situation. Is it the same as Iloco and I are saying, or is it something different? Just wanting to know so we know whether it's two different bugs or the same one.

Also, it's not bizarre to have a program stop working from one session to the next. This can be caused by a whole lot of scenarios, not the least of which is a byte that was not read properly due to a small glitch in the HD surface, a bad shutdown where memory caches did not write properly to disk, a crash in an earlier session that corrupted a file that is needed to load, etc. I've had several programs over time that have stopped working for no reason. I'm not saying VuePro didn't do it to itself, I have no idea, my point is that it's really not as rare as it should be, that's all.

Antycon,
What operating system are you running? The reason I ask is because before I got win2K, I was constantly battling software and crashes. When I got Win2K, I've had a very stable system that ran that same software without a hitch. 98SE is notorious for it's memory management. Now on XP, I can't say. I bought it when it came out, and installed it, but it had so many bugs and driver issues back then, that I formatted the drive and reinstalled Win2K. I do plan to switch back up to it in the future, but I don't have a reason to as of yet, since Win2K does run fairly stable. The software I run generally has a 1% failure rate during usage (meaning it crashes), but VuePro has a 100% rate, so it's something seriously wrong there that shouldn't be. Yes, all software has bugs, but they are generally not to the point where the software is unusable by some. I dont mind slight annoyances, but downright crashing is serious stuff, especially after the price tag.

ShadowWind

PS: I doubt it's the piracy thing, but if it is, there is obviously a bug there so it's the same difference. It shouldn't be interfering with legal owners, which I am (bought all of my vue stuff, Vue 4, the vegetation pack, Vue Pro directly from e-On) and I am registered there.

gebe, it's possible that could do it too, the clicking on another task before the last one is done, and might even explain the undo, but that is still a bug that needs to be addressed. Most software does this by simply locking out new key commands until the last task is finished, leaving only escape. It's noble that e-on chose to make sure they got keystrokes during tasks, it's not good if it crashes because of that. I do remember your list of how to baby VuePro into being a godo little puppy, and if this was a shareware program, I'd say okay, but a $400-500 program should not have to be babied. Photoshop, Bryce, and others don't espect it, and neither should VUe. In other words, it's not acceptable for the computer to crash because one forgot Rule #13: Creoss fingers and pray while hitting CTRL-Z. :) We want to help e-on find these bugs and stomp them out, so they have a stable product and we have a great experience with the software, without all the hoopla of restarting several times a session, etc. I for one will do whatever e-on needs to help us fix this. SHadowWind

Dang, I should have proofed that before I put it up. Forgive the typos, cold medication is playing havoc with me, not to mention the cold...

Since this keep coming up about problems and crashes with Vue Pro it seems to me there is still lots work to be accomplished for the few that are having problems. I think more are having problems than what is speaking up due to getting a run around or being told it is a problem with them and not Vue Pro. Wake up people and speak up if we are to get these problems fixed. This forum is set up for help with vue and problems it has. When Vue Pro came out and there was so many problems and bugs that we kept this forum busy with complaints e-on said they would lookk into or give us a help forum at their site. That was a long time ago and that forum still hasn't been installed. The help system they have has a lot to be desired with how it works. Why can they not have a forum like this one we are discussing problems in. I think it would help them understand what is going on better than with the system they have now that I quit using because it is a waste of my time and theie time since nothing gets accomplished but questions and more questions.

Poser 4 crashes (freezes completely) very often for me. Vue doesn't:-)

gebe are you saying that Vue Pro does not have any problems. I have never had the crashes with Vue 4 as I have with Vue Pro. This should say something about something is wrong. If anyone can prove or show me it is something other than in the software I will gladly apologize for saying it is in the software and buy what hardware I need to make it operate corrctly on my computer. You have stated many times you have no problem with Vue Pro. Does that mean all other users are suppose to have the same when they install the software. I am just glad you do not have any problems and have to experience what it is we are going through and trying to get fixed. You are most fortunate to have a good working version of Vue Pro. :o) I don't mean any harm with what I am saying only what I see on my end with what is taking place on my computer with Vue Pro. And I see a few others are having the same problem. I would love to see this problem solved because Vue is My favorite software program. I am not knocking Vue or e-on at all. Just would like to be able to help get this problem fixed.

iloco, believe me I'm very sorry for every one who has problems with Vue. And even more sorry not to be a technical to be able to help out. But we are very many who have no problem. Unfortunately only users with problems are posting here in the forum. Those are few in comparaison to the number of selled Vue Pro copies. Of course it should work for everybody, but I believe that it would work on a completely clean machine with nothing running in the background. I must say that I only have Vue2, Vue 3, Vue 4, Vue Pro and Poser on my machine, nothing else, no anti-virus, no Word or anything else. All my other softs are on my old AMD 1G machine. This can be a reason that it works so well. I need and use it for my regular work every day. And I know I'm not one of few lucky ones. Many users are working professionally with it. Just see the spotlight samples on e-on's site. Guitta

I know of two friends that are to shy to post about their problems with Vue Pro. This may be reason that others are not coming forward and just watching us do their talking for them and hoping the problems will get solved and they not have to get involved. I had been that way untill this thread when I decide to speakup about my problem. Why does other software work on a computer that has more software installed than Vue. That doesn't make any sense that Vue needs to be the only program installed so it will work correctly. We could go round and round for ever why yours work and why mine should work correctly but in the end it most likely is a bug in the software or you would not have to run it by itself on another computer with out other software installed. Were all the beta testers just using Vue Pro only on their computers when testing or did they have other software installed other than Vue Pro.

No, but if you install first Vue Pro on a clean machine and use it and then only install other programs it must work:-). And a professional program is worth this work, IMHO.

So after spending months and months getting everything set up on a computer so it works the way we want along comes one program that has to be treated different before it will work. So that is telling us with problems that all our problems are because we need to format our computers and load Vue Pro first after putting a new operating system on our computer so we don't get the errors or crash's we are experiencing now. A professional program should not have to be this way to work. So in the future all software will require it to be installed first before it will work. Am I understanding you correctly.

No way am I reformatting and reinstalling everything. No programme manufacturer should expect that of anyone!

I forgot to mention that about two weeks ago I posted my problem at e-on. I was getting a VuePro.eon error when I got a crash. This doesn't happen all the time with a crash. They confirmed that there was a problem in Vue Pro since it was generating this error, but had to be able to duplicate what I did to cause the error before they could find or fix. I can not duplicate what happened. I only know it happens and is still happening as some of the above replys has stated. So if e-on confirms there is a problem that tells me there is a problem. :o) Finding and fixing it and giving us a new update is what the ones that don't speak up is waitng on as well as what I am waitng on.

:-)

"lol" :o)

I am running both Vue 4.2 and Vue Pro on my machine. Intel 2.6, 1G rambus RAM and a GeForce MX440 video card. Vue 4.2 performs like a champ. I don't have any crash problems with it. However, VuePro has been a disappointment since day one. While i don't crash it a lot (I don't think my scenes are big enough), Open GL is worthless. I can use it for a while, then movement slows down within the program. I feel like I am working in slow motion. Actually, I find that happening even with the Open GL disabled and the background drawing bit disabled. After working for a while, the program slows to a crawl. Then stops. This does sound like memory leak behavior. Actually, I've gotten so frustrated with it, I've pretty much stopped using it and gone back to 4.2 where I'm happy. I do my rendering in Pro, but that's about it. For the money spent on VuePro, I expected quality. That's not what I got

Yes, I get that too, slowing down till it almost stops. I also get icons disappear within the programme, and on odd occasions when I've scrolled down to the Windows taskbar the tooltips appear all black with no writing - I get that with no other programme. I've also tried closing everything else down - just leaving the essentials running but still no improvement.

"Yes, I get that too, slowing down till it almost stops. I also get icons disappear within the programme, and on odd occasions when I've scrolled down to the Windows taskbar the tooltips appear all black with no writing" Yes, that exact same thing happens to me as well. If you right click on the toolbar, the pop-up is blank until you mouse-over it ... and even then it does not "draw" correctly. This would indicate to me some type of resources leak for sure. And it is JUST VUE ... nothing else does this of course. And believe, it is REALLY, REALLY hard to make Win2K (aka "The Earth's Best Operating System) to lose resources and behave badly. -Tim

Oooh, okay so much to cover, so little time. Let's ... BEGIN!

Shadow:

"POOF" = Vue simply vanishes from the desktop. No error ... just gone!

"CRASH" = Vue crashes, popping up a generic error message. Relaunching the program works fine, but it may or may not crash again in the next session. But probably will.

The other common problem, as someone else described, is the gradual slowdown and then grinding to a halt (becomes totally unresponsive) in Vue Pro.

Next to the initial release of Poser 5 ... this is the buggiest piece of crap I have ever had the misfortune of using. I was able to crank out a couple of animations last night (thankfully it doesn't seem to crash during renders!), but it was pot luck getting them setup and took about 5 times as long.

TO BE CONTINUED ...

Iloco:

You are absolutely right ... many people do not speak up about their problems. Or heck, even know about these forums or use them. I have no problem posting about the problems I have with Vue -- as many of you know. ;) But, even I had given up and left this forum for some time.

In any case, I think the problems are much more rampant with Vue Pro than almost any other 3D app, especially among the "professional grade" apps. I wish we could do polls here (among other things).

Guitta: You wrote, "Of course it should work for everybody, but I believe that it would work on a completely clean machine with nothing running in the background."

This begs the question, why other complex software (AE, Bryce, 3DS Max, Edius, Particle Illusion, etc.) NEVER crash or have any of these problems, doesn't it? I really apprecaite your input and help on a lot of issues, but sometimes your objectivity (or lack thereof) is severely impacted your hyper-enthusiam for E-on products. I think Iloco (and others) has more than explained adequately why there is indeed a problem with Vue and not the user or user machine.

In any case, we'll find out soon enough. I have three new machines coming in by next week. I will test this theory on the best of them (P4 3.4GHZ HT, 2 GIG RAM, 240GB RAID 0, RADEON 9800 DDR, etc.) I will be doing a clean install and have nothing on there except the very basics. I will install Vue first, test it, then begin adding my video editing and other apps.

CONTINUED ...

To those with Vue Pro (or Vue 4.2) problems:

I did notice Shadow was running Win2K (like me). Could anyone reading this thread who is experiencing Vue crashes list if they are using WindowsXP or Win2K?

I'm wondering if it is some type of incompatibility with WIN2K. (Again, wish there was a poll function here.)

Also, I'm curious what OS are you running Guitta?

Again, I guess I'll find out when I get my new XP machine. Thanks!

I am glad to see others are speaking up with same problem I am having with Vue Pro. It seems it is the one major problem that is crashing our machines. I am using windows 2000 Pro to answer your question on what Operating system I am using. I hope that e-on will read this thread and see the problems that we are having. Their way of helping on their site I got tired of trying to use. You leave a question they ask a question. It goes on and on and nothing gets accomplished. I would like to see them add a help forum such as this where owners of Vue could ask or answer questions. Guess that will never happen. :o)

I'm using Win XP Home edition

There goes that theory I suppose. I was beginning to believe it after Iloco's post. shucks. It was a longshot anyway I suppose.

I run XP Pro timoteo. But most of our beta testers were running Win 2000.

I am running XP Pro. Running any other application, the applications are stable. And actually, although VuePro crashes (or in my case, grinds to a halt), the operating system does not.

gebe would it be possible for you to get one of the techs from e-on to view this thread and read what the users have said their problem was and how it is effecting their computer. Their(e-on) way of offering help has a lot that is not very helpful when trying to get a problem solved. When you post a problem it takes 24 hrs to get an answer and then it will be a question that just keeps on leading to more questions. After a week of this I was back to where I started, No problem fixed and only an answer that there was a problem but I needed to duplicate it again and start the process all over again with trying to get help. This is enough to discourge anyone from using that kind of help system. My problem is exactly as the others have stated only they were able to put it into words better than I. Maybe the tech at e-on if reading this thread might be able to get a better idea with the problem by reading this thread. I am sure I was not able to get my explanation across to them with what my problem was when replying on e-ons tech site other than giving them a VuePro.eon had caused an error. We just knew I had a problem but I could not duplicate it or explain it to them in detail. The above members have explained in pretty good detail what is happening in Vue pro for the ones that are having a problem. The sooner Vue Pro is working for us that are having a problem the sooner all this bashing and wanting help will go away. I would much rather be using Vue Pro than posting about its problems with crashes and errors. Would this be possible for you to do for us. :)