I am not rendering in Rhino Cycles, but the Rendered display mode should be quick as it’s not using Cycles. Now I am often waiting about 3-5 seconds to just switch from the Rendered display mode back to Shaded or Wireframe. This is as soon as I am using a physically based material even with a 512x512 texture.
Rhino 1 bugs are never fixed.
Just some Rhino 9 examples:
https://mcneel.myjetbrains.com/youtrack/issue/RH-55102
https://mcneel.myjetbrains.com/youtrack/issue/RH-53858
Introducing new features does not inherently mean creating a new tool.
Bug fixing actually leads to new features.
1 Like
Rhino is developed on a wide range of hardware including that with Intel GPUs, AMD GPUs and NVidia GPUs. Intel GPUs typically ‘just’ the built-in ones, AMD GPUs typically the ones in Apple hardware, although I have both a discrete GPU and an APU and Nvidia GPUs from GTX 960 to RTX 6000 Ada gen and much in between.
We’re aware of this, it’s on the list to be looked at.
-David
@clement, even though the model might be comically simple, I’d still appreciate if you could attach it here so that I can take a look.
-David
Yes.
That’s my answer to the original question.
I was a fan of “the users will tell us when it’s ready”. That doesn’t seem to be the case anymore. But I get it. Cash needs to flow, not just trickle in. From a business perspective it’s probably necessary not to take as long as it used to between major releases. But from a user’s perspective, those releases that had 4-5 years between were pretty awesome when they were released, and I had no problems updating the whole company at SR1 or SR2. That’s not happening this time.
1 Like
Hi @DavidEranen, thank you for taking care of this issue!
Below is a single surface with PBR Material. It has 2 different textures (jpeg, 256x256px) assigned to 4 slots. I get 10fps in Rendered display mode using a Quadro P5000 (16GB Ram).
PBR_Example.zip (390.8 KB)
If this object is displayed in Rendered display mode and i start eg. a Point getter which has some simple dynamic display fancy attached, it drops below 4fps…
thanks,
c.
there may have been multiple ways to accomplish this, but I think the main factor was that you had apple switch cpu architecture, and consequent need to get an official build out to organizations that cannot have people using software that’s labeled as WIP
1 Like
If we’re on 8.5 already we’ll see Rhino 9 before years’ end? Although I’m never excited about spending more money on software I’ll be keen on using flair and constraints 
And also for Mac M1/2/3 users where V7 simply didn’t run well (or at all) on those machines.
But yeah, I also think it was too early - mainly because of the huge projects this release involved:
Display - completely re-written on both platforms
User interface - completely rewritten on both platforms
Dotnet 7 transition - this is invisible but apparently was a lot of work.
Plus, admittedly, some poor assumptions regarding the UI redesign (on both platforms) - both in the way users would react and as well as how it actually worked (or not, mostly)
And, in reality, a really tiny group of developers to do all of that.
There is a paradox going on here though.
In order to find all the bugs you need a lot of users testing.
The WIP versions were not stable enough to encourage a lot of users to use it regularly
Not enough testers, not enough bugs fixed
Not enough bugs fixed, not enough testers
Etc. ad infinitum.
7 Likes
8 Likes
I certainly think the price should have tailed on, rather than the abrupt end of this month.
Sometimes I feel like I will be needing that new 14900KS just so the selection process in view port will complete in some form of rational time.
“And finally, with some LN2 cooling, and 10.3 GHz Single Core, we can not only get Cinebench at over 40,000, but we can select a Rhino curve in under 2 seconds flat!”.
For me there just wasn’t enough new stuff in R8 that made it worth my while to run the beta. I have ran the beta version since R3 or R4 even for my daily work because there were new features that made my job easier. That just hasn’t been the case with R8. I have no clue how many other users were in my same boat…?
Brian
I think Rhino 6 and 7 each had a little over 30 (32-35?) service releases before the following Rhino version was released. Usually the frequency for a service release is one per month. If McNeel keeps that rhythm and the amount of service releases, then we are still roughly 2.5 years away from Rhino 9.
if i zoom in using that example from above, so the surface fills the entire perspective viewport, i can get it to 4fps in Rendered display mode.
_
c.
1 Like
When Microsoft released Vista they had a similar problem.
Vista was not that bad, but it didn’t feel like that.
The impression was Vista is slow and buggy.
For Windows 7 they tried a new development method.
Every developer had an equally qualified developer sitting next to him.
This developer did NOT write code, he watched the active developer.
And asked questions:
Why do you do it this way?
Don’t you think you need to fix that one first?
Is the feature you are at really useful?
What is the apply button for, remove it.
Wait, you need to test your function with a very large data set.
The underlying memory management is too slow, don’t continue until it’s fixed.
etc etc
The result was Windows 7.
It felt much better than Vista, and was a big success.
Maybe not a solution for Rhino.
The role of the second developer is filled by the unpaid testers and users.
Often the impression is that the testers/user are actively unheared.
Or there is no reaction at all to a bug report.
And even small, simple things don’t get fixed.
This naturally leads to frustration:
Why spend hours and days to report bugs in detail?
Asking for SystemInfo and making a YT is not enough.
10 Likes
I feel frustrated when the number of developers is small and the list of fixes is long. Let’s wait for the next fixes, maybe it will be better. But to be honest, the V8 is unusable at the moment.Thanks
1 Like
More developers don’t lead to more, better and faster results.
Often the opposite is true.
2 Likes
I don’t know about the Windows side… But on Mac rhino, 8 is so much better then 7, and for the first time in 10 year or so, it feel Like Rhino, not Rhino-Lite.
So there’s still a few million annoying bugs, and some still missing features, but none are works stoppers.
I’ve been looking at it [the early 5 - 10 service releases] as a paid extension of the Beta, and I have no problem with this.
But perhaps they [Mcneel] should have delayed the release of the Windows version for a few month …
I mean it’s been done in the past the other way around … R6 for Mac was released 1 year after the windows version. By which time the WIP was so stable I never actually used R6. Just bought the license [without the promotional discount becouse it was a year late to release] and went strait to work with WIP 7.
So guys, let’s focus on reporting bugs for this great "paid Beta’'. as much as we have time and patience.
And to Mecneel team: I feel it is really important to put even more effort [if possible] in giving feedback when we report issues… You guys do, but not always, and the ones that falls off the radar, [I had quite a few of these] very much lower our motivation to report stuff.
thanks a lot
Akash
2 Likes
8 crashes daily doing almost nothing on a new 4090 with 128 Gb RAM. Unusable, gone back to 7.
3 Likes