Sign in to follow this  
Rick Brewster

paint.net 4.1.2 is now available!

Recommended Posts

This is a small update that improves startup performance, fixes some bugs, and addresses two security vulnerabilities. Administrators who manage deployments of Paint.NET are urged to begin updating immediately.

 

If you’re using the Windows Store release, you should get the update automatically within the next 24 hours. You can also force an update check by following these instructions.

 

For the Classic release, you can use the built-in updater by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website.

 

Changes:

  • Improved startup performance if "a lot" of effect plugins are installed. More optimizations are coming in the next update.
  • Fixed: Pixel grid no longer draws some dots darker than others at some zoom levels, as reported at https://forums.getpaint.net/topic/112794-pixel-grid-rendering-problems-when-zooming/ 
  • Fixed: Radial Blur was not handling alpha correctly
  • Fixed: IndirectUI ColorWheel swatch is now rendered correctly (without the fading alpha gradient)
  • Fixed: The tooltip describing the shortcut key for tools now indicates how many times to press the key (e.g., press S four times for Magic Wand selection)
  • Fixed: Pressing Escape to deselect now works with all tools (this bug was introduced in v4.0)
  • Fixed: Images with variable alpha were not displaying correctly at some zoom levels. They were "too dark" in translucent regions.
  • Fixed: For the Store release, launching with the paintdotnet: protocol no longer shows an error if no parameters are provided (thanks @Bruce Bowyer-Smyth!)
  • Fixed a crash for some effects that were rendering too quickly
  • Fixed a bug in the Image->Resize dialog where the asterisk and the note about which resampling mode was being used, e.g. "* Bicubic will be used," weren't going away or updating correctly
  • New: Added a /set:SETTING=VALUE command-line parameter. This is specifically useful for disabling hardware acceleration if the app won't start or you can't reach the Settings dialog. This is also necessary for the Store release whose virtualized registry cannot be edited. To launch the Store version with hardware acceleration disabled, go to Start -> Run and type in "paintdotnet:/set:UI/EnableHardwareAcceleration=false" (without quotes) and press OK
  • New: Added detection for when "Diebold Warsaw" is causing Paint.NET to crash. The error message will indicate this cause.
  • Fixed: Addressed CVE-2018-18446. Credit goes to Bruce Bowyer-Smyth.
  • Fixed: Addressed CVE-2018-18447. Credit goes to Soroush Dalili from NCC Group.
     

Enjoy! :)

  • Like 2
  • Upvote 2

Share this post


Link to post
Share on other sites

Thanks for the update.  However, I hate being a pest, but I really appreciate having the shortcut for CTRL+bracket to increase/decrease brush size by 5 pixels (like it used to) without having to leave the canvas and hold down CTRL and repeatedly click on the plus or minus button.  I hope this shortcut could be added back as I really miss this feature a lot.

Share this post


Link to post
Share on other sites
8 minutes ago, TrevorOutlaw said:

Thanks for the update.  However, I hate being a pest, but I really appreciate having the shortcut for CTRL+bracket to increase/decrease brush size by 5 pixels (like it used to) without having to leave the canvas and hold down CTRL and repeatedly click on the plus or minus button.  I hope this shortcut could be added back as I really miss this feature a lot.

 

That shortcut hasn't been removed...

 

Edit: If you're still having trouble getting it to work, please make a post over in Troubleshooting

Share this post


Link to post
Share on other sites

Please note that I've temporarily halted the rollout of this update. You can still install it manually by downloading from the website.

 

I'll be pushing out a 4.1.3 update soon.

 

There's a problem with systems crashing while trying to zoom if the GPU doesn't support DirectX 10. Yeah, it sounds very peculiar, but is actually related to the pixel shader I wrote to fix the double-alpha issue ("Images with variable alpha were not displaying correctly at some zoom levels. They were "too dark" in translucent regions.")

 

I thought this was only affected ooolllddd hardware like the NVIDIA nForce (remember those?!) but it's also affecting more mainstream hardware like the GeForce 7300 (not the 730, that's much newer).

 

If you have no problems with zooming, there's no need to worry. Nothing else is affected.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this