The updated version 1.00n is significantly more stable, I tried out the scenes which gave me problems before and they all loaded without errors.
1.00n resolved the issue with meshes which have no uvs. But there is still an issue with meshes which are partially uv mapped, and we are testing a fix for that now. Should be available in the next day or so.
- the resolution in the Octane Render Setup window is sometimes different from Poser resolution (for example, an 800x600 scene translated into an 808x611). I'm still not sure if there is a specific reason for this or if I'm doing something wrong, but i happened a few times
You set the default resolutiion on the OctaneDefaults.py file. The installer has it set to 800x600. If you drag the size of the render viewport it will save the new resolution in the rendertarget node, and this will be saved with the scene and be the resolution the next time you open that scene. I just re-tested all the resolution functionality (although it was on 1.1) and it looked ok. If you get a reproduceable issue, let me know.
- if I make a figure or prop invisible, it is correctly not exported to Octane. But if I group figures and props under a Poser group item, and then I turn the group invisible (which means that all subitems disappear from the Poser scene), the contained items are still exported to Octane (probably because the scan routine evaluates the subitems even if the parent is invisible, which is right for all Poser objects except the groups)
This is a Poser error which I have reported to Smith Micro. To demonstrate, load Andy, load a box, parent the box to Andy's hand, make Andy invisible, open the Hierarchy window - you'll notice that whilst Andy is invisible, Andy's Body actor is still visible in the Hierarchy (and so is the box - so therefore OctaneRender thinks it's still visible). So to set the box invisible in OctaneRender, you need to set Andy Body invisible in the Hierarchy window (rather than ticking the Visible box on the Body actor).
- the last one is just a request : in the next release, would it be possible to make the Octane Render Setup window re-sizable? It would be convenient to have more space when working with a lot of items
I think that's a great idea and I'll add it to the list of potential enhancements. Probably won't make 1.1 (which is almost finalised).
All of these are really minor issues, I'm very happy with the plugin as it works now. I still have to experiment and get used to Octane materials, but overall this is a great product.
Yes - thankfully the plugin learning curve is small. But Octane offers so many features - there is a lot to take in. I've working with Octane for months now and still haven't touched many of the features (caustics, portals, all the cool lighting of interiors from sunlight thru windows, etc).