Ok, before I start, I know this sounds more like a question for Eon support and I'll probably go there eventually but I just thought I'd ask here first....

Has anyone ever tried the option to allow posing in Vue after a Poser import? I'm aware of all the warnings about doubling the memory footprint but has anyone seen it work? I've got Vue 10 Infinite at the current service release (built 10008456) and Poser Pro 2012. I'm using the August 2011 SDK for import which is the latest one. My machine is fairly highly specified (64 bit Vista with 12 Gigabytes of memory and a GTX 295 GForce Graphics Card) and I would have thought it stood a chance of using this functionality but I don't seem to be able to get it to work.

When I switch on any feature requiring Poser Support in Vue as part of an import (posing or rendering using the shader tree), Vue crashes with an error part way through the second stage of the import suggesting that the graphics card isn't able to handle it. In fact it's this error here:-

http://nvidia.custhelp.com/app/answers/detail/a_id/3007

Seems like I'm stressing the graphics card by asking for Poser support in Vue but I'm not sure why graphics would be particularly affected as opposed to the rest of memory and I'm also not sure if there is anything I can try in my Vue settings that might help.

Looking at the Vue display options I'm using Open GL 2.1 (shader 4) with max available video memory set to 128 MB. There are a lot of options out there but I'm not really sure what's sensible to try as I'm not clear why this Poser link stresses graphics performance in the import. Should I try increasing vide memory usage or changing the quality settings, or other aspects of open GL texturing or are these not relevant?

Just curious if anyone uses it and has ideas as to what might cause the problem...

Just looked four posts down the forum and I see I am not alone with graphics driver problems. Must remember to read the forum first before rushing off to post!

Possibly this is a graphics driver issue but I am now on the latest Gforce one (295.73) and I still have the problem. If there is some way I can work around the problem I'd still be pleased to take any suggestions...

Switched to software Open GL and I can imoprt properly, so clearly this is some kind of graphics driver problem and not one resolved by the latest driver.

Hi again, DMFW,

Mind you - I am by no stretch a pro when it comes to Vue or Graphics cards, but from what I have read, if your graphics card has the memory capacity, you should definitely set it to 1024.  Otherwise, I would think much of its capacity goes wasted.  Maybe someone else could clarify.

Ok, thanks, that's worth bearing in mind. Using the Open GL in software mode is kind of OK in an emergency but not that nice to work with longer term when you've been used to using the graphics card acceleration. It's noticibly less reponsive and less accurate. I did try a work around of importing my scene in software open GL, making the posing changes there then changing back to hardware acceleration and reopening the scene (have tried this in conjunction with your suggestion about memory capacity above). In fact Vue appeared to tolerate this for a while, but I think the fundamental problem is the combination of using Poser "emebedded" functions and the hardware acceleration and sooner or later it crashes with these two together (and seems markedly less responsive too).

It's very hard to work with posing in Vue using the software open GL because there is too little detail to see what you're doing. In fact I only went down this route at all because of some inaccuracies in the import which I thought I might be able to correct in Vue but the flakiness of the display and the relatively clunky posing interface in Vue has convinced me to steer clear of this work flow in future! I'm going to stick to simple static imports where Vue and Poser operate more independently as generally speaking (apart from the one geometry problem that lured me into this problem) that does seem to behave nicely.

There is a newer build since 8456.  Have you tried using OpenGL (fixed hardware pipeline) instead of OpenGL 2.1 (shader 4)?  Works great that way for me.