Really excited to get my hands on this in the next couple of weeks, especially since it was thought to be the end of Poser 13 updates.
Fingers crossed that some of the bugs I reported are amount the many that will be fixed in this release.

Next Update to Poser 13.3 in Beta Testing

Some of you asked recently about the Poser 14 release date. While there is progress in this regard, there are not yet enough headline features to justify a major version release and meanwhile we have a backlog of completed bug fixes and smaller feature improvements.

This means there will be at least one more update to Poser 13.3 coming in the next couple of weeks with many bug fixes, small feature improvements and a few core code updates that are a necessary prior to a Poser 14 release.

 
It’s the perfect time to get Poser 13. Don't miss out - grab your discount today and unleash your creativity!
https://www.posersoftware.com/store/category/2/poser-software?aid=4

Good, always a good idea to release frequently so we can benefit if we want of the work done !

Great news, thanks !

Anyone know when this will be out? I've had a ticket open for a major bug for most of 2024.

I also just noticed in Poser 13 (Mac), if you click Help > Renderosity Community, it sends you to the Poser 11 forum. Not really a bug but hey it could maybe do with updating :)

I put that in as a bug report.

@dt00swc the issue you're talking about, I presume is the problem with strand hair messing up the preview and making it super slow.

It turns out that it's a problem in the dynamic hair library we use. We're waiting on a the developer of that library to fix it. It's not going to be in the next service release. I wish I could say it was fixed.

There are other Mac-only issues in that library and we may end up having to migrate to a different dynamic hair library as we did with the Talk Designer. (Which is an open source library now)

Again sorry for not having a solution yet.

Aha okay - well no problem, thanks Nerd3D for the response/update. It's good it's been identified as a legitimate bug, and narrowed down to the dynamic hair library, that gives me some hope of resolution.

And Redphantom - thanks for logging that one 👍

Got it, thank you !

13.3.824

I just wanted to say Thanks! I think this is the best version of Poser. Lightning-fast realistic Renders. Fewer crashes than ever before. The Team has done a fantastic job. 

Aha! Poser 13.3.895 is out, and there's something cool to check:
"Implemented displacement node for SuperFly materials. (App) #2234"

Aha! Poser 13.3.895 is out, and there's something cool to check:
"Implemented displacement node for SuperFly materials. (App) #2234"

Both the Cycles and PhysicalSurface root nodes already had displacement, so I'm curious what actually changed.

No, it actually is a displacement node. The other node that was introduced is a VectorDisplacement node.  Apparently, there is a difference.

Hmmm, I assume that's this? https://docs.blender.org/manual/en/latest/render/shader_nodes/vector/displacement.html and https://docs.blender.org/manual/en/latest/render/shader_nodes/vector/vector_displacement.html

That actually looks pretty useful. You could do scaling with a math node but it's a cleaner way to adjust the height and also you can shift the neutral point (I keep forgetting where it is).

I guess vector displacement is sort of equivalent to using normal maps where regular displacement is like using bump maps.

The displacement as implemented in the physical node was behaving weird ... wrong ... uspidebackwards? It's really hard to explain. Let's go with "Busted". It was actually  using the vector displace which is (evidently) supposed to be weird. At least it's the same kind of weird in Blender's implementation of Cycles. It makes the displacement all go in one direction instead of along the surface normal. So it does something, but it's definitely not what Poser users are expecting. The vanilla Displacement node is what you're expecting displacement to do.

The Displacement input on the Physical node now has a Displacement node built into it so it should behave more sensibly. If you are working with the Cycles root you should Put a Displacement node inline between the Displacement texture map and the root input.

Well, it is sobering to know that displacement for PBR was broken all along and finally got repaired.  The addition of a proper Displacement node was a long time in coming to Poser.  Now to go back and examine all the content transposed into physically-based reality, making the necessary repairs to make them render correctly.

Dis place meant to do it right de foist time, but dis place got it right now! (Sorry. Couldn't resist.)

Is this "actual" displacement like Firefly can, or does it still need the underlying mesh to be subdivided a gazillon times?

What Firefly does is essentially just localized subdivision. Even the Blender documentation (linked above) says "For best results when using true displacement, the mesh must be subdivided finely to bring out the detail in the displacement texture." It's still "actual" displacement.

how much you need to subdivide depends on the details of the displacement map. You aren't going to be able to use a noise node to make grass. I used a dirt map on the sphere without any subdivision and it looked as good as if I divided it a bunch.