On Rhino 8 SR24, Extreme component seems to output the exact opposite?
Extreme.gh (11.9 KB)
Thank you for you report, I’m seeing this as well. I have logged this issue with our development engineers
RH-90027 Grasshopper: Rhino 8 GH Extreme component bug
1 Like
Hi Jessesn,
Do you know when will the new version be released? This breaks everything in my script and there were too many instances of it to be replaced.
Edit: If it’s more than a week away, can you please send me a link to install the most recent version where this issue does not exist? Thanks
Sure, and I have sent a download link to you via DM. Thank you.
RH-90027 is fixed in Rhino 8 Service Release 26
Hi Brian!
Can I assume that this change will be integrated in its current form into the coming service releases?
I have reworked all the definitions we use to the new behaviour (as in the release candidates), but would like to go back to the normal service releases. The latest service release (.11001) still has a different behavior from the last couple of service releases.
I just want to make sure which behaviour the component will have in the future, so I can know which version of my definitions to share with my team (with our without switched outputs) 
Hi Isak -
Yes.
If all goes well, SR 26 will be released tomorrow.
-wim