Wed, Dec 25, 8:03 AM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Dec 23 7:38 pm)



Subject: Question about the Poser 6 update...


schtumpy ( ) posted Thu, 24 March 2005 at 7:59 PM · edited Wed, 25 December 2024 at 7:50 AM

I'm an old school Poser 4 guy, but decided today to get Poser 6. First off, I'm not accommplished in any right, so this is like starting off fresh for me. I'd never used P5. Anyway, on to the question. How do I get all my old P4 stuff into P6? Is there a mechanism that I've missed to integrate that stuff or do I have to work in both of them? Any help would be great. Thanks


randym77 ( ) posted Thu, 24 March 2005 at 8:10 PM

You can just add your P4 runtime to your P6 library. You can add extra runtimes to Poser 6, the same way you'd add a pose or a prop.


nerd ( ) posted Thu, 24 March 2005 at 8:13 PM
Forum Moderator

You can link P6 to your old P4 runtime. Open the library and click the "up" folder till you see "Poser 6" and "Downloads". Click the (+) a the bottom of the library. Browse to your P4 Runtime folder and click [OK]. You will get a new folder titled "Poser 4". Double click it, Poser will growl for a minute and you will have access to all your P4 stuff. To switch back to Poser 6 content just go up to the root and then double click Poser 6. This DOES NOT move the P4 library, it just links to it. Nerd3D


Little_Dragon ( ) posted Thu, 24 March 2005 at 8:13 PM

Posers 5-6 have a feature called external runtimes. You're no longer limited to the single set of library folders within Poser; you can have runtimes anywhere, even on other hard drives or removable media. And after you tell Poser's library where to find these runtimes, you can switch from one runtime to another at will.

You don't need to move any of your old P4 stuff, unless you plan to completely uninstall P4. You can simply point P6's library to the existing P4 runtime, and use it from there.

jelisa has a tutorial on the subject.



kuroyume0161 ( ) posted Thu, 24 March 2005 at 8:14 PM · edited Thu, 24 March 2005 at 8:15 PM

See Geep's threads on adding Runtimes to Poser 5/6:

Link

Message edited on: 03/24/2005 20:15

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone


caulbox ( ) posted Fri, 25 March 2005 at 12:57 AM

I expect that there'll be plenty to keep you occupied when Poser 6 arrives... but my advice would be that as you're becoming familiar with Poser runtime libraries, now would be a good time to keep an eye to the future. I'm also awaiting the boxed P6, but (hopefully) installation should not be much of a problem as I keep all my various runtime libraries in a self-contained separate partition, and I will just need to point Poser 6 to their locations. It's taken me ages to (begin to) organise these runtimes 'precisely' as I wanted, and only now am I beginning to realise the goal I had been attempting. As the sheer volume of Poser content continues to increase so dramatically, I personally find it 'essential' to keep some structure and organisation. Not only does Poser seem to load faster, but (for me) it's become so much easier to browse and locate items in this sea of many gigabytes. Separate self-contained runtime libraries (I use about twenty) also make easy (DVD) backups possible. Initially, it will indeed be a simply task for you to point P6 to your existing P4 runtime. However, eventually you may find that you also develop your own particular style of organisation, and might wish to disassemble your inherited P4 runtime into more manageable optimal constituent runtime libraries of choice. WARNING! This isn't an easy task, and the difficulty will constantly be getting greater as your (single) runtime continues to grow. My own peculiar solution to this problem was to use (yet another) separate partition which I labelled "What a Mess" - for obvious reasons! Only very gradually have I managed to re-locate the bulk of the content of the runtime libraries here, to a more organised structure where all my characters (etc) have their own runtime libraries. I've been at it for about a year now, and I still haven't finished! But I'm glad I started :)


kuroyume0161 ( ) posted Fri, 25 March 2005 at 1:28 AM

Going off on a wild tangent here, but your remind me of what I just spent the other day doing. I've been collecting emails back to maybe 1995 (hard to tell since the oldest have lost their date/time information). In all of this time, I have always just saved sent email in the Sent folder and received/saved emails in a Received folder. At this time there are over 6000 in each (and I'm very selective!). Well, I finally decided to make subfolder on the received emails to more easily find them by relevance (and speed up email searches). It took some time, but was well worth the effort - I didn't know how to move emails when using Outlook's Find feature for a little while. Parsing out how to organize them and where many disparate emails should go was half the battle. It really does require a more or less personal structuring. Glad that I started in this endeavor as well. :0)

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone


gothicenchantedangel ( ) posted Fri, 25 March 2005 at 3:47 AM

Yes I'm making up seperate Runtimes up as well now :-)


BillyGoat ( ) posted Fri, 25 March 2005 at 10:29 AM

Thank you all for the information. I installed/uninstalled P5 the day I got it. Just a Poser 4 diehard. I ordered Poser 6 and have no idea of the file structures. I'm so glad this was brought up! BillyGoat


caulbox ( ) posted Fri, 25 March 2005 at 12:05 PM

Just one added comment. I certainly wouldn't want to interfere with what (I agree) is essentially a task of personal structuring. However, if I may be permitted to make just one suggestion. Put all of your hair stuff, in a separate runtime library. My own hair runtime library (about 2 gigs) is probably my most frequented (as well as being my favourite). I was hesitant at first as to whether I should include the relevant hair types within each character runtime instead, but am I glad I didn't! Most hair stuff is universally applicable, and trying to spread the content across runtimes would IMO only have added to the chaos that I was trying to eliminate.


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.