Flog opened this issue on Jan 02, 2004 ยท 21 posts
ShadowWind posted Mon, 05 January 2004 at 11:52 AM
Flip-flopping between versions can cause all kinds of chaos because it leaves certain elements in the registry and other places. I have found in many demo to purchased program conversions that cleaning the registry of all remnants as well as any directories that were involved is a necessity in the uninstall process.
Dale, with all due respect, I seriously doubt that machines that are running Vue 4 fine and having difficulty with VuePro are having such problems due to motherboard/memory issues. VuePro has, well had, at it's inception, quite a bit of bugs that were software oriented. The fact that some people didn't experience these bugs, and maybe how they slipped by testing, can be broken down into two more likely scenarios. Whether one's workflow triggers such bugs, and what is running in the background.
For instance, there is a bug in the All-In-Wonder still capture in which it leaks memory from the resource table (causing the disappearing menu scenario that VuePro does). This bug is only noticeable under the most extreme still capturing and to the normal user and tester, it doesn't exist. I've only had it happen twice myself. but it does exist. The same probably holds true here. I'm a tinkerer with Vue, meaning that when I sit down to do a picture, I love to experiment and play. I load and delete things a lot, move stuff around, try many different texture combinations (both material and jpgs) and other such things, to get what I am looking for in the end. Many times, I'll admit, I don't even have a clear vision of what I want to do until I'm halfway through it. So perhaps my particular workflow (lots of undos/loading/deleting props, etc) triggers one of these bugs. So to me, I have trouble with the software, while someone with another workflow may not.
I will eat some crow and say that e-on has gone to great lengths to try to fix the many bugs that VuePro has and this latest session after patching to the latest has proven to be fairly stable. I still think some of the larger bugs were released prematurely upon shipment, but better late than never I guess. I really enjoyed using the new features that I bought VuePro for and can see the light is no longer necessarily a train. I was able to go from start to finish on a VuePro project (that had lots of figures and effects) for the first time. I think e-on still has some bugs to fix, but it's 100x more stable on my computer than it was when I first installed it (when it wouldn't run for more than 10 minutes without crashing).
ShadowWind