Very good looking indeed.

Please allow a constructive comment : The thigh/hip joint needs some work in side/side rigging. => Visible in the both nude pictures.

Best of luck with your projects. Tony

Cloth room and fitting room could be combined but for that to succeed properly Poser needs to go to single vertex group figures and single vertex group clothing..

Current Fitting room situation is like this. => The clothing puts you on. => The clothing has controlled shrinking to figure, and gets your rigging. => Result, the clothing puts you on.

Later I also filed another enhancement report about => You put on your clothing. => Hard to explain in a few words, but a reverse or a live Fitting room. => But that did not make it.

I filed a demo of a fully rigged single vertex group clothing. I also filed a demo of a fully rigged single vertex group figure because I truly believe that's the future.

Poser can do many things Blender can not do, and Blender does some things Poser can not do.

Together, thy are the best combination possible. Add Krita to the list, and you don't need anything else.

The 3 Musketeers. One for all, and all for one. LOL.

A GoB (GoBlender) was asked for but no-go yet. => So the "fix" is in my first and second video on my YouTube channel; Tony Vilters Poser2Blender2Poser. 7 video's total but one and two are about this.

Ach, my weak spot. rendering.

I am a tech guy too and rendering is probably my weakest spot. Nah, pretty sure it is my weakest spot.

Obj files and rigging quality and "inventing" workflows are on my list.

The fitting room was my idea, my baby, as are dynamic hair lashes, that kind of stuff.

I got the idea from one of Posers greatest men around. Remember PhilC? He was a great guy.

He had a demo video where he used a combination of conforming 'rigged) and dynamic clothing, so he could rig the conforming part, let the dynamic simulation do the draping and then use ghost bones to get further movement in the draped cloth.

He also had a video about how to get plies in a dynamic draped clothing, but that was by using a morph after the simm. Sorry, but I don't remember the details exactly; and PhilC moved on towards other hobbies. Woodturning if I am not mistaken.

At the time I had other priorities, so I did not look in detail at the exact workflow, but it was a very interesting project.

Best regards, Tony

@Afrodite Have you ever tried to morph figures or clothes using the rigging?

I do both : Morph the figure using the rig (biceps, triceps all muscles that are "inline" and move in or out only are game), and morph clothing movements using the clothing rigging.

I am very flexible with whatever the release system but 2 things will KILL an app like Poser. => And by "kill" I mean : Level it to the ground and deeper. LOL.

• Subscription, that is a definite No-No.
• Cloud based. Even worse.

Pricing has become a delicate balancing act because DS is free, and let us be honest, they have the best content.

Blender is also free and about a couple of years more advanced in technology by now. One can walk in and out of Blender with obj files and maintain obj file quality (something that is impossible in Poser because Posers obj file handling is a very old MAX heritage).

Blender has Eevee, (really, at first I thought is was going to be a hype, but man oh man, that thing flies,) and it has some of the best rigging systems too.

I only hope they get the right people to pull it off, and what Renderosity needs right now are the most agressieve and tech savvy beta testers possible and LISTEN to them.

Content, content, content, 3D is all about content. You can build the best and most stable app of the Universe? ? DAZ and others will run with the money because of the content.

Oh, on that point, I agree completely BB;

The reason behind the quote ; " nodes and nodes and nodes" is that most end users keep adding and adding and adding, often creating contradicting calculations, without understanding what they do.

And as far as my test-figures go : I repeated on several occasions that they are test-figures, nothing less, but certainly nothing more.

The obj files, the riggings, the textures, the nodes ? ? ALL of them change almost on a daily basis, and every 6 months they get deleted and rebuild from the ground up.

Well, no clue what a BMW or a Volvo are doing here. LOL.

I used to own 2 private airplanes (Sold both due to age); A Jodel D-120A the OO-FDP a 95hp 2 seater, and a MS - 894 the OO-CCB a 235hp 4-5 seater.

The first currently in the UK and the second currently in maintenance in the Netherlands. Do they count? LOL. Oh, and a car, and a 4x4 quad, and a motorcycle, and 8 bicycles. + Why not, some roller blades. LOL.

Best way that I have found, and this has been discussed in the past, it to use Poser hair room lashes and brows because they always follow the underlying geometry. => In the hair room you can "grow hair" directly on the original geometry.

We had many examples in the now "gone" RDNA forum. Some of those test results are on my old PC if I am not mistaking.

The only thing that kept us from continuing was a well known Poser bug. => Yep, it is 31615 again.

When you save a figure with hair grown directly on its geometry, Poser splits all vertex groups into individuals creating double vertex at all welds when saving.

Ach, it is all a balance.

Right now Windows is the most used OS and that is the reason why most hacking, and personal information stealing apps are for Windows.

When Mac OS or Linux get as much or more end users then Windows, all hacking and stealing apps will come your way too. It is just a matter of time actually.

Stealing apps shift as soon as the end users shift. => Hey, information is money.

Light is what you see bouncing around and the calculations can not be seen, but have to be calculated.

Render speed is all about the amount of math behind the scene to get to the end result.

Speeding up render times is actually quite easy if you remember that everything you add has to be calculated.

I see some adding nodes and nodes and nodes, but remember. . . . . Everything you add has to be calculated.

Same goes for polycount, number of material zones, number and size of textures, number and type of lights.

And if you use the "modern" PBR workflow with older content, please remove all old "cheating nodes" when it is render time.

Many have proved that all content renders pretty good with very few nodes.

Less calculations to perform, and avoiding contradicting calculations speeds renders up.

In the end? Each rendered pixel has just a single R,G,B, value, and the pixel does not care where that came from.

Hi Eric, I see that you use Displacement. SuperFly does Displacement on vertex level and not on pixel level as FireFly does.

Propose to connect to the Bump channel that works on pixel level in both render engines.

I am very happy that Larry (the creator of this great app) and Stephen and BB for the render engines, and Deecey to get the quality manuals, are back to get Poser going forward. Looking forward to what they have planned.

Best regards, and have a good week all.