You'd be surprised how many polys Poser can handle

i7, RTX2070. With more than ~3-5 millions poly its already hard to move the camera around the scene. With 10-12 million polys - framerate is somewhere around 0,05 frames per second when you try to move the camera or pose a figure. You can easily reach such numbers while building a forest or city etc.

Hi, I remember I had this problem once when experimenting with a hard surface model. Try setting the "crease angle" to zero. See images below: model in Houdini, model in Poser (crease default), model in Poser (crease 0).

That would make the problem worse. Yea, flat surfaces would be flat, but round details would be flat too

primorge posted at 8:38 AM Thu, 16 May 2024 - #4484825

Did you try adding Poser Subdivision?

Subdivision is not solution. Poser works very bad with alot of polygons on the scene, so everything must be as much lowpoly as possible. Plus Poser doesnt have instancing for props, so more geometry eats more memory, and sometimes you wont be able to render the scene just because of too much geometry. Also not many models have topology optimized for subdivision, so again, you'll have to rework the geometry manually

I really hope devs would add instances someday. Without instancing its impossible to render big high quality nature\forest scenes.

And Color management like in Blender, without it its sometimes hard to render interior which has indirect light sources

I still use Aiko3 because of LittleFox's "Melody" too. Best figure to make a catgirl