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