the /toLux folder isn't created.

Noob problem time.
I downloaded PoserLuxExporter_alpha_1-10e.zip and unzipped it to /Runtime/Python/poserScripts as indicated in Getting_Started.txt. I ran the script and nothing appeared to happen. I tried moving everything to /poserScripts/LuxExporter as indicated in the comments of the script itself, but still no joy.

I can run LuxPose.air and it brings up the GUI and generates an output file. But running PoserLuxExporter.py within Poser doesn't open a Python window or, after several minutes with a very simple scene, generate any output file that I can find. I have Poser 7. Do I need Poser 8 or 2010 to run this?

Quote - remove the ... gophers? :lol:
(sorry, couldn't resist)

If he removes all the golfers, who's gonna pay the grounds fees?

I put both. OBJ format imports like their textures in the same directory as the geometry. Also, when I've made props in the past I've made bad texture references that bit me later, so I thought I'd eliminate that problem. Once a prop is in the library, the copy of the geometry can be deleted from Textures.

I was thinking that, since some unfamiliar bug involving textures was popping up, maybe there was bad internal data being generated when the OBJ or other geometry was imported that didn't show up until new props were spawned.

An experiment that I did just now:
I copied a folder containing a Waveform OBJ and its textures into the RuntimeTextures folder, and imported the OBJ. That caused the texture references to be reasonable for the prop. I saved the prop to the library and restarted Poser. The prop loaded with textures in place, and the references look correct in the PP2 file. I created a polygon group and spawned a prop. The new prop was correctly textured.

I think the priority should be finding out why the materials are being lost in the first place. Have you tried saving the imported prop to the props library, deleting it from the scene, and loading the new prop from the library before spawning the components?

I wonder if Poser's oddball file search feature is causing you to load the wrong version of the dress half the time. Maybe try renaming the fitted dress something completely unique?