Where in Preferences>Themes can this be set or changed? Or can it?
When I delete a bone that has a parent, the head bone(s) of the new bones in the chain do show up as orange. I would like to be able to see any head or tails show up in color when selected.
In blender 4.0.2, if I select the tip of a bone in edit mode (like your first image) itâs orange. Changing to stick display of bones, and itâs still orange. Selecting the tail of the bone in edit mode, and it changes to orange too. Selecting the whole bone in edit mode, the bone turns yellow and the tip and tail are orange.
Try it with a new file, insert a single bone, change display to stick, and see if you get the same results as I did.
Dawn, the full file with the dogâs body is over 12 megs. Can I send just the armature?
I might not need to send that file. The screenshot above, in reply to randy, is a new file with only one bone and it reacts the same way. When I select the tail of the bone, there is no color.
Looked thru user prefs â themes and didnât see anything related to bones in edit mode. Lots of stuff in themes area, so maybe I over looked something.
Took a look at the bug tracker, set my browser to search for âboneâ and didnât find anything related to bones in edit mode.
@DawnFilms are you using 4.2 too and itâs all working for you?
If so, then try this - on a windows machine look for this folder:
replacing âRandyâ with your user name for your computer, obviously.
In that folder there is a file called âuserpref.blendâ - delete that file. That will delete any customization youâve did to blender and would force blender to use default settings.
If this doesnât solve it, maybe I can get some other users to look at this postâŚ
And @joseph advice is solid. Probably should just rename âuserpref.blendâ to something like âtemp-userpref.blendâ, so blender wonât find the file. Then start blender and see if that fixes the problem. If not, then you can rename âtemp-userpref.blendâ back to âuserpref.blendâ
Must have been a bug then that was fixed. I was going to suggest filing a bug report, but since Iâm not running 4.2, I couldnât verify that itâs a problem.