I'm afraid I didn't follow the custom morph vs. native morph part, but that's OK for now. The thing that stood out was your point that Poser  (Smith Micro) content places the pmd and cr2 together.

I never used SM-Poser content other than the primitives, so I wasn't aware of that, but it came as a real surprise. That seems to defeat the whole idea of arranging your content in a meaningful way unless you are willing to set your search options to shallow or deep, which I don't want to do. Maybe I'm just being old school about this, but I've always felt that if a file was not where it was supposed to be, I wanted to know about it so I could fix it. I don't like the idea of having an app look all over the place for something that seemed to be what I wanted.

And that brings us back to relative paths. I've done a lot of programming in my time on many different platforms and with many different languages and I never had a problem with relative paths. Consider HTML:

1. links in the same directory as the current page have no path information listed: filename
2. sub-directories are listed without any preceding slashes: weekly/filename
3. links up one directory are listed as: ../filename

Easy enough. I can't imagine why that would be difficult to implement in Poser unless there is something very unusual somewhere in the core of the app, and there might be.

---

OS: Windows 10 64-bit, Poser: 10