pyjo

Mmh... sorry I can't follow your thought. Copy Paste and layer management are allowed as long as what you copy/paste etc. is entierely planned, designed and crafted by you. The list of rules that specify which tools are allowed was yet published, and is now clear enough. What I am dealing of now is related to the mental process which is used to conceive the picture. If the hand is free, but the mind is constrained in a grid, the freedom of the hand is only apparent. Everyone here is free to propose a contest in which only a specified list of tools and techiques is allowed. I intervened here with some proposal only because k.digennaro's initial rules seemed too vague to me. Bye Pyjo.

I'm not the owner of this constest, so I can only suggest rules. However my suggestion is that ANY pre-existent digital model should be avoided. In a free-handing drawing your hand should be free from the need of tightly following a model. You can make a pixel-by-pixel copy of a digital photo using only the color picker and the pencil tool, but this is a very boring activity that has nothing to do with creativity and artistic flair. Applying a grid on a photo and copying it in PdN is only a smarter way to do basically the same thing: the creative process remains at a very low level and, above all, the hand is not "free" as the title of the contest requires. (This doesn't mean that the ability of replicating an existing picture in PdN is not valuable at all. There may be a contest in which a picture is proposed and all participants try to rebuild it in PdN). I actually think that also every kind of paper-based 2d models should be avoided, and only real-world 3d object should possibly be used as a model: evaluating proportions and creating the 2d artwork from the 3d model is up to the dot-net-painter ability. I know however that this rule will be considered too restrictive by most PdN users, and it in not realistic since it cannot be enforced in any way. I therefore whish to suggest another way for managing this contest. After the deadline and before voting, participants will post some details about the techniques they used and publish some screenshots of the key points of their work-in-progress (every participant is implicitly assumed to be honest, of course). Then the voting process will take into account both the final result and the creativity expressed in the development of the picture. I'm working on a project for this contest, but unfortunately I have very little time to spent with PdN this week. I hope to succeed in posting my picture before the deadline so that I'll have the chance to better explain what I mean with these proposed rules. Bye Pyjo.

As further rule clarification, It may be useful to show an example of a forbidden procedure according to the rules I proposed: I think that, even if there is no photo in the final result, this picture should be considered as not admissible. Bye, Pyjo

This is my proposal for clarifying contest rules, since unclear rules lead usually to confusion and (sometimes) to bloody conflicts. 1) You MUST create your picture from scratch: no photos, no stock images, no scans. This is what we mean when we say 100%PdN. 2) You CANNOT use any plugin. 3) You CANNOT open the Effects menu. (You may want to apply a stripe of black sticky tape on it to avoid unintentionally breaking this rule). 4) You CANNOT use Adjustments->Curves, since Gradients and Curves together are TOO powerful (this rule does not affect the Line/Curve tool). Is this set of rules acceptable for the free-handing drawing contest? Or are they too soft? If they will get approved by k.digennaro, and if I'll choose to participate, I'll refer to these rules. My personal opinion, however, is that a plugin such as Basic Antialias should be allowed, since antialiasing is not an "effect", but a way to overcome a limitation of digital imaging that tends to be "pixelated". Antialiasing is implicitly allowed by rules since it is included in many PdN tools. On the other hand it is true that everyone could claim to use his own plugin for a variety of reasons, and making an exception could lead to an endless diatribe on which plugin are admissible. Bye Pyjo.

Are features like rotate/zoom, Brightness/Contrast, Hue/saturation allowed? And Layer properties such as blending mode? Bye Pyjo.

This is my last word on this topic, since this post also pollutes the Pictorium. What I wanted to say in my "post scriptum" is that everyone should publish here only its best pictures. There is no requirement that they are all excellent pictures: simply do your best and then post it here. I worked on PdN for a month before posting something, and I now try to maintain the number of my post at a minimum to increase the average quality of them (and therefore the average quality of the Pictorium). As an example, I think we should avoid to post here a picture only for requesting suggestions on how to improve it. There may be a place specifically assigned to this sake. Bye Pyjo.

Sorry... what do you mean with "source image"? If it can answer your question, I'll say you that it is 100% PdN, as usual. Bye Pyjo.

The water is shallow here. Come and see that strange fish! Bye Pyjo. Post Scriptum: I don't want to be boring, but I have something to say about the use of the Pictorium. Maybe I'm wrong, but I think that it should be a collection of the best pictures from the PdN users community, and possibly comments on them. A guest visiting it should say: "oh, what beautiful things you can do with PdN!". An exibition of the power of the gradient tool with enormous, useless pictures or debating on which tool is more powerful pollutes the Pictorium. I think we all should avoid pollution, if possible. Thanks.

