I will try to describe my problem clearly. Over the weekend I installed a new 1TB internal hard drive and then moved all my linked  poser external runtime folders to it because my C: drive was getting a little bit too crowded.  Poser Pro and Poser Pro 2010 had no problems finding the content so all was good there. Then I had an issue with Vue ( 7 infinite ) and had to re-install it so of course I had to re-set all my preferences and the poser import. when I checked the poser import status in my preferences it was on Poser Pro okay good then I didn't have to change anything.

My problem is this anytime I create a scene in Poser Pro and then import it into Vue it seems Vue can't find a blessed thing now.  It asks me for everything .obj files, textures file the whole shooting match it as if something did work when I set my poser import.

Vue will ask me to manually hunt down each and every texture, obj, trans map, etc for example"

"Can not find Runtime/textures/pangopango/blue.jpg would you like to find it manually?" as you can see there isn't even a drive letter just "Runtime". So I am lost on how to fix this even if I were to move things back to the C: drive it defeats the purpose of having another drive for more space.

My Vue content is on the E: drive (New drive) and has no problem finding things like .vobs and scenes.

So does anyone have a clue as to what I should do? I find it funny that after a new install of Vue that my poser import and my general preferences were really not changed or at least gone back the default settings?

Any help would be appreciated!
Thanks!

Never mind got it fixed thanks for all the help.

Well what was the solution?
I'm having similar problems.
Thx

I find that a foolproof method is to use the "collect scene Inventory" script in Poser. This saves the scene file and copies of all object files, texture maps, dynamic simulations etc into one folder. Vue has no problems finding anything from there.

Quote - Well what was the solution?
I'm having similar problems.
Thx

Greetings neighbor to the north( I am in SW Missouri)!
Well it's a long story but in a nutshell when I linked the poser Pro (older version) runtime folder to Poser 7  the issue went away. Which is confusing seeing I have Poser Pro selected as my Poser import. I think it had to do with when I needed to install A4/M4/V4 and all the other little mil 4 people into poser pro. The Daz installers those Bitrock things didn't have a selection for the Poser Pro.exe all it went up to was Poser 7.

Anywho, I copied the poser.exe and then put into the Poser Pro folder so the Daz installers could install the mil 4 folks to Poser Pro. I think some how Vue is only reading the poser 7 exe. Why I feel this way is when I un-installed poser 7 Vue had a fit couldn't find a dang blasted thing. Anytime I mess with or move something that has to do with Poser 7 Vue does this. Maybe I did something wrong along the way I don't know nor do I have an explanation I do know all is well again.

Thanks for the feedback. I'll give these solutions a try.