Serengeti, named after the largest African Savanna, is where Rhino grows.
We like to involve users in every phase of the Rhino development process. As with prior releases, we will be inviting current users to try, test, and provide feedback on the next release while it is still in development.
But now we have something new. You will now be able to participate in the development beyond the upcoming release.
Since many development efforts span more than one release, we have setup the Serengeti Project to give users more direct influence on all future Rhino developments.
That means you can always have access to the daily builds of everything we are working on no matter when or if it will be released. You will also have access to our internal developer discussion, developer notes, and issues tracking system.
Since this is a new project, we are testing with a small number of users. We are inviting you to take part because you are a Rhino 5 user.
We look forward to your input on future releases of Rhino and the Serengeti Project infrastructure.
The Rhino development team will post here as they work on Rhino.
* 64-bit Windows 7, 8, or 8.1
Download Rhino WIP...
Hello Bob and the Rhino6 team,
First of all a huge congrats to you for Rhino5 and now the beginnings of Rhino6. Rhino 5 and 4 have been crucial to us to produce our quality parts.
The main things we've missed and wished that were there in Rhino in general are:
1. Class A surfacing tools (trimming, adding, locating, joining etc of Class A surfaces).
2. I wonder if anyone of you has tried to model a door or window ledge of an organic shape such as that of a Car or an Aircraft. Using Rhino there gives too many gremlins with surfaces refusing to close, Cross sections with infinite number of control points, and even two curve sweeps falling dead in their tracks.
3. The possibility to have a development tree beside a complex surface model so that future changes could percolate in the model in a systematic manner. It doesn't have to be a complete history but it should keep design intent integral.
These are the main issues we fight with Rhino all the time in modeling our parts, which are not just organic and aesthetic, they also have to meet engineering specs. BTW we're users of TSplines and wished that VSR was part of Rhino rather than Autodesk.