Fri, Nov 8, 3:02 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 08 8:41 am)



Subject: Confused about P5 Runtimes, Libraries, the Download Folder


Basis3D ( ) posted Fri, 24 October 2003 at 2:56 PM · edited Sat, 26 October 2024 at 12:38 PM

Is there any good explanation available anywhere on how these multiple Runtimes are supposed to work in P5? The explanation in the P5 manual has me confused because I think I'm following it but nothing works. If I have a folder of, let's say, a Prop ... where exactly do I place that folder within the Downloads folder? I've tried dumping it into the Download folder as well as inside the Runtime folder inside Downloads but when I switch to it in Poser nothing ever shows up. TIA

 Poser 2010 • Poser 8 • MacPro Desktop • Quad-Core Intel Xeon • 10 GB • Snow Leopard • Windows XP 


Bobbie_Boucher ( ) posted Fri, 24 October 2003 at 3:32 PM

file_81326.jpg

I don't use the Download folder. I save everything into a Temp folder, then unzip the stuff there. I install most of my new stuff in a new runtime folder, with the exception of Vicky 3 & Mike 3. (The seem to run better from the main Poser 5 folder.) Here's a screenshot showing how to add a new runtime.


Basis3D ( ) posted Fri, 24 October 2003 at 4:15 PM

Thanks. So where do you keep the new runtime folder? I guess it isn't supposed to matter but I'm still having problems.

 Poser 2010 • Poser 8 • MacPro Desktop • Quad-Core Intel Xeon • 10 GB • Snow Leopard • Windows XP 


MarianneR ( ) posted Fri, 24 October 2003 at 4:34 PM

Anywhere. I have some burnt to CD:s. It works with P5 on Mac at least.


stewer ( ) posted Fri, 24 October 2003 at 5:52 PM

I put everything in the downloads folder. That way, I only have to backup that folder and have an otherwise untouched Poser installation, which should come handy in the unwanted case I should need to reinstall.


dogsbody ( ) posted Fri, 24 October 2003 at 6:05 PM

You could use Pboost as a library manager - it dynamically swaps directories in order to get over Poser restrictions. I use it if I'm using Poser4 (unusual these days but..) Under P5, you can define your own structure, but it takes a bit of work to maintain it. For instance, under 'Figures' and 'Poses' in the P5 menu structure, I have different folders for V2/V3/M2 whatever, those are subdivided into 'Real' characters, Clothing, Character MATS, clothing MATS etc. (hope this is making sense, if not IM me) The problem comes when you buy something new and it unzips into the standard structure. You can ignore the geoms and textures, but the Characters and Poses will need to be moved from runtimeposes (e.g) to runtimeposesV3 Char Mats (or whatever you choose to call it). It's a minor annoyance, but makes searching the Poser structures one hell of a lot easier. The exception is V3 injections, and I suppose that M3 will be the same. Some commercial pose files rely on the injections being in a standard directory structure, (and bear in mind that V3 has some 28 injection libraries). If you move those libraries then the poses can't keep up. The only solutions are to bulk edit the poses to replace the library references, or keep the original library references (which makes your P5 pose interface very cluttered), or if (like me) you find that you don't use those particular poses very often, when you get the first mismatch reported in Poser you can minimize and do a bulk copy of the INJ files to where the pose expects them, then delete them later so they don't clutter up the interface. Messy I know, but far quicker than answering 7 billion "I can't find xxxxx" dialogues If enough folk are interested, I'll write a tut for this, but really it's just common sense Dogsbody


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.