I've had some downtime to find out some more on the trail of what is causing the menu corruption and discovered some very interesting info, that I hope will lead to a solution from e-on.

Earlier in these threads, we were focusing on a leak in the resources like is seen in Win98. However, as was correctly stated by someone else, Win2K does not have a set limit to the memory that resources can use, rather using the entire memory store. This is true. However, I found out that it does have a limit to how much resources can be allocated, but that limit is not based on memory itself, but the number of handlers for that memory. They are called GDI Objects and win2K allows for 10,000 of these per process. Since Vue is one process, it gets 10,000. How does this relate? Well when an application reaches that number, it corrupts the resource index and basically causes havoc in the system such has been reported here.

With this new found information, through Google, I found out that the task manager has a way to find out how many GDI objects are being created (Go to Processes, then in the menu, hit View->Select Columns and click on the box next to GDI objects). Now next to each item, you should have a number that corresponds to how many handles each one uses. This is great, because now we can figure out whether VuePro is doing something crazy with them and what is making it to that crazy thing it does so well.

So I loaded up VuePro and loaded a scene. The GDI object count was 105, which considering the memory load and the type of program it is, this was pretty good, considering that Acdsee runs about 500 handles. Then I started to move an item across the screen (this being in OpenGL). For every inch I moved the mouse, the GDI objects would go up 30-50, which seems very unusual, but I figured it would take them back off after I let go. Nope, it left it at that amount. So as you can see, moving an object continuously or in the example that started this thread, I guess a camera, it leaks these handles badly. To me, this is a bug in VuePro, not in Windows and it's now something that can be duplicated as a demonstration. What I would like to know from the testers or people who ran VuePro on win2K if yours also has that same racking up the GDI counts. If not, then maybe it can be narrowed down even further.

This particular error (though there maybe many more) only seems to happen in OpenGL, which is practically unusable in Vue4, so maybe that's why it's stable. I know what the supporters will say. Just turn off OpenGL. End of problem. Well that's all fine and dandy as a bandaid, but I bought the program specifically for it's better OpenGL support, and have the proper video card to run it. I'm not an animator and I find the plant editor to be quite lacking, so this was a big reason for my purchase and something that makes my life so much easier before the chaos begins.

Dale B,
With all due respect, I'm glad I don't deal with my customers as you suggest, or I wouldn't have any. A lot of bugs are directly inside of the program. While it's true, that operating systems can cause havoc and their own brand of craziness, a company or software house should never just ignore substantiated claims without at least checking and doing a global scour of the code. Just because in your eyes, it's a small percentage, doesn't mean that there isn't enough people reporting the same difficulties to give an indication that it is indeed a software bug and not just a hardware or user problem. I'll be the first one to eat crow if I'm wrong, but I think the above is pretty strong evidence that there is more to this than just some's lack of knowledge or specs.

John,
I don't think the OpenGL issue is part of the anti-piracy code, but I wouldn't doubt there might be such bugs like the one you mentioned.