Thanks for comments and bug report. I'd like to publish the code, but at its current state it is so ugly that an experienced PdN plugin developer could find it obscene, and I don't want to violate again forum rule #12. Now I'll try to fix the bug by myself, to add features and clean the code, so that I'll release the version 2.0 dll with the source. Then the developer community will possibly improve it. About the bug: I think the error occurs only whan you antialias the entire picture and the solid shape touches the border of the canvas. The workaround is to apply Basic Antialias to a selection that doesn't touch borders. Bye, Pyjo.

-EDIT- The 1.1 release fixes the reported bug. Or, at least, I hope so. You find this new Basic Antialias in the Effects->Object submenu. I cannot say if Basic Antialias is better than Antialias. What I can say is that my design goals in writing it were 1) avoid side effects like shrink, grow, blur or outline, and 2) reduce aliasing in a basic way without having to spend time in fine tuning of the settings. Basic Antialias satisfies this goals, and also my personal needs. I hope you will find useful, too. You find the code below. Now I can understand almost everything of it. My code is far from being perfect, it is redundant and not always does the right thing (it is almost impossible to note this, however). If you want to improve it but you can't understand it, please contact me and I'll try to explain. I plan to release version 2.0 with support for trasparent objects in the future, but now I want to try developing other plugins. Thanks, Pyjo. ________________________ What? After Feather and Antialias, another antialias plugin? Well... sorry... this is my first plugin, I wanted to start with something simple and not too experimental. Ok, but why another Antialias plugin? Here is the answer: I noticed that some PdN users, including me, are not totally satisfied with existing antialias tools. I often used motion blur, which is not intended for this purpose, for removing aliasing effectively. So I took CodeLab and wrote this new plugin. Since I'm not a developer (and I don't know C#) it required me a lot of time, but eventually, pushing and kicking, my bare C code worked as expected (I hope that soon or later I'll understand how, too). I created this plugin for personal use, but maybe that someone else will find it useful. Basic Antialias is basic in that it doesn't ask the user for any setting. It affects the border of "solid" shapes surrounded by trasparent pixels. It is useful when you copy and paste a selection in a new layer or when you fill a selection with something like clouds or gradient, as in this example: (f you see no difference between the four moons, please put your nose close to the screen.) The original picture is aliased. Feather and Antialias (with default settings) introduce a blur. Basic Antialias reduces aliasing without altering the sharpness of the border. Here is another example: The rose was selected with the magic wand from a photo, copied two times in a new layer and then Basic Antialias was applied to the second one. To use this plugin dowload the .zip, put the extracted .dll file in the Effects folder and (re)start PdN. You'll find the tool in Effects>Contour submenu (is this the right menu for an antialias? Please give me a feedback). If the plugin seems not to work, verify that the shape to be processed doesn't contain any partially trasparent pixel. Basic Antialias works only when it finds a totally trasparent pixel (alpha=0) near a not-trasparent-at-all pixel (alpha=255). If some antialias tool was previously used on the picture (note that paintbrush and other drawing tools have the antialias feature on by default), basic antialias won't do anything on it. Maybe this limitation will be removed in 2.0 version. Bye, Pyjo. void Render(Surface dst, Surface src, Rectangle rect) { PdnRegion selectionRegion = EnvironmentParameters.GetSelection(src.Bounds); Rectangle selection = this.EnvironmentParameters.GetSelection(src.Bounds).GetBoundsInt(); ColorBgra CurrentPixel; for(int y = rect.Top; y < rect.Bottom; y++) { for (int x = rect.Left; x < rect.Right; x++) { if (selectionRegion.IsVisible(x, y)) { CurrentPixel = src[x,y]; int i,j,p; //VERTICAL double x1,x2; for (p=1;p>=-1;p-=2) { //Addition if((x>selection.Left) && (x<selection.Right-1) && CurrentPixel.A==0&&src[x-p,y].A==255) { for(i=y;src[x,i].A==0 && src[x-p,i].A==255 && i<selection.Bottom-1;i++); for(j=y;src[x,j].A==0 && src[x-p,j].A==255 && j>selection.Top;j--); if(src[x,j].A==255&&y<=(i+j)/2) //bottom { x1=((double)y+(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); x2=((double)y-(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); CurrentPixel=src[x-p,y]; CurrentPixel.A=(byte)((x1+x2)*127); } if(src[x,i].A==255&&y>(i+j)/2) //top { x1=((double)y+(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); x2=((double)y-(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); CurrentPixel=src[x-p,y]; CurrentPixel.A=(byte)(255-(x1+x2)*127); } } //Subtraction if((x>selection.Left) && (x<selection.Right-1) && src[x,y].A==255&&src[x-p,y].A==0) { for(i=y;src[x,i].A==255 && src[x-p,i].A==0 && i<selection.Bottom-1;i++); for(j=y; src[x,j].A==255 && src[x-p,j].A==0 && j>selection.Top;j--); if(src[x,i].A==0&&y>(i+j)/2) //bottom { x1=((double)y+(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); x2=((double)y-(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); CurrentPixel.A+=(byte)((x1+x2)*127); } if(src[x,j].A==0 &&y<(i+j)/2) //top { x1=((double)y+(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); x2=((double)y-(0.5))/(j-i+1)+(0.5)*(i+j)/(-j+i-1); CurrentPixel.A-=(byte)((x1+x2)*127); } } } //HORIZONTAL double y1,y2; for (p=1;p>=-1;p-=2) { //Subtraction if((y>selection.Top) && (y<selection.Bottom-1) && CurrentPixel.A==255&&src[x,y-p].A==0) { for(i=x;src[i,y].A==255 && src[i,y-p].A<255 && i<selection.Right-1;i++); for(j=x;src[j,y].A==255 && src[j,y-p].A<255 && j>selection.Left;j--); if(src[j,y].A==0&&x<=(i+j)/2) //going up { y1=((double)x+(0.5))/(i-j-1)+(0.5)*(i+j)/(j-i+1); y2=((double)x-(0.5))/(i-j-1)+(0.5)*(i+j)/(j-i+1); if(x==((i+j)/2)) CurrentPixel.A=(byte)(255-((y1/2)*127)); else CurrentPixel.A+=(byte)((y1+y2)*127); } if(src[i,y].A==0 &&x>=(i+j)/2) //going down { y1=((double)x+(0.5))/(j-i+1)+(0.5)*(i+j)/(i-j-1); y2=((double)x-(0.5))/(j-i+1)+(0.5)*(i+j)/(i-j-1); if(x==((i+j)/2)) CurrentPixel.A=(byte)(255-((y2/2)*127)); else CurrentPixel.A+=(byte)((y1+y2)*127); } } //Addition if((y>selection.Top) && (y<selection.Bottom-1) && CurrentPixel.A==0&&src[x,y-p].A==255) { for(i=x;src[i,y].A==0 && src[i,y-p].A==255&& i<selection.Right-1;i++); for(j=x;src[j,y].A==0 && src[j,y-p].A==255&& j>selection.Left;j--); if(src[i,y].A==255&&x>=(i+j)/2) //going up { CurrentPixel=src[x,y-p]; y1=((double)x+(0.5))/(i-j-1)+(0.5)*(i+j)/(j-i+1); y2=((double)x-(0.5))/(i-j-1)+(0.5)*(i+j)/(j-i+1); if(x==((i+j)/2)) CurrentPixel.A=(byte)((y1/2)*127); else CurrentPixel.A=(byte)((y1+y2)*127); } if(src[j,y].A==255&&x<=(i+j)/2) //going down { CurrentPixel=src[x,y-p]; y1=((double)x+(0.5))/(j-i+1)+(0.5)*(i+j)/(i-j-1); y2=((double)x-(0.5))/(j-i+1)+(0.5)*(i+j)/(i-j-1); if(x==((i+j)/2)) CurrentPixel.A=(byte)((y2/2)*127);else CurrentPixel.A=(byte)((y1+y2)*127); } } } dst[x,y] = CurrentPixel; } } } } BasicAntialias11.zip

