ghostship2 posted at 11:34PM Sun, 08 November 2020 - #4403849

As I pointed out in another thread, The post effects check box has a bug. You get post effects on a new file even though it is not checked. You have to toggle it on then off to turn it off.

Toggle?? How? Do that in the SuperFly settings, then go do render in FireFly? Trying that, but it's ON already by default, I guess. Good Golly! It worked! Have to close the settings page, then reopen it. Your suggestion is the ONLY thing I've tried that actually worked. After I get calmed down I will install build .276. And I only have one render done, best do some more to be sure I got it right. :)

this is render in background; that IS part of the render.

For no reason I can find, Poser 12 has turned that "post fx" appearing thing ON by itself, no warning. I suddenly see 'render pass 1 of 3' when it should be 1 of 2. And only if SSS is being used, correct? I have found nothing in the manual yet that explains this post render lighting change for FIREFLY. Well, it is doing the same thing in SuperFly too. Settings seem to show all effects are OFF. And it is still doing this. The finished image does look like this. Then suddenly the "system" (P12 system?) takes over, cannot interrupt it without hitting RESET (shudder). When THIS is completed, the Outer Limits returns control of the system to me.
Went to Poser Support site, created an account (again), and opened a new ticket for P12 and this issue.

Progress!

They spoke to this very recently somewhere. Either in the Readme for P12 or the mailout, I'll have to go find that. Anyway, they said they will not require the old P11 License Key to provide the Upgrade Path. And when I registered P12 it did not ask for a previous versions key. It just went ahead and upgraded. But to even get the upgrade in the Renderosity Store I had to provide that key to show eligibility FOR the Upgrade. They even said we'd be able to go back and forth with both versions. It is expected and allowed. Yaaay! No guilty conscience! :D

Ok, have tried all your suggestions folks, and I appreciate all of them. Nothing helped, P12 wasn't responding where it came to THAT issue. And as I mentioned, ALL renders of any kind regardless of engine used or settings selected this one POST effect was being ran and applied to every render. And it blew out the image with brightness. So, unable to stop that, I did the good ol UNinstall/REinstall of the software. That did the trick, that worked. I can now get renders as expected from both FireFly and SuperFly, I can use POST Effects in SuperFly fine and they only apply as expected for THAT render. I now think my cat Mogwai was the cause of the problem. Well I can't think of anything else! THIS problem is now resolved.
We will be looking forward to PY scripts to be updated along the way. All in good time, and a huge thanks to all who are doing that!

Thanks Royston! That's great news. I have Ralf's XL, and would love to try the updated version out!

Ah no worries on that bit; found em and installing the new P12 items now to check em out :o) And, thank you for all those freebies folks!

I don't want it put where you want it put.

I got flustered, and with no answers to this issue I did the Last Resort: Uninstall/Reinstall. And now its rendering in FF and SuperFly both, and I have not touched that scary little button in the Render screen! I dunno, maybe my cat rolled on the keyboard in some way that affected the program. I want to add, P12 has yet to crash no matter what I did to it. Solid as a rock. Which is very cool :o)

@ Y-Phil, ghostman ; working on other settings that should NOT affect that but might be. Got a single V4 Mick rendered using 'render over current bg shader' and it didn't activate that POST thing. It did both of these without hooking POST. I am leery of clicking that symbol in the render screen, that might be what sticks it on.

Yeah I did Ghostman. I am aware it is a "Yah We Idiots are paying you so I can be a guinea pig!" early release. When I said it isn't quite as bad as P8 was on release day I wasn't kidding one bit. This POST FX thing isn't its only issue. Just the worst immediate one. And as I am using FireFly why is it even doing it! Its supposed to be superfly only!

Oh right. It is ShaderWorksMetadata Builder, not a major one?

@ Haruchai - check the Scripts Menu dropdown for new versions of ShaderWorks scripts. I saw that folder being installed earlier.

I don't suppose we can get a copy of the Python 3 interpreter?