I think the problems you are having with Rhino are not the problems everyone has with Rhino, which makes this hard to improve for you. If I were in your shoes, I’d either try out a different computer or return the product.
I know, I remember. But that’s the feeling I have over the years.
A post about a bug with 0 replies will receive a reply from a dev, in a way or another, that’s sure.
A post about a bug with some user replies might not receive a single comment from any dev, and this happens a lot.
I’m not criticizing. But I agree with anon feeling about this.
We are all grateful for devs @ availability, though.
sure, but here one essential important bug that lingers for many years, that strangely nobody is interested in though a really important part for documenting properly, talking about how many important fonts are not working properly and we users currently being left with a mess of an interface for fonts generally since freaking V6.
with @dan strangely not being able to repeat the issue
and after being served a thorough explanation on how to repeat this frankly very easy for all others to repeat as shown in that topic, never showed up again and i am waiting for more than 2 years for him to follow up.
and strange enough more than 2 years later in a different topic just very recently completely oblivious to this topic, again cant reproduce???
i lost count how often i have @ing developers and got ignored. maybe its a bit of narcissim that lets me think that but boy does that impact my experience with Rhino and almost even more with Discourse much rather.
I think the fact that you can even @ developers is huge and should not be taken for granted. Most other software you can’t even email developers.
Devs are not paid to answer your tags.
Don’t get me wrong, I have had my fair share of frustrations too, these are just two examples of many.
BUT, I think it is awesome and rare that we can so easily tag devs. Let’s appreciate the fact and not ask for more. Expecting them to reply to every single tag is too much, in my opinion.
making Rhino better and workable includes acknowledging bugs, otherwise there is no improvement, bugs dont get found by developers that often i assume and if the amount of bugs found by users is probably significant enough if not even exceeding.
i am very happy to be able to report bugs here hoping that they will get fixed at some point and not new ones being introduced while year old bugs still make it impossible for me to sufficiently work with Rhino like i did 10 years ago. so the only thing i am really asking is for Rhino to work properly. and very often do i help out on the forum as a payment.
not really, i am thankful for every contribution. but some things suck for years and get zero attention even after intensive interventions and pro active support from the users. and no obviously not just me thinking that… just scroll up a bit.
I do acknowledge that, I have my own share of personal favorites. Rhino has become a massive animal, and there are many people pulling it in different directions. Some bugs are simply going to end up having lower priority for different reasons. If the font bug you mentioned is one of them, idk, maybe @Alain can comment on that specific one.
That doesn’t answer the question at all, so I’ll repeat it… How do YOU fix something that someone tells you is wrong, but despite the detailed description of the problem, you cannot make it happen YOURSELF… Kindly tell us how you personally would go about doing that, and then maybe we can all follow the same procedure.
Ok, since now it seems that someone does care, here is the small list of my biggest issues with V8. All of them were reported, but none of them fixed. Also, none of them was present in previous versions (or at least not in my V5).
broken Recent Commands
Custom Shortcuts
This one with gumball origin was reported so many times, that I even can’t find report that I commented:
To this topic:
Sorry for negativity @Gijs but please look at it from my perspective: I am a professional product designer who bought a commercial tool for his work. But this tool has many flaws (unlike the version I was working with earlier). I have even spent some time here on the forum reporting bugs, but very few of them have actually been fixed.
I was even thinking about returning the V8, but since I already have too much data in the new format, it’s no longer a possibility… What should I do now?
i think you might also be missing the point. i do not disagree with your theory, but you seem to exclusively assume that this is the case in every instance, this or you indeed missed the point.
Hypothetically? I’d try a lot harder to find the problems before releasing them into the wild.
What would that mean? I’d have to make assumptions about what goes on behind the scenes, pretend to be a software developer and I’ll sound stupid if I make too many specific suggestions that may expose me to nyah-nyah-shows-what-you-knows, but I’d probably start with:
-more internal testing by, and in the manner of, people who also actually work in industries served by Rhino, in addition to this forum (which is still the least worst of the feedback options)
-more types and generations of computers, including crappier ones
-more confident, deliberate releases of the software that have fewer persistent or inherent problems
To preempt responses to these suggestions, I’ll take the liberty of paraphrasing a few responses from McNeel I recall on the forums and my answers:
“We can’t possibly replicate every real-world scenario.” Totally true. But you can replicate a lot more than you apparently do. You must be able to.
“More developers doesn’t always mean more or better capacity.” Ok, I partly believe you. If you insist, I suggest you add more internal testing capacity.
“There’s no better feedback than hearing it directly from our users.” Definitely. And I believe you truly want it, you’re true believers in the software and you probably love it even more than we do. But you then have to respect our time more than you do now.
The list goes on. And I stopped scrounging because I reached a convenient stopping point. I don’t know how you guys sleep with a to-do list as long as the YT system you have to manage.
That’s fine. Let’s say I drop 1-2 grand or so on a new computer. First of all, I’d be happy to take specific suggestions, because I’ve asked for them and, I don’t know, maybe people think I’m kidding. One guy posted a link from the state of North Carolina’s shopping list, actually the most useful guide yet.
Second, what’s to make me believe that a new computer is going to make the problems above go away? Peeps around the world with much better gear post before I do about this stuff. You guys are going to fix all the new problems you created with 8?
I’d just ask you to imagine how many other people there may be out there, silent and not posting, who experience problems McNeel introduced with Rhino 8 (some caused by computers too crappy for it like mine apparently is, even though it runs everything else fine) and come away thinking “Rhino sucks” or “Rhino isn’t stable any more” or “Rhino is kinda cool but it’s not pro like [insert big goofy company name here]”.
I pay too little for Rhino. Been saying it forever. This is what makes me spend time volunteering to learn and help, even if it’s in a way that people might not like, and why I resent feeling that my volunteered time 1) shouldn’t have been needed in the first place and 2) is wasted those times it is wasted.
Edit to add my system information, because I should know better by now:
Windows 10 (10.0.17134 SR0.0) or greater (Physical RAM: 16Gb)
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA Quadro P2000 with Max-Q Design (NVidia) Memory: 4GB, Driver date: 4-11-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 552.22
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
Intel(R) UHD Graphics P630 (Intel) Memory: 1GB, Driver date: 2-18-2021 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- There are no monitors attached to this device. Laptop lid is probably closed
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 4-11-2024
Driver Version: 31.0.15.5222
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
Rhino plugins that do not ship with Rhino
C:\Users\Armen\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\ColorPicker\6.0.0\ColorPicker.rhp “ColorPicker”
C:\Users\Armen\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.3\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.3.0
Windows 10 (10.0.17134 SR0.0) or greater (Physical RAM: 16GB)
.NET 7.0.0
Computer platform: LAPTOP - Plugged in [100% battery remaining]
Non-hybrid graphics configuration.
Primary display and OpenGL: NVIDIA Quadro P2000 with Max-Q Design (NVidia) Memory: 4GB, Driver date: 4-11-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 552.22
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Primary OpenGL: NVIDIA Quadro P2000 with Max-Q Design (NVidia) Memory: 4GB, Driver date: 4-11-2024 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 552.22
> Integrated accelerated graphics device with 4 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Secondary graphics devices.
Intel(R) UHD Graphics P630 (Intel) Memory: 1GB, Driver date: 2-18-2021 (M-D-Y).
> Integrated graphics device with 3 adapter port(s)
- There are no monitors attached to this device. Laptop lid is probably closed
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 4-11-2024
Driver Version: 31.0.15.5222
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB
I looked into this one and will keep an eye on it, but so far I cannot make that happen on my end.
I added that again on the agenda for next UI meeting to emphasize the importance.
I know it is, I will add that also to the UI meeting agenda.
It’s still on the developers list to fix this, but I’ll bring this up again in the next meeting
Also added as agenda point, but this is also on the developers list of things to fix.
I went through the linked issues in that thread, some of them are actually fixed (notes, edit button, navigation, deletion of all materials), some won’t be fixed because of reasons mentioned in the YT’s and a few are going to be in 9
I totally agree this should be simpler. It’s been a long standing issue.
I could not reproduce what you are showing either .
Yes, see that thread for more info
I don’t know, that one seems also a hard one to track down, I don’t recall having issues with it, certainly not in a test I just did but I will keep this in mind.
Apple macOS Version 12.7.5 (Build 21H1222) (Physical RAM: 32GB)
Mac Model Identifier: MacBookPro16,1
Language: en-CZ (MacOS default)
.NET 7.0.0
Metal GPU Family Apple 0
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Intel UHD Graphics 630 (1536 MB)
AMD Radeon Pro 5300M (4 GB)
Color LCD (1792 x 1120 @ 59.00Hz)
GPU Vendor: AMD
USB devices
Apple: composite_device
Apple Inc.: Touch Bar Backlight
Apple Inc.: Touch Bar Display
Apple Inc.: Apple Internal Keyboard / Trackpad
Apple: Headset
Apple Inc.: Ambient Light Sensor
Apple Inc.: FaceTime HD Camera (Built-in)
Apple Inc.: Apple T2 Controller
Rhino plugins that do not ship with Rhino
/Users/morris/Library/Application Support/McNeel/Rhinoceros/packages/8.0/SubstanceImporter/2.0.7/SubstanceImporter.rhp “SubstanceImporter” 2.0.7.0