That quote is from a few days ago. Yes, over the Labor day weekend, when my daughter was visiting before going off to college, I took a break from work and from Poser and we were all playing with the iPad and enjoying each other's company.

I'm completely burned out due to weeks of lack of sleep. Now it's Wednesday and I have another product demo to due tomorrow and I don't have time at the moment to play with Poser.

I've done a ton of stuff with the exporter, but seeing how things got a little wonky what with people expecting it to do more than it was capable of, I feel really uncomfortable publishing anything half-assed.

There is a desire to use IBL. adp did some work there, but it requires more complex handling that I don't have time to fix.

We want the app server included, and I have it running, but structurally it is a little bit ugly and I have some small amount of refining to do. As well, I have to integrate adp's sub-classing of the Poser object so that it can run safely in the background all day even if you run other Python scripts that steal the scene event callback. The way it is right now, if you're running on Poser 8 or Pro 2010, it uses a wxTimer - that's new in the past couple weeks. But if you're on Poser 7 or 6, it has to use the scene event callback and it will, but if you run some other script it will mysteriously stop. I do not want to debug that with people. So it will wait until I have time to make it foolproof.

The spotlight export falloff isn't right and never was. I have to figure that out before I publish another set of light exporters.

The ambient power issue we ran into still needs investigation. I saw the post saying that setting "power" or "efficiency" to 0 will disable the power scaling with size, but when I tried it, it didn't work.

There were issues with the AIR installer, and I have it working without installing (I think) for Windows, but not for Mac. I have a Mac to try things with but it is terribly slow and I spent hours with it not getting the info I wanted. It will take me at least another 10 hours to figure out how to deal with a not-installed AIR GUI on the Mac.

I also have to make that work in Linux. Don't know how.

The light group prefix hack seems not a winner, so I have to put the per-light GUI in and let you set the light groups in LuxPose so you won't have to change your scene light names.

Overriding the per-material settings is necessary and I have to build the GUI, the server callbacks, and the business logic to deal with that as well.

I don't want any more confusion about black renders, so I feel I need to assemble a few reference scenes so that there is no confusion by new users as to what is happening or not happening.

The light gain factors are not consistent across different integrators and I know that adjustment is needed but I haven't figured out exactly what that adjustment is.

I proposed using the Sun+Sky option, which I implemented (which required that I rotate the world). But since then the geometry exporter has been updated so I'll need to go into it an re-apply the changes to odf's newer code so as to again rotate the world. There was also the request to separate sun and sky as independant options. Since that changes the data model, and since I'm trying to publish an exporter that supports presets, I have to decide the final data model first. Otherwise, all the sun and sky presets will be useless. 

There are other similar niggling issues.

In other words, I've already put another 90 hours or so into LuxPose since my last publication of anything, but since I see how it gets used, I'm not going to publish any of this until the rest of the changes I described above are finished. That could take another 40 to 100 hours. I don't have that much time.

I do have enough time to answer Syyd because I owed her one. (There were other conversations in PM that you're not aware of, nor should you be.)

---

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)