Paint.net blog

[...] way we all win. As usual, you can download it directly from the website or you can use the built-in updater. Make sure that you enable “Also check for pre-release (beta) versions,” which [...]

[...] third beta build for paint.net 4.0 is now available! To install, you can either 1) use the built-in updater from a previous 4.0 build, or 2) use the built-in updater from v3.5.11 if you have " [...]

[...] final release will be sometime next week. As usual, to install, you can either 1) use the built-in updater from a previous 4.0 build, or 2) use the built-in updater from v3.5.11 if you have “Also [...]

[...] way we all win. As usual, you can download it directly from the website or you can use the built-in updater via Utilities –> Check for Updates. Here are the changes for this release: Fixed: [...]

[...] memory, instead of corrupt results. This does happen on 32-bit/x86, especially when using the Magic Wand on large images. [...]

[...] . Just about the slowest thing you can do in Paint.NET v3.5.x is to use the Magic Wand on a large image and then try to move, rotate, or combine that selection. The geometry [...]

[...] ” gradient type, and allows configuration of the repeat mode (none, repeat, wrapped). Magic Wand and Paint Bucket now allow live adjustment of Tolerance and the Origin (click location) after [...]

[...] draw another one, for instance. Most of the non-brush tools support this (e.g. Move, Gradient, Magic Wand, Paint Bucket, Text). Added a choice between Light and Blue color schemes to Settings. The [...]

[...] sometimes when pressing the right mouse button while already holding the left mouse button. The status bar now reports the correct selection location when it’s outside the image boundaries (e.g. [...]

[...] something like Alt+9 as the Home key Fixed some effects leaving an empty progress bar in the status bar Fixed the Magic Wand tool sometimes leaving an animated progress bar in the status bar Move [...]

[...] sometimes when pressing the right mouse button while already holding the left mouse button. The status bar now reports the correct selection location when it’s outside the image boundaries (e.g. [...]

[...] in the wrong location and/or at the wrong angle. When drawing a rectangle selection, the status bar would always say it had zero area. Selection adjustments would sometimes result in half-pixel [...]

[...] when the Shapes tool is active (Shift+A cycles backward) Fixed mouse input centering for the brush tools when antialiasing was disabled Re-enabled Ctrl+D as a “commit” button Moved the & [...]

[...] was getting in the way of some very important improvements to the input system for the brush tools. That in itself wasn’t a good reason for dropping it, but I had no hardware to test [...]

[...] start drawing a new shape via clicking and dragging, of course) Improved rendering quality of brush tools when antialiasing is disabled Improved performance of Shapes and Line/Curve tools on most [...]

[...] , Clone Stamp, Recolor) now have much smoother mouse input handling via GetMouseMovePointsEx. Brush tools (Paintbrush, Eraser, Clone Stamp, Recolor) now have soft brushes support via a “Hardness” [...]

[...] the application’s CPU usage was very high (e.g. slow CPU, slow GPU, disabled hardware acceleration) Reduced CPU usage of animated UI elements, especially when not the active [...]

[...] an installation error, and will be automatically repaired. Improved performance when hardware acceleration is disabled. All 7th generation Intel GPUs now default to hardware rendering. All older [...]

[...] , and will be installed if needed. A dual-core (or more!) processor is highly recommended. Hardware acceleration (GPU) via Direct2D is now supported. Please disable this in the Settings dialog if you [...]

[...] , CPU usage, and battery life. Because I’m using Direct2D and do this mask filling with hardware acceleration, CPU usage for an animated selection almost non-existent. Click on the screenshot below [...]

[...] 2) it only took a few minutes to implement. So, in 4.0.4, it’ll be back. Dramatically faster Magic Wand tool. I came up with a new algorithm to do the reverse scan-conversion that is needed here. On [...]

[...] (regression from 3.5). Faster: Move Selected Pixels has been significantly optimized. Faster: Magic Wand Tool has been significantly optimized. Faster: Working with aliased selections ("aliased [...]

[...] here’s an update that fixes them. Chiefly among these bugs are a break in how the Magic Wand tool works, a crash when using Effects, and one when trying to use the Shapes tool. As [...]

[...] this image to be 5x larger, giving me a 136 MP image (19,355 x 7,975). I clicked with the Magic Wand tool in the same spot in each, waited for the selection to be created, and then did some simple [...]