@patlane

Ok. I think you're making this more difficult than it needs to be. Put all of the objs that are referenced by cr2 in the same geometries folder on the same drive. If you have to manually edit the file path references to the objs in the cr2, do so. The obj reference sections are at the start of the cr2 and then again not far down through the cr2 file.

Is this cr2 you've created intended as a marketplace product or a freebie?

Unless Renderosity is requiring you to include an inventory collection through that utility script I think its moot. I know that freebies have no such requirement.

Create a Runtime folder with a Geometries folder, a Libraries folder (and relevant sub folders), and a Textures folder. Within each create a sub folder that identifies your figure and place the relevant files. Place the objs in the Geometries subfolder. Place the cr2 in the Characters subfolder (with the necessary mapping applied to point at your objs). Place your image files in Textures. Load you figure into Poser and create image based materials in the material room that point at your files in textures. Also references are created to textures that exist on the figure at the time of being added to the library, if the location has changed for textures make sure to reapply the textures and resave. Create any pose files.

It's best, for redistribution, to use relative paths in the cr2. Relative paths start with Runtime and are separated by colons like this

figureResFile :Runtime:Geometries:MyFigure:MyFigure.obj

And so too with all image file references within the cr2, like this

textureMap ":Runtime:Textures:MyFigure:MFDiff01.png"

Sometimes, for strange reasons, Poser will write absolute paths. I had a problem with absolute paths in one of my freebies I had to correct. It was for alternateGeom: objFile references (geometry switching).

After all this write a ReadMe that also lists included files, put that in a Documentation folder separate from Runtime and zip it up with an appropriately named zip. If everything loads fine from this Runtime structure with no errors you should be good for distribution.

And now I'm tired of talking, may have forgotten something, and need to get back to my Poser projects.

Take Care.

---

W10 Pro, HP Envy X360 Laptop, Intel Core i7-10510U, NVIDIA GeForce MX250, Intel UHD, 16 GB DDR4-2400 SDRAM, 1 TB PCIe NVMe M.2 SSD

Mudbox 2022, Adobe PS CC, Poser Pro 11.3, Blender 2.9, Wings3D 2.2.5

My Freestuff and Gallery at ShareCG