Only Poser 12/13 are now supported with the current version of Octane.

Poser 12 changed to a newer version of Python and the Poser plugin has been updated to support that.

I have used Octane since it was released as beta and am very happy with it.

Poser 13/Superfly has caught up with regards to speed, but lacks some features which I really like such as cloning, easier material layers, better HDRI support, micro displacement,  VDB support (cloud data), etc.

Thalek posted at 2:36 AM Mon, 22 May 2023 - #4466109

Y-Phil posted at 1:53 AM Mon, 22 May 2023 - #4466106

Thalek posted at 1:38 AM Mon, 22 May 2023 - #4466104

Did you checked Win10's Events journal? you may find a hint. Or maybe the support could help you if it is about more "intimate" () things proper to Poser 

Haven't checked the events journal, can't consult Rocketship's support, and haven't consulted Microsoft support.  And PzDB is a standalone.  I can drop selections on Poser, but it doesn't need Poser to be running for me to use the database.  I can confidently assert that the problem is unrelated to Poser as I haven't even turned it on the last several days while I concentrate.

It's one of the reasons you guys haven't had any of my renders inflicted on you lately.

I have gone back to Poser Search, which is pretty fast and with the exclude option (- preceding the exclusion) is pretty usable now.

Setting up your content to be able to access it from multiple computers can easily be done by sharing the content folder on a local network. The only additional requirement is to access that share as a network drive (Map Network Drive from file manager). Now you can add that runtime to your Poser library.

I you also want to use the same scenes files on both computers, you heed to have the mapped network drive letter to be the same on both computers.

Thanks and gratulations to the other artists!

Thank you Wim. Yes, this does partially illustrate (if not explain) why the lighting is different, but in no way helps me in determining a conversion formula, leaving me simply to eyeball it. Worse still, his approach of test rendering EVERY SINGLE SCENE with multiple settings is ridiculously impractical, AND Poser does not allow you to separate out the channels to see the impact in detail like Blender does. But thank you anyway.

It does not give a formula - correct. It does show however which bounce settings are important. It also shows you that a formula is rather difficult to determine since the branch path and non branched path renderers acting differently depending on the nodes used (blend for glossy/diffuse for instance). But the main reason I showed the video link is to explain the difference in light bounces.

I do support you with wanting to have additional render layers for spec, light, shadow, indirect light, etc. Those are very helpful.

Branched and non-branched path renders use a different approach and they also treat materials differently. Blender - Branched path tracing explained shows the difference between the two and what influence the sample and bounce settings have on each.

Another way to do it is to create a null figure (load cube, enter setup room, leave setup room) and parent the table and chairs to the null figure, hide the cube. Now duplicate as many as you like.

I had a sudden slowdown as well (P11 and P12). It turned out to be scene related - when I load that scene, Poser went into slowdown mode (giving you a second, then seemed to freeze waking up for a second and freeze again). I then started to delete the figures in the scene and after deleting the 2nd one, suddenly the problem was gone. Funny thing was that when i did an undo of the deleted figures, the problem did not reappear and I was able to save that scene under a new name. The new scene did not have the problem.

It looks like in my case there was some corruption whicb was cleared when I did the Delete and Undo delete. If the problem happens when you start up, it might be an idea to see if it happens with factory default preferred scene as well.

Y-Phil posted at 12:33AM Thu, 21 January 2021 - #4410695

ChromeStar posted at 3:39AM Tue, 19 January 2021 - #4410676

Ah, that's the easy answer I was hoping for. :) I made the material invisible but did not hide the body part. That did fix it. Thanks!

You're welcome :-)

I don't why, but Vic4's eyebrows remain a curious problem.

That being said, I'm using Sasha-16, a weightmapped version of Vic4, and I'm truly happy with. Most clothes are almost straightly conformable. Sometimes, a few slight adjustments, sometimes weird effects near the shoulders/arms but easily manageable.

And the eyebrows hidden by default... :D

The weird effects on the shoulders in clothes is easily fixed in the joint editor:

• Pose the figure with clothes on
• Select in the cloth the LeftShoulder
• Open joint editor
• Select up-down in the joint editor
• Select the innerMatSphere in the parameter window of the cloth
• Increase the zScale from 3% to 4%^
• Do the same for the right shoulder.

In some poses you need to do this for the Front-Back as well. Once done, it usually works for other poses as well. It looks complicated, but takes just a few seconds

excellent explanation! Working with PBR makes transitions between render engines a lot easier as well.

it works fine in Poser 12

Thanks for choosing my image as pick of the week. Congratualtions to the other artists as well!

Thank you for choosing my image for one ot the poser staff picks of this week! Congratulations to all other winners!

In general preferences change UI scaling to 1.5, that will solve that problem

Thanks for selecting my ladies night for being in the staff picks!