I am evaluating v8, downloaded it. Installed … and first thing I get is panel sluggishness.
Empty scene, creating a couple of materials, then trying to delete those materials, hitting “delete” nothing happens for several seconds, then there is a glitch where all the sections of the physical based material expand on screen, then collapse back down, then after a second “delete” attempt, nothing happens and then finally a confirmation dialog.
No matter how much work you put in the product, if the visible stuff are sluggish, they convey a somewhat lack of pride.
The delete button not kicking in, could be a focus-loss issue (?)
However the Physical material sluggishly coming to focus and expanding all it’s contents before collapsing them again keeps happening. I don’t have a specific set of steps to repeatedly reproduce it, but it’s constant, maybe every twenty material clicks it feels like it gets stuck thinking about something.
I have noticed some very bizarre lockup behaviors too.
Sometimes, I won’t even be selecting anything, and Rhino 8 will just decide that it has something else far more important to do, locks up the entire UI (without ‘Not Responding’), and then comes back.
It’s odd too, whatever it is doing, it ramps up the CPU and fans, but not to maximum, then calms down, unlocks, and then I can carry on.
(Un)hiding Layers is an easy way to induce lockup here.
Using some parts of Cycles adjustments causes this too. In addition, changing the gamma level can cause PBR painted objects to look like they have been in a pressure cooker, and the geometry “implodes”; which requires a restart.
When initially running Rhino 8, anything rendering related will take some time to prepare, since shaders need to be compiled. This includes opening the Rendering panel, Materials and rendering itself.
@ThomasAn and @David53 pls run _SystemInfo in Rhino and post the results.
The Cycles side of Rhino is considerably better in 8.5, though I tend to use bella more.
However, I think at the moment, my new full nickname for Rhino is… well… self-proclaimed by Rhino
I really wish I could pin the problems down more, but the lockups are so random. Today, the Picture command locked up for absolutely no reason, and just sat there; no rendering, no bella viewport, just shaded.
There is usually no option to crash gracefully out of Rhino, so I have nothing to show as a report.
I beleive you have my SystemInfo anyway.
It’s not a problem for me as such, but I thought I would add myself to the list of affected people still at 8.5 level. It’s more agitating that I cannot pin the problem down, but I can only conject that there is something underlying that is causing these problems and they could be the same issue. It’s bothersome that Rhino seems to be finding “other” things to do.
I don’t think I do, and it is best to get your latest anyway.
We do get crash reports and these are studied very carefully each day. And they help a lot in improving the stability of Rhino. Be aware though that not all stability and other issues are happening with everybody. That’s why getting your info is important.
