We’re not adding any new features, nor are we making significant changes to the UI. We’re also done breaking the APIs, so plug-ins written for this Beta will work in the commercial release of Rhino 6.
I used the link “Download Rhino 6 Release Candidate now!”. The download page indicated it was a beta. This is what was downloaded:
rhino_en-us_6.0.18012.13241.exe
That is the BETA. You should have received an email with your BETA license key after downloading. Shortly, the BETA links will become Evaluation download links instead.
So, I’m on Beta v6 Release Candidate 1 right now. As far as I know, its evaluation period end is not imminent. But if I go v6 Candidate 2, does that mean past April 22nd, I won’t be able to save my work? Will Candidate 1 be able to open it?
I’m using this in a production setting (I know it’s at my own peril) and want to make sure I don’t mess myself up by updating software.
I plan on updating to the full version of Rhino6 when it becomes avail, but in the meantime need to make sure I’m fully capable of working, saving, opening, etc.
A couple more words than Nathan: we’re currently trying to get it to run well, without crashing. When we get it stable, we’ll release a WIP. Then, we’ll be getting all the new V6 Windows features running on the Mac, and we’ll ship. I have no idea how long it will take. No promises here
Since I’ve updated to v6 Release Candidate 2, I’m finding that Control-Shift Selecting individual objects in a group is very slow. Sometimes a 1/4 Beat, sometimes as slow as a full second. Very odd.
ALSO: When I delete something with multiple crvs, in a decent-sized file (24mb) they delete crv-by-crv. Like an animation of them deleting.
Sometimes bugs get introduced into Rhino related to the properties panel, or other panels that dock. I wonder if you close some of those panels if things speed up (and the objects delete more quickly). If you can figure out which panels cause the slowdown (if, in fact, my theory holds any water) then it should be easy for us to fix the problem.
Also, and this is a real problem, when I double click into a Viewport to change something on the modeling layer, and then click back into Layout page, a bunch of dimensions shoot off into oblivion. Not a new thing from Candidate 2, but I don’t think I’ve mentioned it before (and haven’t seen a posting about it)