Jump to content

RandomPerson1

Newbies
  • Posts

    4
  • Joined

  • Last visited

RandomPerson1's Achievements

Newbie

Newbie (1/14)

  • First Post
  • Week One Done
  • One Month Later
  • One Year In
  • Conversation Starter

Recent Badges

0

Reputation

  1. So, I am aware of the fact that over the years a lot of people have already made posts asking for the bug to get fixed that sets the black level of a color set in the HSV part of the color window always one unit below of what you actually set. My current workaround for this is to simply set the black level of the color one unit higher, when I want to have the black level of 50, I set it to 51, and when I check the color with the color picker tool it always gives me the one unit subtracted color of 50 in this case. Intentionally setting the color higher of what I want to let the bug " fix it out ". But, well, if this is really something that always happens when changing the value in the HSV slider by just one number... Can't you just +1 the black level of the color up in the code to get the bug fixed? I have read that this problem is caused because of the nature of RGB and HSV as they are two different ways of calculating color, and that converting between them is never going to be perfect. Yet at the same time, maybe just a simple if statement in the code is really all it needs to fix this. This way the developers don't have to fix an always imperfect conversion between color systems, but just do something like: " If: black level HSV color slider has been changed: black level = +1 " Please Paint.net Developers, fix this bug. Maybe this solution is going to work.
  2. Well, I was giving Aseprite a short try in the demo version, and honestly I am pleased with the pre-color palettes avaible that pretty much make this problem obsolete as I can always rely on the palette and dont have to pic the color from the image itself. Therefor, I think this post can be locked, Thank you for your support. If it stays online I think other people who run into this problem can find quick support here Again, thank you for the fast support and the additional knowledge you gave me! Good night.
  3. First of all, thank you for your extra quick Reply, and by reading your explenation, it makes all of this way more logical to understand than " random bug lololol ". However, isnt there any way to bypass this? I already was thinking about buying a software like Aseprite. But I dont think thats a good idea.
  4. Greetings fellow Paint.net enthusiasts! I am using paint.net for multiple years now, and I always enjoyed it as it serves me the basic tools I need for 90 % of scenarios. However, there is a very weird bug haunting me since all these years strongly decreasing my work efficiency allot, so I kindly ask for help in this Thread. The bug goes as the following: Everytime I decrease or increase the V value of the main or sub color, switch to the other color and then switch back by the icon in the Colorweel, the V value just decreases itself by 1. exactly 1. In most cases, something like this propably wont be that problematic, but in my case, as I am using paint.net for Pixelart only, its really bugging me on in things like smooth color transition and other stuff, where those values HAVE to be perfect. I hope that somebody allready got a proper solution for this. Hopefully I gotta get back to Pixeling real quick Have a nice day.
×
×
  • Create New...