Rhino 6 Release Candidate 1 Available

This is not slated for V6

SubD display in V6 still needs a lot of work and won’t be completed for the initial release of 6.0. We kept SubDFromMesh around because users needed it, but it is a “Test” command in Rhino 6.

We are investigating this issue this week.

Thank you

1 Like

Looks like that bug never got logged. I just logged it as https://mcneel.myjetbrains.com/youtrack/issue/RH-43457

This bug will be fixed in the first service release. An SR1 release candidate will go out almost immediately after 6.0 is released.

There are 7,549 open issues on our bug tracker logged toward Rhino for Windows. Almost none of them will be fixed before we ship Rhino 6.

@stevebaer @brian Sure i understand You have lots of work and i really appreciate that :slight_smile: I just thought it wouldn’t be that hard to fix cause afaik was last piece of achieving full dark ui experience i know there are more crucial things but this one would give few smiles on faces around :wink:

That might be true. There are probably another 500 issues on the list like that. It’s not about hard or easy, it’s about minimizing the changes we make as we try to stabilize Rhino for release.

This is a small thing but the ‘between’ option is missing on the one-shot Osnaps. Am I missing something here?

It should show when holding Shift, rather than Ctrl while hovering over the OSnap window.

Between is now with Shift and not Ctrl.

Such a basic thing has to wait for a SR?
Users will be impressed.
Especially when they want to upgrade from V5.


Am I missing something or is there no DevSrf panael?
I do find the DevLoft command but nothing on DevSrf.


DevLoft appears to be the replacement for DevSrf.

Wow I had no idea that functionality was there. Cool.

This per-object display mode bug with curves introduced in V6 is a major problem over here. I really hoped this could be fixed before V6 ships and now I just saw the fix is slated for 7.0 ???
Hope you can reconsider its priority.

The bugs in new functionalities are one thing, but things that worked well in past versions and work no more in V6 IMHO should be high on to-fix list.



I agree and didn’t realize this was a regression. I have moved this bug over to 6.x release target and will investigate.


@Jarek I see that you added an additional bug to the initial bug report. I need to split things like this up into two bugs in our system. Which part is the regression?

Oh, I see - sorry, I thought it is another result of the same bug.
The regression is, currently in V5 when we use SetObjectDisplayMode and assign a mode with XrayAllWires enabled, the curve objects are not Xraying (other object types do xray OK).
I illustrated it here:

Thanks, I’ll probably be able to fix both at the same time. I just needed to know what specific item you were referring to.

FWIW, the original RH-42692 is also a regression!

It’s worth a lot; thanks for letting me know