AsteroidLady opened this issue on Apr 01, 2015 · 13 posts
AsteroidLady posted Wed, 01 April 2015 at 6:32 PM
If I install content into my main Poser runtime, it hides it. So I've just gotten into the habit of putting it in other places. So what do I do if it's something that will only work if it's installed in the main runtime? It doesn't put the stupid locks on it, if I look into the folders it looks normal, but it just doesn't appear in the library.
Boni posted Wed, 01 April 2015 at 7:17 PM
Excuse me if I'm asking an obvious question ... but did you refresh your runtime after the install? If you have Poser running and you add content you need to refresh the runtime you've installed it to for it to show up. I hope this helps. (on the runtime folder in the library is a round arrow, that is the refresh ... click that).
Boni
Boni
"Be Hero to Yourself" -- Peter Tork
WandW posted Wed, 01 April 2015 at 8:21 PM
If I install content into my main Poser runtime, it hides it. So I've just gotten into the habit of putting it in other places. So what do I do if it's something that will only work if it's installed in the main runtime? It doesn't put the stupid locks on it, if I look into the folders it looks normal, but it just doesn't appear in the library.
If you are using Poser 8 or higher, the runtime in your Poser program folder shouldn't be part of the Library, beacuse of Windows User Account Control in Vista and higher. The only things that should be installed into the program folder runtime are python scripts to appear in the Scripts menu, Face Room heads in Poser 8 and PP2012, and add-ins in Poser 10 and PP2014. The default content location is outside of the Program Files hierarchy for good reason, and one chooses otherwise at their own peril.
Edit; I managed to delete the previous iteration of this message without a prompt; fortunately I had the text in the clipboard. Not to hijack the thread, but I ask again, WHY IS THIS FORUM SO FCKED UP???? (I'd use the real word, but there's no profanity tag in the editor; I'm Bldy pssed!!) :(
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."
AsteroidLady posted Wed, 01 April 2015 at 8:53 PM
Yes, I refreshed it...I recently bought some older Poser stuff at a sale, installed it into the external runtime as usual, and it wouldn't work. When I contacted customer service at the store I bought it from, they said it's because it needed to be in the main runtime. So I moved it to there, and now of course it doesn't appear in the library. So, basically, I can't use it? I currently have it installed in both locations but it isn't working.
hborre posted Wed, 01 April 2015 at 9:08 PM Online Now!
Exactly what content did you purchase?
seachnasaigh posted Wed, 01 April 2015 at 9:32 PM
If you're on Vista or later, look in
C:UsersusernameAppDataLocalVirtualStoreProgram FilesSmith Micro
and manually copy any runtime stuff to your main runtime.
Poser 12, in feet.
OSes: Win7Prox64, Win7Ultx64
Silo Pro 2.5.6 64bit, Vue Infinite 2014.7, Genetica 4.0 Studio, UV Mapper Pro, UV Layout Pro, PhotoImpact X3, GIF Animator 5
AsteroidLady posted Wed, 01 April 2015 at 11:41 PM
I already looked in appdata. As I said, if I look into the folder, it is there, it looks normal, it just doesn't appear in my library from within Poser. If I put it in the external runtime, it does appear, but the dials don't work. I have Windows 7. The products in question were some morph packages for Poser 6 and 7 characters.
AsteroidLady posted Thu, 02 April 2015 at 12:39 AM
And I'm not even convinced that's the problem. It would help if I knew why it's supposed to be there. I noticed it uses pmd files, and I previously had a similar experience of my dials not working when I had accidentally turned on pmd files and they weren't automatically loading, which makes me think it has to do with that. They are not where they need to be. But, I currently have them installed in both locations, and it still isn't working. Where do these actually need to be, in relation to what?
WandW posted Thu, 02 April 2015 at 6:00 AM
As I noted before my rant, the Runtime in the Poser program folder is not part of the Library.
PMDs wil load fine with Binary Morphs turned off, but Poser just won't save them. They usually live in the same folder with the file that loads them, but that depends on how the pz2/cr2 is set up. Is it a figure or morphs?
----------------------------------------------------------------------------------------
The Wisdom of bagginsbill:
"Oh - the manual says that? I have never read the manual - this must be why."
hborre posted Thu, 02 April 2015 at 8:18 AM Online Now!
If you are referring to Generation 4 morph packages from DAZ for V4, M4, etc, those should always be installed into the runtime containing the base models and initialized. It doesn't matter where the runtime is externally located. As WandW posted, do not install into Program Files for those OS mentioned, always install into external runtimes or the Poser Content folder which, by default, should be located in a separate share folder. PMD's are always located on the same level as the cr2's, within the same folder. It doesn't matter whether it is on or off in the General Preferences, Poser will still recognize it. However, if you have multiple instances of the same file linked to the Poser Library, the pmd's might not work correctly, even though I haven't seen this happen yet.
AsteroidLady posted Thu, 02 April 2015 at 11:36 AM
They are for Poser figures, for James and Jessi. Morph packages. I'm guessing the folders are a little different in Poser 7 than in Poser 10? So I should stick them in the folder with the cr2's?
hborre posted Thu, 02 April 2015 at 12:17 PM Online Now!
Same runtime as the cr2. However, double check that the morph packages match the figures. IIRC, there is a JamesG2 and a James, and there is definitely a JessiG2 and a Jessi. The morphs are not applicable to both.
AsteroidLady posted Fri, 03 April 2015 at 3:16 PM
I see. That's probably the problem, then.