As stated when I try to change the materiality of a layer via the layers toolbar and proceed to click on “color” Rhino freezes and crashes. I recently updated to SR10- it was not doing this previous to the update. Any ideas on how to fix this?
I should also note that when I try to change materiality via the properties toolbar with selected objects the change is made no problem- I need to be able to change entire layers, however.
This is a weird problem, but the solution, for me at least, is to use VRay and create a basic material and apply to layer.
I have the exact same problem. When selecting material and trying to apply it to layer in the Layers menu it crashes when trying to select it. However, found a way to apply material by layer with the tool TOGLE MATERIALS PANEL in the render tools. Not idal but you can right click the material and apply it to a layer.
Are you also using VRay?
Yes,
I am using Vray, but I have to disable it to be able to select the material
picker of rhino. I only asign the renderer to rhino and vray back and
forward. Thats the best trick I found.
De : “Wim R.M. Dekeyser” steve@mcneel.com
Répondre à : McNeel Forum
discourse+69a6b7137a63440c14f59e5e919f4c6b@mcneel.com
Date : jeudi 5 février 2015 02:09
À : Guillaume Vanderveken gvanderv@gmail.com
Objet : [McNeel Forum] [Rhino for Windows] Rhino render color picker
causing rhino to crash
wim <http://discourse.mcneel.com/users/wim>
February 5
Are you also using VRay?
To respond, reply to this email or visit
http://discourse.mcneel.com/t/rhino-render-color-picker-causing-rhino-to-cra
sh/14636/4 in your browser.
It looks like that makes 3 people in a row reporting the same crash bug - all using Vray. Can you reproduce the crash when you start Rhino in safe mode - simply switching to an other renderer isn’t enough.
Strange. I tried it in Safe mode, it worked and now it works in normal mode also. Before that, I tried with the renderer selecter to rhino and vray without any difference, it was always crashing.
I am having crashes with color picker. I do not have Vray, but I have Maxwell. Running in safe mode seems to load a different looking Material editor than the one loading from normal version. No crashes in safe mode. I tried un-installing Maxwell to see if it is the culprit, but I still get crashes. It is repeatable.
Actually just clicking on certain parts of material editor window crashes rhino for me.
Running R10 on Windows 7 64bit
I noticed this happening too recently. Rhino has been fine right up until about a week ago and then suddenly crashed every time tried to pick a material. It seemed to coincide with a windows update. I was going to try a uninstall/reinstall but did the repair option instead in Programs and Features and now it works fine.
Hope this works for others.
FreekeeDeekee, I tried the repair option. Unfortunately it didn’t work for me. I am not sure a full re-install will make a difference. It seems to be a bug of sorts. I guess if need be I can just go through the render area and assign colors and materials rather than using the layer material editor.
Hi Talos - so, with Maxwell currently not installed, and having done a ‘Repair’ on Rhino, (Correct?), what steps, exactly, causes the crash?
thanks,
-Pascal
Hi Pascal
I click on the circle to the right side under Material column of the layers. The editor opens up with a spherical icon indicating current material. Under the color option, when I pick color picker from drop down menu, then I get the blue ring of death and Rhino basically crashes. As mentioned I ran Rhino in safe mode, and the material editor seems different (I am not sure if it’s just a simpler version of the editor running in safe mode). Anyways, color picker works fine in safe mode. I am trying to re-install Rhino and plugins to see if it helps.
UPDATE: re-install did not solve the issue. I still get the blue ring of death and Rhino crashing. This time I ran Rhino before installing Maxwell again.
Ok. I did a second re-install and now it seems the color picker for layer material editor is working without a crash (fingers crossed). So a re-instal may fix things for some people. I am not sure what caused the problem, but it may have been a windows update that broke something.
So. I am noticing Rhino crashing again when I click on the color picker or even color option of the layer material editor window. It was working fine, but something is broken. I am at a loss at what it can be.
Hi Talos -Does the McNeel crash report interface show up on these crashes? If so, are you sending the reports?
@jdhill, do you have an idea? It seems at least in some cases Maxwell might be in the picture.
thanks,
-Pascal
Pascal, I am not sure. I don’t see a report window. The app just dies. If I try clicking on the app window, I receive the typical Windows message asking if I want to kill the app.
Screen grab of what I see as far as the editor goes. Is this Rhino’s or Maxwell’s editor? Notice the “Not Responding” notice on upper left…middle of a crash.
The crash seems to be somewhat random. Picker works ok for now. But I had to restart my computer.
Hi Talos- thanks - yep, that is Rhino’s control - so, am I correct that you never see the color picker at all after the click, or does it turn up and crash or? I think we tried this with Maxwell and/or Vray blocked, in Options > Plug-ins (restart Rhino), is that correct? Can you verify that this still happens without one of these rendering plug-ins loading at all?
thanks,
-Pascal
Today, instead of killing the app after clicking on the color option and having Rhino break, I just let it be for a few minutes. Then I see the color picker showing up after a long delay (kind of strange). Now, yesterday I un-installed Maxwell and was still getting the crashes. As of now, it seems to be working ok.
Hi Pascal, I’m not yet able to observe anything like this here. My first question when dealing with weird behaviors like this is usually, what are the chances we’re running in a virtual machine. Secondly, I notice that in the screenshot, it looks like KeyShot and T-Splines are also loaded, so I’d ask about checking with those disabled/uninstalled, too, just to be sure.