I don't think Paolo tried - I think he dismissed it out of hand.

First - if it was dismissed for speed reasons, this is not a valid reason. If I plan to render in Lux, it's because I expect it to do better than Poser. That means at least a 10 minute render, and more likely an 8 hour render. If the first step, export, takes 2 minutes, I hardly care. Poser takes 20 minutes at least to render a decent scene involving IDL and raytracing, and usually it needs much longer than that. In the end it won't be as good as the Lux overnight render.

I have many hundreds of nights where my computer does nothing at all. If I choose to run the exporter and render in Lux, then go to bed, I don't care if the export is 2 minutes, or even half an hour.

Second, suppose I care about speed and really want to use C++. Fine - from Python, call Poser's API to export the whole scene as an OBJ file. That exporter is built into Poser in C++. Using Python also, save all the material settings as material collections. Now everything is on disk. I write a C++ program to read the OBJ (for geometry) and the MC6 files (for materials). This is trivial.

---

Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)