Getting Ready for Rhino V8

[MichaelDonn]

Kia ora

I may have encountered an issue with the icon labels that provides an indication of a reason for some of the occurrences of this label:

• when debugging the installation for an Apple computer user I encountered (still) some people who did not follow the instructions about unzipping the Python file!
• I then noted, that the most common action of an Apple Computer user when asked to unzip a file is just to double-click it: if, as most of my students do, you have still a copy of the Python folder from last year in the directory, it is not over-written, but a second <Python(1)> folder is created and populated
• the result for these people was EVERY icon was “OLD”

I wonder whether my desire to have Rhino 7 and 8 on my Windows computer may have created a similar issue?

M

[chris]

Sorry for the late response here, @Asisnath and @MichaelDonn ,

As Mostapha said, the bug was already reported to McNeel and it has been fixed in Rhino 8.5 as @tay.0 noted.

Here’s the full record of this issue:

Rhino 8.3 Error When Using Legacy GHPython for the First Time

And note that there’s an easy way to work around it if you still have an older Rhino 8 installed. You just need to disable and re-enable the component.

[MichaelDonn]

Thanks for this.

I am already working with the Mac/Apple O/S users and being tidy about unzipping Python files…

[chris]

Just to give an official answer to this:

@MahaShalaby

Will the legacy version be updated so that it is compatible with version 8 and runs correctly?

No, it won’t. Technically, Legacy had some issues that were never resolved with Rhino 7 but it’s officially deprecated for Rhino 8 and you should not use it there, especially now that LBT has practically all of the Legacy functionalities (plus several new capabilities that Legacy never had).

Along these lines, we also just added a new “Legacy Updater” component that drops the equivalent LBT component if you have Legacy components on the canvas:

The component is available now with the LB Versioner and it will be in the LBT 1.8 release that should hopefully be happening this week.

So time to update ! And if you sense any ambiguity about how something has changed between Legacy and LBT, just open a topic on the forum and I’ll happily advise.

[Korgaard]

Are there anything liket this for HB-Radiance plugin as well.

At the moment I am using rhino 8 with the 1.7 version of Ladybug. While calculating my HB annual Daylight I get an error saying “Solution exception: WindowsError”.

Is this due to the version being to old or is there any other fix?

[chris]

Hi @Korgaard ,

This is your issue:

@Korgaard

At the moment I am using rhino 8 with the 1.7 version of Ladybug

If you want to use Rhino 8, you must use LBT 1.8 (or above). There were several changes that we had to make to the components that run simulations so that they do not conflict with the new Rhino 8 scripting environment. So just update and you should be good.