Dear Ivelin, you might find consolation in the fact that you seem immune to these interface quirks.
I sure hope I wonāt have to resort to re-installing Windows.
That would take me a whole day, and probably result in the loss of software, files, ā¦
I see this as a purely Rhino related issue since I have no other software with this problem.
@osuire, you should rethink your conclusions as:
Hence, not a Rhino issue, perhaps an incompatibility with some new driver or Win Update. Above it is mentioned that you update the drivers. It has happened that new win updates donāt like new GPU drivers. I spent half a year investigating an issue with another software. At the end it turned out that I have to down-grade my gpu driver.
Another reason could be that Windows builds up garbage data over time. Usually it is recommended that you re-install windows at least every 6 months.
Note: Iām not looking for a fight, I honestly think the issue is with your windows installation. You should also try to run Rhino as administrator.
Dear Ivelin,
I stand by what I said.
Hereās a quote from Brian : āThis makes sense as the problematic dialogs are all the newer ones based on a technology called WPF. The ones that are working are based on very old Win32 windows.ā
Why ALL the Rhino interface was not upgraded is beyond me ; maybe it would take more than the 7 year upgrade cycle, I donāt know.
But still, if itās an issue with drivers or Win updates, then whatever software I have that uses that WPF tech, whatever it is, should go bonkers as well.
I use a shitload of recent and various apps and programs, and everything is just fine.
If I had to point out one pesky little critter on my computer today, it would be Rhino.
Heck ! Even my non-linear structural analysis package behaves better than Rhino nowadays.
If youāre happy with your Rhino as it is, go on raving but donāt come over here and piss me off like that !
No, not really.
Have in mind that newer UI consumes more resources and demands more powerful PC and new dynamic libraries, more dependencies lead to even more issues and so on. Myself personally, I prefer older UI. Not ribbons but buttons and toolbars. I hope McNeel wonāt ever remove them. If what you need from a ui.button is to start a command why do you need fancy blinking/animation/dynamic shadows inside the icons and all that to consume additional resources?
Another thing McNeel is relatively small company (comparing with Autodesk, Dassault Systems). Do you prefer to them redirecting their whole programmer army into creating new-fancy-useless UI instead of fixing bugs and providing new functionality and performance fixes? I certainly donāt.
Weāve been discussing this internally, and really donāt have a good idea how to fix it. Itās frustrating that Rhino doesnāt work on your computer, I know. Itās also frustrating that this problem is well below what we know how to fix. Itās really a lot like Rhino saying to Windows: āHey, Iād like to save this file to the C:\ driveā and having Windows respond with āNo, thanks.ā
Hereās what we know:
- Rhino uses a lot of different technology to display UI. Some of the oldest technology is still working fine, but itās difficult to maintain. So when we need to make changes, we upgrade the technology.
- WPF is among the newest UI technology we use.
- WPF is a UI system written and maintained by Microsoft. It uses DirectX to turn the UI definitions into pixels on the screen.
- On your computer, and some other computers in your office, and others in the world, something is going on between Rhino asking āHey, WPF, can you show this dialog to the user?ā and WPF saying āSure!ā. For some people, Rhino crashes. For others, blank dialog boxes.
We speculate that the problem is related to an incompatibility between your video cardās DirectX driver and WPF, but we donāt really know. Iām sure youāve already got the latest drivers installed.
Yeah, thatās a real drag to have to do. I tend to do it every year or two just to keep my computers running well - it might actually be time for your computer, too. Iāll let you decide. Another option is to get a different video card and driver for your computer; maybe thatās a less impactful way to make a change that would let Rhino run.
As always, if we canāt get Rhino 6 to work well for you, youāre welcome to return it for a full refund, no questions asked.
1 Like
WPF is also tied to the .NET framework. If you havenāt done so, you may also want to make sure that you have the latest version of the Microsoft .NET runtime installed.
Well, if itās a video card issue, it must happen to a LOAD of people, because Iām using a GeForce GTX 1070 (mobile version).
Itās not exactly a salvaged chip from a Soviet era satellite ; this thing is everywhere !
As for the refund proposal, Iāll give my tired old answer : Iām in for the Grasshopper.
This thing rocks, and itās the only thing making Rhino relevant at this day and age.
Thatās the rub. There are loads of people running GF GTX 1070 cards that do not have this problem.
Thatās why we think it is related to some Windows tool (like .NET), that is the problem that is unique to your system and a small number or others.
@osuire The 6.9 service release is due to come out today with a potential fix for you. Please give it a try when you can and let me know. (RH-48508)
I doubt our service release is going to fix the problem since this is a system level problem that we canāt repeat.
Thanks for trying the installer Olivier. Another thought; have you looked at any pending Windows Updates for your system?
Awww, Steve, Iāve sent you all my pedigree already, multiple times.
Iām more up-to date than Bill Gates himself !
In case it wasnāt clear, Iām referring to running āCheck for Updatesā on your computer. When I do that on my computer, I see a whole bunch of updates that are āPending Installā after a restart. Just trying to exhaust any possibilities that an update for Windows isnāt holding this back.
@osuire it sounds like weāve done everything we can; Rhino 6 just wonāt run well on your current configuration, Iām sorry. Your options are to buy a new computer, reinstall Windows, or return Rhino 6. I donāt think thereās anything else we can do for you.
1 Like
Well, if Iām still alive for Rhino 7, I sure hope that it will play nice with the cloud-neural-quantum-holographic OS they will have by then.
I stand corrected. It was pointed out to me that there was a fix that went in yesterday that may (fingers crossed) be related to this issue. We should have a new SR9 release candidate available later today that has this fix in it.
1 Like
Hmmā¦ so if that was the case, I would have been kind of right in insisting to look on the Rhino side, huh ?
Anyways, I just wanted to point out that I updated the crap out of my computer and I still have the bug.
Also, a colleague at the office has the bug on a spanking new Dell laptop , just so you know.
RH-48508 is fixed in the latest Service Release Candidate
