Rhino does it better but it has problems with reading external files so there is no win-win situation.
Does it have anything to do with colour spaces they work in?
I can’t comment on the native Rhino and Human components and the color differences, but what version of eleFront are you using and under what circumstances can you not see the color output? See below for the v5 eleFront and the v4 eleFront.
Objects are in the Active document and referenced. Version 5 “Get Rhino Attributes” component works as expected.
Objects are in the Active document and referenced. Version 4 “Get Rhino Attributes” component works as expected.
Objects are in an external file and referenced (not in active document). Version 5 “Get Rhino Attributes” component works as expected (requires objects to be in the Active document).
Objects are in an external file and referenced (not in active document). Version 5 of “eleFront Attributes” works as expected.
All my models are built on ONE layer, always with the same colour, marked ByLayer.
This layer is 242,242,242 as RBG or 0,0,95 as HSB.
There are some exemptions in colour and I am trying to track them.
Below is the list of the colours that Elefront reads compared to the other plugins:
from left to right: RHINO - HUMAN - ELEFRONT
I have no idea where 165,165,165 in Human comes from or 105,105,105 in Elefront.
Rhino show proper colour values. The problem with Rhino is highly unreliable Import3dm giving me constant errors where Human and Elefront are OK in this field.
For the time being I am stuck with Elefront V4. I can’t change it as it will affect many users in my team.
Perhaps you could DM me a file to check if you want. I ran some quick tests and I am getting the the correct, expected colors in the panel readout the v4 version of eleFront. It would be helpful to understand more about your particular situation to see what the issue may me.