14 month later: Is Rhino V8 finally useable for us? My table stakes list

R8 crashes every time I try to copy R7 button to R8 toolbar. And on different machines same buttons have different icons.

If this is repeatable, that is great news. Can you send me your R7 RUI file with some steps to repeat the crash?

Thanks

1 Like

@Mitya would it be possible to share your v7 toolbar so I can attempt to repeat this crash?

1 Like

Hi Steve, I’ve send it.

I just have send you a toolbar with a group, enabling which every time crashes Rhino.

hi McNeel team,

I’m still struggling a bit with toolbar migration. My 2 questions of the day:

  1. How do I import a toolbar into my .rui file?
    in V7 I did this…

in V8, I cannot figure out a way to add an existing toolbar saved somewhere else into my current .rui file:

  1. because I cannot import a toolbar, I figured I’d create a new one and start dragging one-by-one buttons (as copies) of other toolbar files. It’s very error-prone and laborious, but it’s a workaround. But doing that destroys the vector thumbnails. See video:

When will this be fixed?

Thanks,

G

1 Like

Did you try ā€œOpenā€ for the first item?

I’ll need to check on point #2.

Open will open a separate -RUI file, correct? I don’t want to have and then manage a bunch of separate ,RUI files.

I want to maintain just 2 .RUI files:

  • default.
  • my_toolbars.RUI

So any other custom toolbars needs to be imported INTO my_toolbars.RUI just like I can do in V7.

Makes sense?

G

Ok, so you are looking for some sort of merge functionality. I can look into adding this

Correct, clean merge. No dependencies or link to the .RUI file I previously imported. Just like in good old V7.

Thx!

G

1 Like

Thanks, I can repeat this crash and am working on a fix right now.

2 Likes

I experience much less crashes and freezes in rhino 8 than i did in Rhino 7. I actually couldn’t think of a time when R8 crashed on me since I started using it for a year.

This alone is a big incentive for us to switch from R7 to R8.

However, apart from the much stabler performance, there really isn’t much good to say about R8. For one , I am really not happy with all the bugs that I have encountered. We use Rhino for basically everything, especially drawing documentation, but I don’t see McNeel taking priority in fixing all the bugs and issues associated with printing and documentation, which disappoints me a lot.

The new UI is also atrocious. Some old UI feature from R7 is taken away. (E.g. Toolbar search, nice colors and easy docking) , and sometimes really buggy,( e.g. Toolbar opening at the corner, toolbar is unable to be exported, toolbar not showing in right click menu but do in options…)

we are well aware and working to try and address this. It was a big (and necessary) job to overhaul it and its a big job to fix all the issues that occurred from that over haul. We appreciate your patience, and I can assure you are are doing our best to address these issues.

please report the things that prevent you from getting your work done so we can push them to the top of the very long list of fixes.

4 Likes

Hi, I can maybe point you in the correct direction, but I had trouble actually using it - in V8, there is a distinction between toolbar and a container, and a toolbar can contain multiple containers.

I however don’t know if you can import toolbars from R7 as a R8 containers - I don’t think you can.

I had to edit my own post here because of this. :expressionless:

Please, let’s get some attention paid to this:

Hi @stevebaer, all,

Do you have any time estimates when these below can be fixed? fI really need them fix so I can keep trying to migrate to V8:

Thanks!

G

2 Likes

RH-85294 is fixed in Rhino 8 Service Release 16

1 Like

To be honest this feature hasn’t been on my radar. If this is the blocking feature for you, I can definitely switch over to working on this. I can never predict when this will be ā€œdoneā€, but it will sure be done a lot faster if I work on it than not at all.

Could you send me two RUI files that you would like to be able to merge? I can use this as a starting point for development.

1 Like

The merging is less important than the dragging copies of buttons and preserving their vector quality.

This will be my migration approach:

I have many V7 toolbars where 60-80% of the buttons are default tools/icons and only the rest are custom ones. I wants to recreate the toolbars based on copying new buttons from existing default V8 toolbars. And then whatever is custom/missing I will import/merge as tools to add and then I will recreate/draw those icons in V8.

The merging of toolbars needed depends of what icons I need to remake. Does that make sense?

G