I've got a problem with Poser import which I gather is a bit of an old chestnut but having said that a search round the internet seems to have uncovered more suffering than answers and maybe someone here is better informed!

The trouble is when importing a scene from Poser into Vue, Vue is not finding any content. Despite knowing the relative path it clearly can't find the absolute path. Now the really annoying thing about this is that I had got this working perfectly and what has broken it is installation of SR 2 for Poser 2012, however I don't seem to be able to go back to a working configuration. My Poser set up does have multiple run time libraries but this was working for me before the SR 2 installation. Poser itself has no problems locating the files in the same scene file. I have Vue 10 inf configured to use the August 2011 Poser SDK and pointed at the base library for the executable (which is not the one where I have my main library).

Here's what I've tried:-

(1) I have "use external binary morphs" turned off in Poser

(2) I've reverted my entire prefs directory in Poser (took the option to back this up when installing the Poser 2012 SR 2 and just tried reverting it all)

None of this had made any difference and I am wishing I'd never gone with SR 2.

Any ideas?

Solved it! Posting the solution here in case it helpd anyone else as I was on the point of despair. Didn't want to have to use scripts to collect content in a subdirectory before import (but tried that anyway and it didn;t work). Tried editing the library prefs xml file to bring my main library to the front. No dice.

Here's what did work (although this may not be a full solution if you switch between libraries... Most of my scenes are built over one, it just isn't the default one)

Found in the file  Poser UI Pref Map.xml a couple of paths under a BfileSearch node called LastPath_Image and LastPath_Geom and noticed that these were pointing to relative paths within the installation. Manually edited them to point to my main ilnraries absolute path instead. Saved the file, opened Vue and tried the import...

Cue lots of grinding gears but this time no request for path information and got to the import options dialog without further problems.

Sorry in the above post where I said...

<>

I meant

<>

It's getting late and my typos are getting worse. Hopefully the above makes sense and might help someone....

Forgot to add (and it could be important). I also edited AddLibraryLastPath in this Poser UI Pref Map.xml file. Note sure if that is what fixed it or the changes described above.

The new patch for Vue 10 Infinite includes a new Poser SDK.  Does that help out at all?

That's interesting... I can't find any reference anywhere to anything more recent than this one:- Poser SDK from August 2011?

I'm on build 10008945 for Vue which as far as I know is the latest version of 10 and I'm now on SR2 for Poser 2012 so I thought I was up to date with all patches but if there is another SDK out there I'd like to try it because there are still some scenes where the import logic messes up the geometry. I raised this with eon ages ago but no solution available and the SDK was blamed. I'm not holding my breath for a solution...

Back to this problem, editing the  "Poser UI Pref Map.xml" seems to have worked for me although I couldn't find that documented anywhere and I also suspect that if I were to try scenes based over different libraries I would have to edit this file to "hard code" the new library before import everytime. Haven't tried it and as I almost always use content in one library (just not the base poser one) I am unlikely to need to do it. Even so, that would still be a lot better than having to select every path on an import....

That is an old build you have.

and Poser is at SR2.1     9.0.2.21492

Mazak

Ok thanks Guys. Interestingly when I ran a "check for update" on Vue it thinks it is up to date, so possibly something a bit wrong in the checking mechanism or the server I'm being connected to. I'll see if I can get hold if the update manually.

I think it might be because 10009012 is technically a beta build that I wasn't automatically notified to upgrade. Interested to how the new SDK works though (just in case it fixes some of the other import problems I've had historically), so I reckon I'll give it a try...

Quote - Ok thanks Guys. Interestingly when I ran a "check for update" on Vue it thinks it is up to date, so possibly something a bit wrong in the checking mechanism or the server I'm being connected to. I'll see if I can get hold if the update manually.

That works only once in awhile for old updates that are no longer in beta.  Best to login and see what new download was posted.

Keep your old update file still in case the latest patch breaks something that was working before.   But you probably already are familiar with Vue to know about that.  I typically hang onto the last three update files.