Comment by zkmon
2 days ago
>> Most importantly, the pelican has one leg on each side of the bicycle - that's very rare.
How can you say "each side"? I don't see any z-ordering between bicycle frame and legs.
2 days ago
>> Most importantly, the pelican has one leg on each side of the bicycle - that's very rare.
How can you say "each side"? I don't see any z-ordering between bicycle frame and legs.
Because, if you look at the image you can very clearly see that the frame and relative components partially occlude one leg and not the other.
The model is presumably aiming for an acceptable visual representation, not trying to produce z-ordered components and a lost of any other random requirement people might come up with. The task is to show a pelican riding a bike, not produce a technical design that is layer order correct, after all.
Also:
> Near leg: from (300,245) to (356,408): thigh+shin as a single slightly bent line: M300,245 C 310,320 330,370 354,406. Stroke #F2953F width 12, linecap round. Far leg: from (320,250) to (404,452): M320,250 C 350,330 385,410 402,448. Stroke slightly darker #E0802F (behind, drawn before near leg but after bike? Pelican legs are in front of frame? Pelican is drawn after bike, so legs overlap the frame. The far leg ideally would be behind the frame, but in flat cartoon this is acceptable — or draw the far leg before the pelican body but after bike; overlaps the red frame.