Poser's "Color Math" mystery for me


  • Poser Ambassadors

    Oh .. my .. God. It looks like the new developers have no idea what they're doing.

    Not only do we have situations where the color chip is used and the plugged in pattern ignored, we also have situation where the plugged in pattern is used and the color chip is ignored.

    I don't know what to say. This demonstrates a total lack of understanding of basic programming, as well as a complete abandonment of QA regression testing.

    0_1530614679747_16be98a4-f302-4d7a-81c2-33409bdf5690-image.png



  • @bagginsbill would that kind of treatment (admittedly faulty) perhaps stem from trying to handle existing nodes the way the SuperFly Cycles nodes treat in-node values being subsequently ignored (and not displayed) when a node is plugged into them?



  • @englishbob said in Poser's "Color Math" mystery for me:

    @Y-Phil Thanks! That explains why searching for 'blush map' didn't work. I must have passed over those downloads at the time.

    I have his original Easy Shader, which incidentally solves another search I had, which was for tan lines for V4. So double thank you!

    You're welcome
    0_1530617236852_aww.gif



  • @bagginsbill said in Poser's "Color Math" mystery for me:

    Oh .. my .. God. It looks like the new developers have no idea what they're doing.
    ...

    Before writing such insulting nonsense you should better make some tests. I tested this issue with Poser 11 SR2 and its already there.


  • Poser Ambassadors

    @nagra_00_ said in Poser's "Color Math" mystery for me:

    @bagginsbill said in Poser's "Color Math" mystery for me:

    Oh .. my .. God. It looks like the new developers have no idea what they're doing.
    ...

    Before writing such insulting nonsense you should better make some tests. I tested this issue with Poser 11 SR2 and its already there.

    It's not nonsense and your response is only adding to the confusion. I am 5 releases PAST sr2. The bug was not FIXED in SR2, it was ADDED after SR2. Not sure which, but probably the 11.1 release (you are on 11.0.2)



  • It's not nonsense and your response is only adding to the confusion. I am 5 releases PAST sr2. The bug was not FIXED in SR2, it was ADDED after SR2. Not sure which, but probably the 11.1 release (you are on 11.0.2)

    I tested it with SR2, SR7 and 11.1 all have the same issue.


  • Poser Ambassadors

    So you think the old developers did it? If so then the old developers didn't know what they're doing. Either way it's a pretty egregious mistake that should have been caught in QA.


  • Poser Ambassadors

    Workstation Urania is Win7Pro-64 and P11Pro version is 11.0.8.34338.

    The bug is present in build 34338 (SR8).

    Interestingly, with the color saturation at 240, the preview engine displays correctly, though Superfly renders with red all over. I used a B&W mask w gamma=1.

    As long as the saturation is <240, it works correctly. With saturation = 238, it's OK. I couldn't check saturation=239 because Poser keeps changing the saturation to 240 if I enter 239. (Enter 239, click OK, re-open color picker, and the saturation shows as 240).



  • SR3 (32055) - bug exists in Firefly Color Math node, not exists in Cycles Mix node. (Well, now I know how I missed it before...)



  • Seems like the bug exists in SF only! i.e. if FF engine is active, both preview and render work as should.



  • And this bug exists since 11.0.0.31047 at least.



  • And to be sure: is the bug already reported?



  • There are a few reports that revolve around it.

    Hmm...


  • Poser Ambassadors

    I took me a while to find it. I have no memory of this.

    I reported this exact problem April 12, 2016, more than 2 years ago. It is bug report #37624 for those who can access mantis.

    "SuperFly Material - Blender ignores attached nodes if color has a 0 in it"

    "A Blender ignores attached input node data if its color chip has a color with a 0 in any component, for example RGB 255, 0, 0. It behaves correctly with RGB 255, 1, 1, but change any component to 0 and it ignores the input node."

    This is the screen shot I included with the bug report:

    0_1530645363406_b3da1bf6-d912-441a-b554-f6080f9f7861-image.png

    "Connect any pattern node to blender color input set to RGB x, y, 0 or RGB 0, x, y or RGB x, 0, y. The pattern is ignored."

    I did not bother testing other nodes but we see now that it is also a problem in some other nodes.

    It was assigned to Stefan and targeted for a fix in SR4. Then they all got fired.


  • Poser Ambassadors

    It is still marked high priority, serious, and open to this day. Not a good thing.


  • Poser Ambassadors

    Correction but I can't edit now (because reasons)

    The date I reported it was April 9, 2016. The last update on it of any kind was April 12.