Version 8 SR11, Grasshopper Player buggy. Restore previous Version

Hello everyone,

Yesterday I´ve updated to the latest service release Version 8 SR11 (8.11.24254.15001, 2024-09-10).
I´ve noticed that my GH defintions don´t work as before, when I run them through Grasshopper Player.
Running the GH definitions without Grasshopper Player seems to be fine.

As I need to finish some work, It would be nice to be able to restore the previous version of Rhino for the time being.
Is there a way to “downgrade”?

Thanks!

Kind regards,
Dominik

1 Like

Update:

The issue could be related to the ContentCache component + GrasshopperPlayer, as other gh definitions without ContentCache seem to be fine.

1 Like

Update:

Previously the GetGeometry component didn´t break the link to the model object.
Now it apperently does.

1 Like

Please also see an attached example gh definiton and 3dm file for debugging.

GrasshopperPlayerBugV8SR11.gh (13.9 KB)
GrasshopperPlayerBugV8SR11.3dm (467.8 KB)

What version were you on before? I rolled back to 8.9 and didn’t see a change.

I was using V8 SR10.
I found a way yesterday to downgrade to V8 SR10 and the GH Player worked again as usual.

1 Like

Hi @Dominik_Wrigley-Simo,

This will be fixed on 8.12.

Hi @kike,

thanks for answering. I´m glad to hear that :slight_smile:

Why was it broken in R8.11? Don’t you realize that people have paid money for this code?

Yet long after the official release almost a year ago, the product is still buggy. Even worse, new bugs like this appear? What in the world is going on :interrobang: It’s so very wrong.

You’ve been around here longer than most, how many bugs have been created/fixed since grasshopper was first released?

Granted, whack-a-mole bugs are frustrating for everyone but are fixed quickly when they pop up.

Should a lot of features been pushed to WIP 9 instead of 8 in favor of stability? absolutely, but risks were taken to push things forward, just like in previous releases. I, like most, want the new features and stability, but making the complex simple is rarely straight forward, it’s an iterative process (like building an efficient gh definition). We can only trust the process and learn from the mistakes.

I also had a long career as a programmer and have never seen such a screwed up process that produces so many bugs, especially in R8. It’s disgraceful.

Hey everyone, I thought this might be related to this topic.

Since the update (a couple of days ago) to Rhino 8.11 I am receiving a grasshopper breakpoint for all of my grasshopper components

Here one example:

That happens also for:

  • FieldCOmponents
  • GalapagosComponents
  • IOcomponents
  • Kangaroo2Component
  • MathComponents
  • RhinoCodePluginGH
  • ScriptComponents
  • SurfaceComponents
  • TriangulationComponents
  • VectorComponents
  • XformComponents
  • GhPython components

That is, almost all of my grasshopper components.So now my grasshopper is looking a little sad like this (and impossible to work):

I know the image shows the breakpoint from version 8.12 to version 8.11 but this was just my last trial to see if in the service release this was solved, but apparently not. I have the exact same issue with version 8.10 to version 8.11

I haven’t really seen anyone complaining about this exact same issue so I’m just wondering if it’s only me?
This is installed on my private machine and I have admin rights and there are no company rules in this.

Now my question for now is: How do I find the rhino 8.10 version so I can roll back to it?

In this case the version that resolves the issue is 8.12.24268.13001

Hi, just a quick, literally minor, correction:

The version you sent me is 8.12.24269.13001 and does solve the issue, but the current service release candidate 8.12.24268.13001, that I download today previously, didn’t.

2 Likes

Hi @natasha.catunda,

This is issue is not related to any specific version of Rhino, it is an issue with the installer.
It looks like Rhino was loaded but Grasshopper was not while the installer was trying to update certain files.
Apparently Grasshopper files were updated but not Rhino files, this is why you get the error message you shared.

Do you remember if the installer asked you to restart Windows before using Rhino?