I purchased Vue4Pro hoping to do some good animations from Poser. My copy has basically never worked. I have tried three systems but they were all Windows 2000. I have a brand new system service pack 4, plenty of memory. After I import a Poser figure if I switch to another application (poser, task manager) Vue4Pro is hung not using CPU. I try to use the mover wizard just to make a fly thru with the camera on an empty scene, it doesn't show the way points. At the finish button it hangs. After that now it won't even get to the waypoints, just hangs one or two screens in on the mover wizard. I have tried both the official patch release and this very latest one. What a piece of crap! Does this thing only run on macs? Is it java based? What gives? Frustrated in San Diego

Did you try closing poser before opening Vue ? I know that Vue 4 doesn't play nice with other applications. I haven't used Vue Pro enough to tell about that for sure.

In Vue Pro you don't need to close Poser. Are you saying yhat you cannot see the way points you create in the wizard? Or in the scene?

My response from e-on and they were correct, was that Open GL was not working. So at least that problem is solved. My main complaint is the hang after importing a Poser figure. That is what I got Vue4Pro to do and it does not work for me.

Are you sure it's actually hanging at that point? It takes a VERY LONG TIME to import a Poser figure. I usually start my import and wait for the message about grouping the meshes. Then I go and do something for a half hour or so to see if the import has finished. During this time Vue is figuring out the textures and creating a "mini-render" that it uses to display the figure in OpenGL mode. I'm running WinXP with only 256Mb RAM and it works fine for me.

The hang occurs after the import. You can actually drop the figure, rotate, add trees, save. The hang occurs if you change applications like switch to IE, task manager. You can't ever switch back to VUE4PRO. Its not using any CPU just won't respond to the user interface. I have tried it on three Windows 2000 systems, one freshly installed with SP4.

grunthor is right. Even when the slider is at its end, the import is not finished. You must wait, wait, wait:-)

I have Vue 4.12, Poser 4.03, and Vue 4 Pro on a W2K SP3 system with 1G Athlon and 1G DDRAM. Poser figures generally come in to Vue and Vue Pro fairly quickly for me. I do know that both Vue versions don't like me to use other applications while Vue is open. I always close Poser before importing to Vue, old habit from Vue d'Esprit, see no reason to change. I have had crashes of Pro when I change a figure in Poser and reimport to Vue if I have modified any textures; rather than update them or apply the modifications to the new import, Pro does the "generate error" thing and crashes. This has been reported to Eon.

And yes, Guitta and grunthor are right; I always wait until the imported figure appears in the world browser and the mesh appears on the screen before attempting to do anything. It may seem like Vue or Pro's not doing anything, but it is!

Before you try to move the figure, rotate it, etc. have all of the textures been applied to the OpenGL view of the model. If not then the import hasn't finished yet. I've also had a few crashes when I have more than one thing open at a time with V4P. I've always attributed this to my lack of memory.

Hmmm... Grunthor, you -may- also have a bad memory bit at the high end of the bank. That is one of the most common causes of 'this program is a piece of shit!' that I've seen; particularly graphics programs. 90% of what's out there never get near the top of the memory stack, but high end games and graphics programs, with their texture loads, can. And all it takes is one bad bit. Most people still don't realize that they never get out of the lower 512megs, so the upper end of that 1 gig stick could be landfill, and they would never know it. Unless they addressed it. (and it is very possible to have a bad stick of memory, even if the BIOS memcheck says okay. That's a very simple access/talkback check. It doesn't do level testing, to see if there is a weak cell in the memory that only holds its value most of the time...)

That could be Dale. But it's only happened a couple of times (2 or 3 at most) in the months that I've had V4P. As a hobbyist it's not a big enough problem for me to worry about.

I want to give credit to e-on for discovering the problem. It seems that it is really an OpenGL interface problem. I disable OpenGl because it was keeping my Mover Wizard from working correctly and the problem has stopped. Has anyone discovered the list of supported cards?