Happy New Year! Pyjo.

December 21: winter begins! In the boreal emisphere winter is cold. Bye, Pyjo.

That definitely elicits the WOW factor! :shock: That is really well composed! However, the exception would be the antennae which aren't as natural looking as the rest of the image. I think the proboscis too is not enough 3-dimensional, and the legs also could be more accurate. But the point comes you have to say "let's stop". I was satisfied when the butterfly jumped out of the screen. However, I can guarantee that it's 100% PdN Bye Pyjo.

Pay attention to the butterfly, it's escaping from the screen! Don't worry, there is no danger: it's 100% PdN. Bye, Pyjo.

Perhaps it doesn't worth a tutorial. Start with something like this: Apply Shape3d with half sphere map and a little vertical radius. Then play with various light settings. Finally create the other half by using a simpler texture. If you know in advance which color you will use for the environment you can include it in the texture. I choosed the color only at the end of the work... so my picture it is not so good. Bye Pyjo. Note: this is NOT a tutorial. Please don't blame me for having posted this message in the wrong place.

100% PdN, of course. Bye Pyjo.

This is my wedding ring (without ruby). Bye Pyjo.

I added a thick, mouse-shaped (to honour the mouse I used to draw it) bra to the picture I published in a previous post and that was considered inappropriate for this forum. It isn't the same thing as before, but still pretty. I hope that now it is chaste enough to survive. I was allowed to show the original image to those who request it via private messages. If you want to see what PdN can actually do (or what you can actually do with it) and are not adverse to nudity in art please contact me. Bye Pyjo.

