Mon, Dec 23, 5:18 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)



Subject: Poser to Vue Runtime Problem


regaltwo ( ) posted Thu, 04 December 2008 at 7:26 PM · edited Mon, 23 December 2024 at 10:46 AM

I recently got a new computer (which I'm pleased with).  But I've got 1 problem.  I reinstalled Poser Pro and Vue on my new computer, and I copied my runtime from my old Poser install to my new computer.  I then went in and added the runtime to the list in Poser.  But when I try to import a Poser file into Vue, if any of the scene I bring in is in the old Runtime, it can't find the textures, and it's a pain to have to guide it to it everytime.  BTW, it finds the stuff in the main runtime just fine.  Any suggestions as to how I can fix  this?


thefixer ( ) posted Fri, 05 December 2008 at 1:26 AM · edited Fri, 05 December 2008 at 1:27 AM

I use one runtime with sub folders rather than multiples like you, one suggestion I'll offer is to put your other runtime into the downloads area of your main poser folder and see if it works there.
It's not a proper fix, but it might be a work around!

Injustice will be avenged.
Cofiwch Dryweryn.


Rutra ( ) posted Fri, 05 December 2008 at 2:55 AM

I do like thefixer, only one runtime, and everything runs fine. I used to have several but I kept having problems with imports. However, I've read of people with multiple runtimes and have no problems. Why some have and others don't... I have no idea. I don't think much about these things, as long as it works, it's fine for me. :-)


Angelsinger ( ) posted Fri, 05 December 2008 at 4:42 PM · edited Fri, 05 December 2008 at 4:51 PM

If you mean the .pzz or .pz3 file when you say "Poser file", I think I may know why Vue asks you to locate the textures.

I have looked at many of my poser files (created in Poser 6 & 7) in a text editor, and inside all of them, each texture is listed according to the exact path in which it was located when I first created the scene. This obviously includes the drive letter, etc.

So when I transferred my runtimes to a different drive later on, the scene files themselves still had information inside them pointing to the old location of the textures.

To avoid this hassle, I handled it 1 of 2 ways:

  1. Before importing the scene into Vue, I made a copy of it (to be safe), opened it in a text editor, and did a "Search and Replace" of all the paths to update the jpgs to their new location. After saving the edited scene, Vue then read those updated texture paths and imported the scene without asking me to locate anything.

(If you don't like editing your scenes in text editors), you can also:

  1. Get Poser to export all the textures used in your scene to a single folder, and place the files from that folder in the same directory in which your Vue scene resides.

How do you do this in Poser? Go to the menu, choose --
Scripts, Utility, collectSceneInventory, Copy all to folder

Vue will first look for the textures in their original locations, and when it doesn't find them, it will 'spot' them in their new location (because they are in the same directory as your .vue scene). So Vue will show this message:

"Unable to find file (then it gives the file's original path) --
Use file
(mentions the file it found in the copied location) instead?"

Choose "yes to all", and Vue will then automatically use all the other texture files in that same folder.

I prefer method # 1 btw. : )
And I sincerely hope this helps.  ; )

**EDIT: **I need to add that I had to decompress my .pzz files in order to edit them. The .pzz files look like gibberish inside text editors, but the .pz3 files have language I can read!  :p


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.