Jump to content

alexo

Members
  • Posts

    72
  • Joined

  • Last visited

Everything posted by alexo

  1. Is there an effect that will make a font look like a sitched military name tape? Examples: http://tinyurl.com/m3m9thq Alternatively, is anyone aware of a font that already looks like that? The font used in those name tapes is Franklin gothic condensed, but I need to simulate the "stitches". Thank you!
  2. Hello, Are there plugins, tutorials or plain "best practice" lore as to putting fur on people images in Paint.NET? In particular, I'd like to achieve something like this, but more seamless if possible. Thank you!
  3. Let's say I have a picture with several people and I want to change the skin tone of one of them. What would be the best way to do it while minimizing selection errors? Thank you!
  4. I started having this problem in 3.5.10. It would not copy images larger than about 400K pixels, which is really quite small Windows paint has no problems with images even larger than that. Any ideas? I can't work...
  5. Hello Simon, Thank you for your reply. I find the forced autodetection feature is subjectively unhelpful. In the screenshot below, it shows me 42 icons, out of which I currently use exactly one program and may conceivably use another. In other words, 95% of the icons are not needed. And that is without mentioning duplications. What I would like is the ability to turn autodetection off and instead use a set of predefined applications. Is it feasible? Best, Alex.
  6. Is there a way to remove some of the autodetected apps from the dialog?
  7. Can anyone post an explanation how to work with the Lens Flare? I couldn't get any results from it Thanks in advance!
  8. Thanks pyrochild. I uninstalled it completely and now it does not want to reinstall. You and me both. Unfortunately, my computer does not concur. I opened a thread on the MSDN forums, hopefully I'll get some useful answers.
  9. My .NET 3.5 SP1 framework got hosed and refuses to reinstall. While I am trying to solve the problem, I have this question: can PDN be persuaded to use version 4 of the framework? I am running on XP pro SP3. Thanks, Alex.
  10. The blue/magenta format seems to be obscure (at least according to wikipedia).
  11. Sorry for resurrecting. I am also longing for Resynthesizer. There aren't any alternatives for its functionality really. If anyone can massage the source and create a Paint.NET plugin, they will have my eternal gratitude.
  12. I may be missing something but *exactly* outlining an irregular image was never very "easy" for me.
  13. Theoretically yes but in practice, the boundaries between the body skin and the background is not so well defined, particularly in the presence of clothes. The "magic wand" often fails to discern between them and using the lasso is very tedious, prone to errors and the results look bad. There must be a better way. Thanks, Alex.
  14. Thanks, I'll look at it. That will not work since I want the head (face) to stay the same and adjust the skin tone of the body (affecting the background as little as possible).
  15. There are a lot of fakes floating around where a head is photoshopped on a different body. I wonder how to do that in PDN? In particular, how one would adjust the skin tones of the head and the body to match without affecting the background? Any helpful plugins? Thanks.
  16. I never worked with additive layers. I wonder what else I'm missing... Out of sheer curiosity, is there a reason not to treat transparent the same as black? Will setting the background to black with Alpha=0 (effectively transparent) work as well? Thanks, Alex.
  17. Hi MadJik, thanks for your reply! I may be missing something but I don't remember anything in the 1st post regarding black background for the "Glitter" plugin. I am also a little confused about the need for a black background. Here is what I am trying to do: 1. Take an image 2. Add a layer (transparent background by default) and make it the active one 3. Select an area in the new layer 4. Randomly add white points in that selection using your "Stars" effect. 5. Blow the points up using your "Glitter" effect. Using a black background on the layer will prevent the original image from showing. Thank you and a happy 2010 to you too.
  18. Sparkle--Glitter doesn't seem to do anything for me. I put a bunch of white dots on a transparent background, run the effect and, after some chugging involving 100% CPU, nothing happened. Please advise. Thanks.
  19. I tend to install fair amount of trial versions of applications, play around with them and uninstall them before the trial period expires. I am not claiming my experience to be universal but I have never encountered such behaviour in other applications. It may not be a bug per-se but I'd file it under the "undesired behaviour" category.
  20. The first time that it happened, I killed it after (IIRC) 20 minutes or so after the progress bar reached 100%. That can't be normal.
  21. Hi pyrochild, thank you for your reply. Can you suggest how to do that? Does Rick publish a list of blocked plugins or is it "upgrade, find out plugins are blocked, uninstall, find the old version, install" dance? I use the oct/quad plugin occasionally to "create" shadows. I have never experienced a PDN crash or any other instability. Unless the alleged problem only started manifesting itself in 3.5, in which case I stand corrected. So let's say I write a plugin that, for some reason, gets blocked in a subsequent version of PDN. Since I cannot recreate the issue, I advertise that a "beta" build is available for those that want it (for error submission purposes or whatever). The end result is similar to what I suggested (in that it allows the user to load the plugin if they want to) except it provides less flexibility and more work on the user's part (renaming the DLL to make it load / not load, explicitly contacting the author, etc.) Fair enough. I understand that Evan has a new version out which I'll get the next time I have time for my PDN-related activities. However, I still believe that, in the general case, my suggestion merits consideration. Best regards, Alex.
  22. 1. Pyrochild implied that he knew how to override the block so I asked him to share the information. Surely it is a legitimate request. 2. I prefer a public discussion to private emails. I suspect Rick will also prefer a single public discussion to potentially a multitude of emails. I suspect that would only work for unsigned assemblies.
  23. That doesn't look like the best way to address the problem to me. I would much prefer a solution that would allow me to choose whether to load the "problematic" plugin or not on a case-by-case basis. The reasons are twofold: 1. If I come to depend on a plug-in in my workflow and it does not cause any problems in my scenarios, why should I be locked out of it? 2. If the plugin *does* cause problems in my scenarios, but its author cannot reproduce them, I now cannot help him debug the problem. This is what I would suggest: Option 1: pop up a dialog on startup with the names of all the "banned" plugins and a set of options for each: (*) Ignore ( ) Load ( ) Permanently delete Option 2: add a command-line argument like: /forceload= I understand that but I would still appreciate if you told me how to override the block. Thanks, Alex.
×
×
  • Create New...