i've tried everything but i cant fix the swoosh .... i just simply feather this one more than once. any better? I did this without any plugin. I duplicated the layer and applied motion blur with different angles, then faded with gradient in transparency mode. Bye, Pyjo

@Crazy Man Dan: Thanks. Now I feel good. I'm not combative. I don't want the link to be restored, if it is not compliant whit rules. I only wish that rules are applied in an impartial way. Rule 5 is at least as important as rule 12, don't? And I hate too many exclamation marks. Thank you for your work. Pyjo.

Ok, I abide the rules. If someone want to see the censored picture he/she can send me a message. However I want to point out that the first message of the pictorium is outlaw, because it infract rule #5. Now I expect that the entire Pictorium will be removed. Bye Pyjo.

If you are older than 18 months I cannot guarantee that you won't be hurted. If you are less than 18 months old you surely will enjoy that. The picture is 100% PdN. Bye Pyjo. EDIT - Sorry, the link was removed. Someone didn't like my picture. Too bad, I think it was one of my best work.

IMPORTANT: read carefully! They usually come in pairs. They are soft and round. They are one of the most beautiful and useful things God has (or is said to have) created. Many painters and sculptors in any historical age have included them in their masterworks (and now there is a 100% PdN version, too). They are offered to newborns and very little children, who like them very much. Despite this, there is someone who could consider them an inappropriate subject for this forum. A friend of mine, who saw my PdN pictures, challenged me on this subject. He was amazed by the result. I'd like to post this new picture in the forum, but this could infract forum rule #12. I choosed not to post it, and provide a link instead. Perhaps this is also an infringement, so I recommend that adults don't click the link. URL Removed * I'm doing it. Maybe I'll be banned. Maybe this is my last post. Thanks to all. Thanks especially to those who make me feel their appreciation for my work. I'll miss you. Pyjo. Post Scriptum: please be polite in your comments. * The image was found to be inappropriate for the forum due to depictions of nudity. pyjo has offered to send the link to the image via PM to anyone who wishes to see it. This is permissible, but keep the link in the PMs.

Here is a gallery of solar system objects. These pictures are among my first PdN works; I created them when I discovered the Shape3D plugin. I choose to publish them now because, although they are not so noteworthy, I saw that there is some interest in this forum on planets/stars/space pictures. I tryed to make them as realistic as possible. One can easily find the real planet textures, such as this: to create extremely realistic planets, but there is no fun in that, and you can't say... 100% PdN! Here you can see a solar eclypse (very very simple but quite effective) and the Sun seen through a very dark filter. Here there are Venus with ist dense clouds (false colors) and Mars with its thin atmosphere: Here there is Jupiter with its giant red eye (not easy to do... maybe I'll improve it soon or later): Finally let's go on Saturn, one of the most charming solar system jewel: Bye Pyjo.

Maybe I didn't understand well your comments... thank you anyway. I tryed to achieve some atmospheric perspective by inserting a transparent light yellow layer (the morning sunshine) between the grass and the mountains. The blur is not intended to achieve atmospheric perspective, but to create a photographic "depht of field" effect similar to this (from Wikipedia): I used it because I wanted to emphasize the flower... and also not to spend too much time working on the background details. Note that in my picture there are many levels of grass with different blur amount, and also the upper petals of the flower are a bit blurred at the edge, because they are out from the in-focus range. Bye Pyjo.