| Following are instructions on linking your Poser 4 Runtime (or another runtime) to Poser 5: | |
|
Okay, make sure that you are at
this level in the Poser 5 library. The red dot indicates that the Poser 5 Runtime is the active one. |
|
|
Now, either click on the down arrow above and to the right of the Poser 5 folder and choose Add New Runtime or Click on the Add runtime plus sign at the bottom of the library |
|
| The Browse for Folder panel will come up where you can locate your Poser 4 Runtime folder |
|
|
My Poser 4 Runtime folder is
located on my D drive, so I navigated there, selected the Runtime folder,
then clicked on OK. Do not go into the Runtime folder. |
|
| And the Poser 4 Runtime folder now shows up in my library panel. |
|
| And here is all my Poser 4 stuff: |
|
| You can also add additional Runtimes, this one here is the one I'm using to reorganize my P4 Runtime for Poser 5. It's located on my E drive until I finish reorganizing then will be moved to a subfolder on my D drive and relinked. |
|
|
Poser 5 is very literal in its
translation of pathnames and using small or capital letters. Once you've
linked your Poser 4 Runtime and try to use a file that applies textures, you
may have to fix the pathnames in the file. A good text replacing tool that
will fix multiple files at once here is a good thing. For example, I applied a MAT pose file to Victoria using one of their MAT pose files and it worked perfectly. I then applied a MAT pose file from the Sakari package and it started asking me to locate the textures. After comparing the two files in WordPad, I noticed that the DAZ file used a relative pathname, ":Runtime:textures:DAZ:..." while the Sakari file used a full pathname, "C:\Program Files\Metacreations\Poser 4\Runtime\textures\Sakari Textures\..." Since my Poser 4 is in "D:\Poser 4", this pathname didn't exist. Using a multiple file replacement tool, I changed the full pathname to ":Runtime:textures:Sakari Textures:..." and the MAT pose files then worked perfectly. Other files that I had problems with ended up being because the relative pathname in the file was missing a subdirectory or used a small letter where a capital letter should have been. |
|
