Here you go, Steve. Now it’s wishified…
http://mcneel.myjetbrains.com/youtrack/issue/RH-30675
Hi,
Wish would ideally be to have same yellow colour used at edge as at centre cross and as on lines and curves, as a thicker edge might get in way of fine work. as another poster also commented on.
Steve
@jeff, any ideas on the difference in colors?
My simple plan is that all layers are black and the selection color is orange or red. Black layers are VERY POWERFUL for design feedback – so I get nice gray shading on all surfaces. I’ve seen people with too many layer colors and its either distracting or skews your opinion of the design. Black layers + gray shading makes it easier to study the form and make design decisions.Plus, selecting is a breeze.
1 Like
If it wasnt for coloured layers I would not be able to work, my projects are extremely busy with lines etc and I use colour to stay sane and make sense of all the shapes. as well as hide and other such things…Red is for cutters, green dims, other colours except yellow for different items and other intelligent use.
If I were to make them all black, I think I would suffer a brain nasty or mental breakdown.
Steve
Hmmm, this looks buggy to me…strange I’ve never seen this until now 
It appears that edges are getting blended with the selection color and their layer color. You can really notice this when edges are thicker than 2 pixels. However, if the layer color is one that doesn’t “mix” well with the selection color, only then do you see the problem. For example: Black (the default layer color) is just all zeroes, thus when mixed with the selection color gives you 100% of the selection color, and you don’t see the problem. But if layer color is something like red, then what you get is something that looks orange-ish (if selection color is yellow).
I’ll have to dig through the code to see where and why layer color has any impact on selected edge color. My guess is that there’s something buggy with the “Edge Color Reduction %” setting/logic in the display mode attributes, but just a WAG at the moment until I can take a look.
As of right now, I’m not sure what kind of workaround will help, or if there even is one.
-Jeff
1 Like
I think there’s definitely something odd with “Edge Color Reduction” and has been for a long time… I have forgot to report it and just got used to it…
Philip
Um, Ok. However, I never said there was something wrong with the Edge Color Reduction…just that there might be something flaky with the logic in regards to selected objects.
So, could you please elaborate on what you mean by “something odd”? There’s not much to the color reduction code…it just takes the color and multiplies it by a percentage, yielding a different color…basically it’s just a “brightness” factor…so I’m not sure what would be odd about it.
Thanks,
-Jeff
Hi,
I thought I had lost a pictureFrame pic having moved it,
Layer it is on is black.
When I can find it, selected its so much more visible. (pic shos it after slight rotation I needed to do.
Steve
Yes, I know - sorry about the vague comment… I was in a hurry…
There’s nothing odd with color reduction itself - the odd thing is when I started to use it i noticed that about the same time I began having difficulties to determine what surface to pick when the object selection menu came up - I didn’t get the pink shading on the surfaces.
However… I just tested it with two overlapping boxes - and that works (I get the pink shading) - but it doesn’t seem to work on all objects. Hmmm, that doesn’t help to much… I have to test some more on both OS X and Win7.
Philip
Ok, now a did some quick tests on both operating systems. With a new, empty file everything is fine on both Bootcamp/Win7 and OS X - I get the pink edge color when the selection box pops up. In most of my files the pink shading doesn’t happen on either OS. I get just a darker black (?) edge color. That makes it really hard to see which surface you’re supposed to select. It obviously hasn’t got anything to do with the color reduction thing (sorry Jeff) as it happens in all display modes regardless of the amount of color reduction - or edge thickness, for that matter. It seems to be related to my files. I might have some materials or textures (or something else) that has ‘traveled along’ from file to file as I often use ‘save as’ when starting a new project. I haven’t had the time yet to figure out what the exact cause is, but here’s a small file with the selection problem, if someone likes to try…
Philip
Xtest.3dm (3.0 MB)
@jeff I’ve found a few other irregularities while messing around with display settings, perhaps related? I’ll make a new post about it when I have some time this weekend.
Is anyone seeing what I see…? @jeff
Philip
I’m not seeing any selection problems at all here using your file… However, all you gave was a file… No description of where or when you see the problem. Can I just click anywhere that causes the selection window to pop up? In any viewport? … So far, trying everything I can here yields the pink selection highlight if/when multiple objects are detected.
There are some other things to try:
- Export all your display modes for safe keeping.
- Restore all of your display modes to their installation defaults.
- Try to reproduce the problem.
Also, if you think this is some kind of residual cause and effect, then I would try starting with a brand new scene…Shutdown Rhino, restart with a new template and start modeling something…eventually you should see the problem…and if not, then perhaps it is residual, although I have no idea what that would be.
Note: Once you’re done testing restore all of your display modes by importing the files you saved in step #1 above.
Note2: If restoring the display modes to their defaults does seem to solve the problem, then I’d like you to send me the exported modes you made in step #1 so that I can compare them to what Rhino’s default settings…it might reveal the cause.
Thanks.
-J
Yes and yes.
Ok - I did the tests. Using the ‘restored to default’ display modes solves the problem and I get the pink highlight. Importing my custom display modes again makes the problem occur again - the display modes I haven’t changed are ok. This happens in the file I sent and in any new file - and in all viewports.
Philip
Edit: This is all in WinRhino. I have the same problems in MacRhino, but I’ll have to test a little more on OS X…
Custom 01 Shaded.ini (10.9 KB) Technical.ini (10.4 KB) X-Ray.ini (10.9 KB) Wireframe.ini (10.4 KB) Shaded.ini (11.5 KB) Ghosted.ini (10.9 KB) Rendered.ini (10.4 KB) Custom 02 Shaded 2D.ini (10.9 KB)
In MacRhino strange things happen… Even if I revert the display modes to default values I get the strange behavior in my test file - in all but one viewport! In “Right 00” I get the pink highlight, but not in the other… Odd!
In a new file everything is ok…
Philip
Using both of your “custom” modes, I’m still not seeing the problem…
Is there any other steps you’re doing other than loading the file and clicking on objects? Do you have any other external type of devices attached? Like a Space Mouse?
-J
No space mouse, but a external Apple keyboard, trackpad and mouse (and a Logitech wireless mouse) as I use a MacBook Pro + an external 27" display. Did you try the other display modes. They are all ‘custom’ or somehow modified (blue ‘names’ in WinRhino) even if it doesn’t say so in the name - sorry for the confusion there…
Philip
Forget this comment… I hadn’t restarted. Everything is fine in MacRhino after reverting the display modes to default values. Sorry…
Philip