I'm pretty sure my team are aware not to use solid greys to shade with. It could very well be that the layer has been set to something that hasn't saved well in transparent form - we draw an awful lot, and get into habits with our drawing. Sometimes we just end up setting up our layers for what worked in the last group of files and forget to change them.

We do also work with both a dark and a light base. Some things just slip through when you're drawing dozens of items, day after day. I'll try and keep a closer look on the smaller features for those out of place pixels :)

Quote by Shalashaska

Oh geez... That&;s one of my favourite items but I wondered why the eye sockets washed things out a bit.
For anyone lurking:

<em>cough</em>grey shading<em>cough</em> + bonus bleeding

A ha! That's one of mine, and is NOT grey shading! It appears to be a desaturated orange on multiply, and is definitely incorrect, but I knew I didn't intentionally shade with grey. Man, I bet that was me playing around with the hue adjuster.

The mistake I've made here is setting the layer to multiply, and then I've saved for web (as we are required to) which doesn't preserve the multiply setting. I'm pretty sure when this went through the previewer wasn't working with dark bases and so it wasn't spotted by whoever approved it. Simple error in saving, because that file contained about a million layers and I tend to get used to my multiply layers.

Easy to fix, as are a lot of things listed here, I imagine. (I will be bringing this up in our next department meeting)

It actually isn't a case of minor semantics here. A problem was presented to me, and you immediately implied that it was clear what the issue was - grey shading. Now, if I just went to my girls, and said 'don't shade with grey', they would already be aware of that and nothing would be fixed because the problem wasn't really diagnosed. And actually, it IS my job to be able to figure out which of a myriad of different things could be going wrong in my coworkers or my own files - and now I can actually ask the question 'is your layer set to multiply?' when I'm going over image issues such as these with my artists.

Just as a programmer needs to investigate a problem before it can be fixed, I had to diagnose what this problem actually was. I am happy to fix things that are pointed out to me. If you'd just wanted all current colour bleed problems and incorrect shading issues fixed, just a simple list would have done, although we wouldn't really have got to the root of the problem.

I'm letting you in on my process because, well, users have enjoyed this kind of transparency from us. It's nice information, and helps other people who might have had the same problem, and shows that I/we are actively working on the problem with the intent to fix it. I mean I /could/ have just said 'this is being worked on' and nothing else, but that's not much fun now, is it.