Thank you #Rhia474.

My bad: Took me a while to track them down, as Ghostship posts as bpmorton777

A caution: if RTE needs eg P4F 'Posette', there may be several versions with differing CRCs due updated credits / release info. But RTE will only accept one (1), cannot offer a clue. IIRC, I found a long-lost 'Classic' mermaid tail, had a lot of trouble locating the required P4F version. Yes, after trying several, its match was the original, deep in the legacy P4 run-time in my E: ½TB CAD archive...

FWIW, sometimes conforming clothes don't 'take' first time. eg LaFemme's swim-suit 'drags & drops' to fully conforming about 85%.

For the rest, if you move her, prepare for blushes. Gotta select & delete the garment, reload it...

Sorta B~C, as I set external library calls for WIPs to my ~½TB CAD archive on E:, unload when done.

To put it politely, i find Windows File Explorer search engine much, much friendlier than Poser...

My Poser run-time on C:, is minimal. Just the basic suite. My ½TB CAD archive on E: is reasonably organised, with many, many folders and sub folders. Each Poser whatsit or set has a 350x350 thumbnail, a meaningful name, the original zip etc and, where appropriate, a mini-run-time. I add WIP needs via the 'external library' facility, off-load when done...

To put it politely, I find Windows File Explorer's search engine is much, much friendlier than Poser's...

Sorta tangential to PZ3 issues...

"Quote - This will never be undoable as the pz3s cannot ever be converted back to absolute pathways ever again. It is tragic."

http://www.philc.net/PZ3editor.php { Recently updated for latest Win'10.}

PhilC's full PZ3 Editor ($10 registered) can pull the bundled models out of PZ3, similar to how GeomStripper can convert a PP2 to PP2+OBJ.

And, in passing, probably let you edit the paths...

Returning to Poser after a decade away from CAD, I found the Firefly defaults well behaved, but the 'new' superfly dire. Everything was horribly speckled, everything was so dull. Soon learned that a dozen Superfly 'pixel samples' gave similar quality to Firefly defaults, albeit very much slower. And, still dull.

Still learning, one 'oops' at a time...

IIRC, you are recommended to have Poser & core run-time on C: lest sundry legacy scripts, modules etc fail to 'play nice'. Same caution applies to other CAD programs: If core is not on C:, all bets are off...

I've a minimal 'runtime' on default C:, just core Poser. External library calls utilities and WIP stuff from my ½T archive on E:, calls I 'unload' when done. Archive is reasonably organised, each of the many, many sub-sets with its own mini-run-time...

Just been wrangling a large OBJ file, a sprawling industrial set/scene, that did not read its bundled ~30 KB MTL file. Yes, ~30 KB. Hand-loading those ~250 materials' calls to ~140 textures maps in Material room was totally impracticable, but I did first dozen from curiosity. Then thought to check the OBJ's MTL call. Opening ~32 MB OBJ file in Wordpad found path led deep, deep into a sub-folder on author's D: drive. Oops. Took longer to re-save than edit...

Question arises: If Poser can prompt to browse for a missing texture, albeit with legacy 'initial characters off field' bug, why is there no obvious way to browse for a strayed MTL ?? Or call an 'alternate' MTL ?? Could not find anything relevant in the 'manual'...

Aha, opening the huge (32 MB) OBJ in Wordpad found it held a path to supplied MTL file (30 KB, with 468 numbered materials calling ~140 texture maps !!) but in a deep, deep sub-folder on author's D: drive. Trimming path back to just calling the MTL file by name resolved that. In fact, took longer to re-save than edit...

But why is there no obvious way to 'browse' for a strayed MTL within Poser ?? It would also be a real-neat, portable way of loading scene texture variants...

I found a freebie 'Landing craft' model with multiple OBJs for its parts, each with its MTL, also 'proper' MC6 calls. Comparing MTL and MC6 pairs in a spreadsheet, I can see how each MTL holds a small sub-set of the MC6 info. So far, pairs' MTLs have only called Kd (diffuse) maps, but I'm seeing the pattern. Given a few more complex examples, I could probably edit MC6 down to basic MTL...

Latest problem is an imported OBJ / MTL which has too many texture calls for hand entry via material room. Literally hundreds. So, how to persuade P to read MTL, or convert MTL to basic MC6 ??

Yeah, I suppose it could cause a list-handling fault... Thank you. I'll check it out tomorrow !!

"...crazy number ... in the render cache."

How would that make the camera / scene animate ??

I've just installed the 'basic' Pro 11.3, happily retaining my modest library from 11.2. Hey ! And my un-saved trial renders !!

Took a lonnng time to load, but could have been scanning library etc. Took a couple of minutes to respond to the UI dot to switch to my preferred screen size, used a complete CPU core and ~96+% of GPU. Similarly, took ~30 secs to respond to simplest command.

After a while, I noticed the view was changing without my input. The camera was very, very slowly tilting upwards so that, instead of LaFemme in mid-screen, the ground grid-lines were vanishing off the bottom edge, one by one, followed by her feet, her ankles, her knees. And, perhaps, the camera was progressively tilting, too...

Happens I've seen such before, following an FBX import that went horribly wrong. So, I hit the animation toolbar's 'stop' button, turned 'loop' off. And then RESTORE ALL to pull the scene back. Yeah, prompt control functions restored....

How can I prevent this anomalous excursion ??

Now, why could the forum search engine not find my comment above ?? D'uh...

Belatedly thinking laterally, there's another possible explanation for missing textures: Some MMD PMX artists habitually set their models' texture folders to 'hidden' in Windows' File Explorer. ( They'll also 'mung' the PMX geometry which, IMHO, is a different bucket of stinky 'chum'...)

If an OBJ+MTL artist did this, and original path was 'baked' into OBJ+MTL, you would have to edit those paths and un-hide such covert folder(s)...