Just for curiosity what antivirus / malwear / security / firewall thing do you use? I want to be sure there's not a real issue lurking here.

That's a pretty common request. And it's not that we haven't heard you. It's just a lot more complicated than it sounds. We basically need a new type of material that doesn't replace the existing material. That's the easy part. Making it so the partial material actually knows what parts to replace, what parts to leave alone and where any new new bits are to be connected ... that's probably going to need an ESP mind probe. Who's up for a Poser brain implant?

No. The RTX 30 series (Ampere architecture) was introduced several years after Poser 11 development ended. The newest GPU supported for SuperFly rendering in P11 will the the GTX 20 series.(Turing architecture.)

The 30xx and 40xx series are supported in Poser 13

Poser 12 just needs to periodically contact the license server to renew the lease. Just let poser go on the internet. You don't need to buy a new version. All Poser 12 license are perpetual.

Open a support ticket and we will fix this for you. https://support.posersoftware.com

Yeah I wish it worked that way too. Dials get numbers. No percent, no degrees or on-off or any other decorations. The best you can do is change the dial descriptions so the numbers make sense. Name the dial "Some Setting  Off <==> ON". Then set it's limits to 0-1 and the sensitivity to 1. An example of this is the "Hide <- Control Handles -> Show" for the control handles on LaFemme. That's about as fancy as it gets. And yes it's been requested. Maybe someday.

I should share with all of you a little part of this saga. The fix for gamma shifting did indeed break something else. That happens a lot and I've come to expect it. So now the fixed fix for the original fix is fixed and in testing, AGAIN Again again a.... .....

I should add here that the shadow catcher setup may seem a little weird. The option to enable shadow catching in on the Poser Surface node for both FF and SF. And, In SUperFly enabling it on any material of an object will turn the entire thing into a shadow catcher. This is because in Tempest (aka FireFly) shadow catcher is a property of a material. In Cycles (aka SuperFly) shadow catcher is a property of an object. We implemented so it was mostly the same as users were familiar with the FireFly shadow catcher.

SO I came up with this one it's kind of works in FF but It's much closer to what seems to be the objective when I render it in SuperFly.

SuperFly

It kinda works in FireFly ...

Just so all of you all know a fix for pixel and gamma shift at the end of renders is in testing. It will be released as soon as it's received an adequate test cycle and as long as it doesn't break something else.

Watch for the update notices in Poser.

Go to https://support.posersoftware.com Create a support ticket. We can lookup your serial based on where you placed your order and the email address.

Rendered the same scene FireFly in P11 and P13. The saved images are identical. If you're seeing a difference in JPG. Well that's JPG. It's just lossy format.

The tear-off not getting preview render is already being worked on. That will be fixed on a service release. Probably not the next one as it's "eminent" and I don't want to accidentally break something by sneaking something in after it's in testing.

The pixel shift from FireFly renders is ... squirmy. I may need some detailed input here. I've taken a screen grab from just before the render completes overlaid it on the saved image from the same render. They're pixel perfect except for the render dialog ...

This leads me to believe the pixel shift is just that the final image isn't displaying correctly in the Poser. I need to be sure I'm chasing the right bug here. I'd appreciate if those of you seeing this could try the same thing and see if it's just the image display in Poser. I don't want to send the coders on a snipe hunt.

On the Top Menu go to Poser > General Preferences ...

ON the Interface tab put the dot on Launch to factory state.

[OK]

Exit and restart poser.

That gets you back to the factory UI. You can safely return the preference to "Launch to previous state" in preferences.

Now how to make sure this never happens again ...

Every room in poser has a set of memory dots. Among other things they store the UI layout for that room.

A Dark dot is empty.

A light dot contains a stored layout

A blue dot is the layout that's applied.

Click a dark dot to store a layout

Click a light dot to load a layout.

[ALT] + Click a dot to erase what's stored in it.

Once you've reset your UI you should store the factory UI in one of the dots.If it ever gets messed up a gain your one click from the factory layout. Then arrange your pallets to your liking and store that in another Memory Dot. Next thing you know you'll be storing different UI arrangements for different tasks.

Every thing about Memory Dots: https://www.posersoftware.com/documentation/12/index.htm#t=Poser_Reference_Manual%2FBuildingScenes%2FPoseRoom%2FMemory_Dots.htm&rhsearch=memory%20dots&rhhlterm=memory%20dots%20dot

This is a bug that was present through the entire run of Poser 12. It went unnoticed until Poser 12 development ended. It has been fixed for Poser 13 but that doesn't help you. There is a work around but it's a bit cumbersome.

The failure was in the way lights store the animation data for the color and intensity of lights. First is to delete the light, recreate it and set the color before you render the scene with that light present.

Next if you have already rendered the scene you can usually "jiggle the right lose wire" by disabling the Animation on the light's shader node in the material room. Select the light and click the little key icon next to the color and intensity icons and remove the check from Animated..

This will cause poser to re-generate the shader nodes for the colors of the light. It won't stay fixed because the animation will pop back on as soon as you render the scene. (Because the way lights colors animate is totally borked in P12.)

So if you change a light's color and it doesn't respond in a render first try toggling off the animated key in mat room. If that doesn't work try deleting an recreating the light.

This only really affects color lights. if the light is a white it doesn't proc the bug. That's probably how it went unnoticed for so long.

Hope this helps.

Mirror function on the Morph Tool ...

To copy morphs between figures load both in a scene. Select the target figure and Figure > Copy Morphs From ...