wimvdb, technically you're correct. The product works as advertised. I just don't think that reflects reality very well. It's like burying some critical piece of information deep inside a software terms of service agreement and expecting regular users to actually notice it.

I've not actually polled the Poser community on this, but my impression is that very few users actually use the default library structure. That means that everyone who uses a non-default structure will have to do extra work to get the product to work when the vendor could have saved everybody that extra effort by putting the morphs in the Geometries directory, or anywhere outside of the Library directories. So instead of the vendor doing something one time, you've got, what... 100, 1000, 10,000 users doing it 100 or 1000 or 10,000 times.

I should mention that some of the product's reviewers who complained about the lack of morphs appeared to be unaware of the obvious fix and resorted to other workarounds.

I realize that Poser doesn't provide vendors with any kind of standard of guideline for this sort of thing, but it looks like most have settled on using Geometries or a Morphs directory within the library directory.

I suppose the best approach might be for Poser to be able to recognize relative paths like HTML, so that a reference to just a file name would assume that it is in the same path as the referring file, and something like :morphs:MyFile.pmd would assume a subdirectory under the referring file, etc

---

OS: Windows 10 64-bit, Poser: 10