Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 03 12:46 am)
I believe Runtime Repair will convert Absolute Paths (what you have) to Relative Paths, which is what you want, assuming you have a recent version of Poser. (I don't own it or I'd test it for you.)
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."But there really shouldn't be a drive letter in the path at all...
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."uh... why should there NOT be a drive letter in the file path WandW? -- I have runtimes on several different HDDs, and thus need the full paths, or else I have to go hunting when the files try to load using textures or geometry from a different runtime..
...and with regard to the original question, does using a shortcut to redirect the file search not work? (haven't tried it)
I think Wand was thinking more along the lines of content than PZ3's Nance. At least I hope that's all it was. PZ3's need absolute paths because of the mutiple runtimes issue and the speed of loading from absolute paths beats the heck out of searching multiple runtimes using relative paths. The's part of why poser takes so damn long before prompting you to locate files for absolute pathes when you've changed a drive letter. When absolutes don't work it tries searching relatives and usually fails.
Yes, I thought the issue was library content, as I myself don't keep saved scenes in my Runtime. If it were saved PZ3's I too would just use the text editor Save-n-Replace...
A thought; you could create a link from the new location back to the original location. In Windows, you would create a shortcut from the new Runtime location back to your Poser director or original external Runtime location, and rename it from 'Shortcut to Runtime ' to 'Runtime". This would probably work. In OS X you would create a symbolic link (at least that's what they are called in UNIX, which OSX is under the hood). This would almost certainly work, as it does work in Linux.
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."Quote -
A thought; you could create a link from the new location back to the original location. In Windows, you would create a shortcut from the new Runtime...
I tried it in XP-it doesn't work.
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."Quote - > Quote -
A thought; you could create a link from the new location back to the original location. In Windows, you would create a shortcut from the new Runtime...
I tried it in XP-it doesn't work.
I believe that starting with Poser 7 or maybe 8, Poser stopped seeing shortcut's properly anyway. When I had Poser 6 through 8 all loaded I know at least one of the Post Poser 6 versions wouldn't do anything at all when clicking on a shortcut in the library window. I'm pretty sure it started with version 7.
FYI I still have a "Shortcuts" folder in every library of my installed Poser 6, Character, Face, Pose, Prop etcetra, with shortcuts to all my external runtimes and they work just fine under Windows 7 Professional 64 bit.
Ok, I;m sure its just late & I'm being dim, but: if I have two props, in two different runtimes, on different drives, that both call the same geometry file, how do you not need the full path in the pp2, ... or two copies of the geometry?
If not in the current runtime, doesn't Poser go off on its own, searching through ALL the runtimes for it? Or is mine fubar?
In Windows, you can use Disk Manager to change your drive letters. I do it frequently with my flash drives.
♥ My Gallery Albums ♥ My YT ♥ Party in the CarrarArtists Forum ♪♪♪ 10 years of Carrara forum ♥ My FreeStuff
Sort of an after the Barn Door is open response, but one thing I do is Archive my Projects using Collected Scene Data to save the Projects out to their own folder. This allows me to open them without the Libraries active in the case of testing, but works well for the real world. I did it the first time I was setting up a new system back with Poser 5 and now do it out of habit. You can then open the Collected Scene Data File and add more things to it and after saving, run the Collected Scene Data again.
ratscloset
aka John
Quote - Ok, I;m sure its just late & I'm being dim, but: if I have two props, in two different runtimes, on different drives, that both call the same geometry file, how do you not need the full path in the pp2, ... or two copies of the geometry?
If not in the current runtime, doesn't Poser go off on its own, searching through ALL the runtimes for it? Or is mine fubar?
If they're the same prop calling the same geometry, Poser just loads the first geometry file it finds with the correct filename. Hopefully you don't have a different prop that calls for geometry with the same file name that isn't the same prop.
Quote - rat, where/what is, how you say... "Collected Scene Data". Embarrassed to ask since you said its been around since P5...but news to me.. Is that a third party app?
Scripts Menu... in Utilities (Collected Scene Data) there are two versions.... one is just a list, the other creates a Folder with all the Files needed.
I use this when using Queue Manager so everthing is easier to find... I always check it before Rendering, just to make sure nothing is amiss...
ratscloset
aka John
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.
I committed the mortal sin of changing the drive letter where my runtime lives a while back to accommodate other software needs. This broke pretty much everything. Is there anything out there (I'm willing to pay... though it really seems like something the already expensive program should be able to handle) that can fix that? I've tried runtime repair and other solutions, but I can't get them to work, too powerful and complex for what I need. All I need is to change that one little letter in the files.