Rhino 8 for Mac is a constant f****ng bug.
you can read here why it was decided RH-70566 User-Interface: Viewport title menu and context popup are made more consistent with Windows version
and later the change that was made: RH-79868 Context Menu: Added Display Modes to viewport context menu
Not just teachers, but also technical support, instructional videos, documentation and the like. Not to mention common code base for the developers.
Time will tell if this happens and there is a āmass exitā of Mac Rhino users as you seem to predict - or if people will just get used to using the software in a slightly different way than before and get on with their business.
Dunno, if I type dim and Enter in V7/Mac or PC I get the command Dim(ension) that launches - Dim is actually the full command name. Exactly the same on V8/Mac or PC. I only have V5 for PC running, but it does the same thing.
Commands have not changed significantly between versions, so I donāt know what you are describing here. Everything is still in the menus. If there are differences in how the Autocomplete fuzzy logic works between V7 and V8, then itās probably on both platforms, not just limited to Mac Rhino.
Yes. As a matter of fact, for future versions, itās probably going to continue in the direction of more unification, not less. Who knows, maybe V9 for Mac will finally get a real command lineā¦
Just for fun, here is a page from the Blender forum, who apparently changed the interface recently.
(Donāt know personally, I am not a Blender user. Are the Mac/PC interfaces different in Blender?)
The comments seem very similar to hereā¦
It is worth noting that compared to Rhino 7, this version does feel rather more disjointed in Windows; there are many changes which I cannot say donāt make sense, but they certainly feel very different ergonomically.
I have felt that this seems to be a little like the Newton-Raphson method of finding a new user interface, and we are the first iteration.
It is additionally worth noting that I have been experiencing many, many lockups in the last few days doing various activities in the Windows version; sometimes with the sad Rhino, others just close to desktop leaving no recovery file. I do very much enjoy the new features, but the Mac users certainly are not alone with problems.
Having used Linux for enough years, I do understand the need to unify the interfaces for ease of development.
The Blender note above is very interesting. There is a lot of internal squabbling over what Blender should be, and Blender is a behemoth of a program now; with many vested interests, not all of which are good.
I also experience the difference in how some of the command searches seem to be, and I have had to backpeddle a few times when I have just made various key entries, and seen the geometry vanish or whatever, relying on the Rhino 7 implementation.
Locking up is another shared issue with PC users, and there is a good spread of users, including myself that have experienced the random āRhino is too busy for you todayā lockups that somtimes arenāt lockups, and sometimes are lockups that decide to crash out with no error; it can be mildy frustrating. I can sometimes cause it on demand, but I admit I have lost the will to report it over the last few operating hours.
While I wouldnāt call it fraud or any other extreme term, its certainly a lot to digest; but equally, there have been a lot of bug-fixes which are almost directly addressed in the original thread where they were given by the community. Something I donāt often see with a lot of software. And there was (to me anyway) a major error which appears to have been rectified with Cycles, which is great!
At this early stage release (is this still soft release?), given the heavy changes to both OS versions, if we were to adopt some behaviours from Mac, then if they are objectively better (however one measures that) then okay.
Donāt we forget that Blender is f***ng open source and FREE.
Contrary to McJoke, they donāt have to provide a functional software to their users.
It is indeed free, and I certainly wouldnāt debate that.
My point was around the common problems around settling on a unified solution. While Blender is free, the funding behind the Blender Foundation is reasonably political; and there have been highly aggressive groups of users and developers (and still are).
Hardly any business who funds the Blender Foundation does so out of the goodness of thier heart. To some extent, they arenāt answerable to thier users, but they are answerable to other parties. I meanā¦ Adobe, Meta, AMD, Google, just to name a few? In some sense, they actually do have to provide functional software (too big/embarassing to fail).
Again, there are many problems on the Windows version, but Iām not sure everyone is having the same experience of Rhino 8 being utterly disfunctional on either OS. Thatās not to say you are in isolation either; perhaps just on the lower end of the āpositive/negative user experienceā bell curve.
But I am.
McNeel wanted to release v8 for Mac to public while navigating a single-box model in shaded mode caused Rhino to lag, and I had to fight alone for weeks just to make McNeel notice it.
This is the level of their teams.
Worst: that issue has never been solved, they just applied a workaround, which is still there.
Rhino for Mac has very serious problems at its core, that Rhino 7 didnāt have.
Those have also hired actual DESIGNERS and provide good functional software.
Excuse, not only Rhino is buggy as hell, but also its UI has been designed by a drunken child.
Iāve taught Word classes where half are Mac and half are PeeCee.
Same problem.
Relatively new Rhino for mac user (less than two years) having started with v7. I cannot agree with your comment about it looking like the PC version. This sounds like the tired PC vs Mac conversation and is not productive. I CAN agree about the user experience. More about that later.
At first, I was very unhappy about v8, transitioning from v7 as I had just learned v7 and had just become very productive. Version 8 became available and was found to be so different, I felt like I had to learn yet another new software. But hereās the thing: one must be open and willing to learn new things. Change is inevitable. Get used to it! Jump in and confront it head on. I promise, the brain can be very plastic. Jump in and take it on is how I decided to go forward and Iām glad I did.
Now about the user experience. McNeel have been very public in acknowledging mistakes in the release of v8. The release was premature. They are making extraordinary strides to fix bugs and make it right. They are also very public around the reasons to unify the UI. That comes down to business fundamentals and being efficient. Inefficient business fail! This is where users will need to adapt old was of thinking regarding the PC vs Mac argument. What if you report to work the next day and all your tools had been changed and you had no other option but learn the new tools or perish? In order to become productive, I spent a lot of time customizing keyboard shortcuts and aliases. Customizing window layouts and toolbars also was a critical step for me that really helped the user experience. Rhino is very flexible in this regard, so the user can custom tailor much of the environment. This puts the user largely in control of user experience. Sure, some things cannot be manipulated. The critical user experience item I can note is the COMMAND + ENTER paradigm (why must we beat up on the enter key?) This is the same AutoCad UI model going back more than 30 years. If we could remove this necessary keystroke combination for aliases/commands, that would go a long way to making it feel more up-to-date IMHO. Yet, I do this because itās necessary, although Iāve been around long enough and used ACAD over 30 years ago, so it is familiar.
Final words of advice: Just do it. Use it, learn it, adjust the tool to your own satisfaction, because itās too easy to only be a critic.
1 Like
no idea why people complain, I find it quite impressive ā¦ interested if synchronization with Cinema and Blender is coming and nit sure why only these two plugins are missing from the listā¦though full respect fro improved render previews power of Rhino itself - quite enough for all preliminariesā¦
What would be in a moment the most fluent way of Rhino 8 model toward above mentioned engines like Cinema and Blender adapted for the use on M3 Chip ? Precisely , is there any change beside exporting it to formats like .fbx etcā¦ ?
Export .fbx and import to C4d works quite well. All textures and geometry are translated. Set up cameras and lights in c4d ā render. Layers come thru with rhino geometry so managing geometry in c4d is manageable.
well you come several month if not several years late to the show, while others were battling out the bugs and you wonder what people complain about is a bit strange dont you think.
you thereby say that all people actually investing there efforts are delusional.
12 months later, to what expect have the kinks been ironed out please?
12 months later, thatās the situation
ā layers delete when the shouldnāt.
RH-86060 was fixed in 8.17.
-wim