I bought Poser 13 to support Bondware. It offered no real advantage over Poser 11 for my usage, except the suggestion that Firefly rendered faster. The first dismaying discovery was that La Femme loaded all black until I copied all of the textures from my Poser 11 runtime to Poser 13's. Then, technically, Poser 13 worked, so I got what I paid for. I added my other libraries, which show up and will add, say, a G2F character when I double click on it. But Poser 13 doesn't find the textures, just like with La Femme at first. When I open or import any scene I created in Poser 11, the figures appear without textures and I am supposed to find them all, one by one. I have used force quit to close Poser 13 far more times than the quit command. This useless to me. I bought La Femme 2 to support Ohki, and I sure hope it is worth trying out in Poser 11. Cheers.

Sounds like you got your File Search set to None in Preferences?

Mine is set to Shallow to help me track down issues for products, but for general use it's best to leave it at Deep - that will make Poser search all your Runtimes for the files it needs :)

If it's not that, then I'm sorry, I haven't used a Mac in years and we certainly didn't have Poser in it (it was at a former job) so I wouldn't know.

As for LF2, she should work well in P11 except for scripts (aka the stuff to convert LF1 materials, and the makeups in LF2 Pro). Though IMHO her skin looks much better in P13 with the new Subsurface Scattering methods, but still looks nice in previous Poser versions.

It's set to deep. But thanks for the suggestion! I haven't looked at the texture files yet (I'm doing first experiments with LF2 conforming clothing, and full-body sleeveless clothes and high boots look pretty easy to adapt with the morph brush), but can I use the skin tone face textures to make freebie makeup for Firefly like I did for base LF?

Maybe check and make sure that the Default Poser Prefs file is pointing to the location of your content. You can edit it using TextEdit, and will find it in your Poser folder, ⁩ ▸⁨ Runtime⁩ ▸ ⁨prefs. 

Bit tricky to troubleshoot since I'm not sure where everything Poser 11 is on your system and where any new Poser 13 stuff might be.

However, if you are still doing everything from a Poser 11 runtime, and just installed Poser 13 for the app itself it might be as simple to fix as changing CONTENT_ROOT_PATH "/Users/Shared/Poser 13 Content" to CONTENT_ROOT_PATH "/Users/Shared/Poser 11 Content"

Maybe check and make sure that the Default Poser Prefs file is pointing to the location of your content. You can edit it using TextEdit, and will find it in your Poser folder, ⁩ ▸⁨ Runtime⁩ ▸ ⁨prefs. 

Bit tricky to troubleshoot since I'm not sure where everything Poser 11 is on your system and where any new Poser 13 stuff might be.

However, if you are still doing everything from a Poser 11 runtime, and just installed Poser 13 for the app itself it might be as simple to fix as changing CONTENT_ROOT_PATH "/Users/Shared/Poser 13 Content" to CONTENT_ROOT_PATH "/Users/Shared/Poser 11 Content"

CobraBlade posted at 8:47 PM Tue, 17 October 2023 - #4476434

Maybe check and make sure that the Default Poser Prefs file is pointing to the location of your content. You can edit it using TextEdit, and will find it in your Poser folder, ⁩ ▸⁨ Runtime⁩ ▸ ⁨prefs. 

Bit tricky to troubleshoot since I'm not sure where everything Poser 11 is on your system and where any new Poser 13 stuff might be.

However, if you are still doing everything from a Poser 11 runtime, and just installed Poser 13 for the app itself it might be as simple to fix as changing CONTENT_ROOT_PATH "/Users/Shared/Poser 13 Content" to CONTENT_ROOT_PATH "/Users/Shared/Poser 11 Content"

Changing the pref to Poser 11 Content  made all the libraries disappear, but thanks for the idea.

Windows and MacOS uses different path naming schemes but I think that the concept is the same: in Poser's XXX  version user-profile related folder, you should find a file named "LibraryPrefs.xml". It's a text file, organized as its names implies it, as an XML one.  It contains the list of Runtimes the corresponding Poser is allowed to use.
On my system, I have P11, P12 and P13, both share a max of runtimes, except that P11 doesn't have access to "Poser 13 Content" nor to "Poser 12 Content"

If you know how to get to Users ▸ "Your name" ▸ ⁨Library⁩ ▸ ⁨Application Support⁩ ▸ ⁨Poser

You'll find folders for each version of Poser. You could delete 13 and then copy 'n' paste 11 to make a copy of that and rename it 13.
The next time you start Poser 13 it'll be using those settings you used with 11, which might make things better.

RobZhena posted at 7:55 PM Tue, 17 October 2023 - #4476429

I haven't looked at the texture files yet (I'm doing first experiments with LF2 conforming clothing, and full-body sleeveless clothes and high boots look pretty easy to adapt with the morph brush), but can I use the skin tone face textures to make freebie makeup for Firefly like I did for base LF?

One thing I've found is cross runtime issues.  I normally have about two dozen runtimes.  I keep each character generation in it's own runtime.  eg: a gen4, LF, LF2, Dawn...

I generally only have open the runtimes relevant to whatever I'm working on.  For instance, I usually don't have LF open when I'm working on toon stuff.  

Of course, installing only takes place in one runtime.  But Poser will look for files in all the runtimes you have open.  (It would be nice if the "remove from the GUI library" didn't also remove it from Poser's awareness.  But baby steps :)

 This really comes into play when I open scenes.  i have to make sure the runtimes used for everything in the scene is open.  For instance, let's day I used a LF, V4, a building (in another runtime).  I have to have all those runtimes open when I load that scene.  That's why I settled on generations.  I commonly used a4 textures on v4 body.  Or morphs as well.

I ran into the same thing when I was deduplicating to hard links (saves heaps of file space).  Have to dedupe only within a runtime.  Otherwise, things can break when you close one.  

You might get that error if the runtime where the texture is in not in Poser's library list.  But then it should notify you that some content was missing.

All sorts of issues are why I keep runtimes very separate.  From P8 on.  Everything in it's own.  And nothing is added to the default that came with the poser version.  This keeps the installation (and its content) clean.  If i have to reinstall, it touches nothing I installed after.  Decades of painful experience led to current setup :)

That's really helpful! Can I safely delete the Poser 13 library and just keep the one I know the textures are in, or will that hose the program?

That's really helpful! Can I safely delete the Poser 13 library and just keep the one I know the textures are in, or will that hose the program?

Fortunately, I'm stubborn, and I figured out what my problems was. So, not that anybody cares, I am not giving up on Poser 13 for Mac. And you cannot remove the Poser 13 content library. I tried!