Sign in to follow this  
Rick Brewster

Paint.NET v3.5.11 BETA is now available

Recommended Posts

This is probably not the update you were expecting :) I need to push out an update to v3.5 in preparation for the eventual release of v4.0, and it’s necessary to do this sooner rather than later to make sure everyone is up-to-date by then. I’m releasing a “beta” today to make sure everything is still working (compilers, packagers, updaters), and then I’ll be pushing out the Final/RTM in a few days.
 
The primary goal of this update is preparing for the v4.0 release: v3.5.10 will not be able to offer the v4.0 update, but v3.5.11 will. I’m not a fan of putting out an update for purely infrastructure purposes so I’ve also reverse-ported a handful of low-risk improvements from the v4.0 code base. This 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 you can do by going to Utility –> Check for Updates, and then clicking on the Options button.

 

Here are the changes for this release:

  • Fixed: The Gaussian Blur effect was incorrectly calculating alpha values for non-opaque pixels. (http://forums.getpaint.net/index.php?/topic/18483-gaussian-blur-mistreats-alpha/)
  • Improved performance of the Sharpen effect by about 25%
  • Improved performance of the Median effect by about 30%
  • Improved performance of the Fragment effect by about 40%
  • Improved performance of the Unfocus effect by about 100%
  • Reduced memory usage when many selection manipulation operations are in the history/undo stack (the undo data is now saved to disk)
  • The built-in updater now supports upgrading to paint.net 4.0 (once it’s available)

Enjoy!

 

See my blog post for more: http://blog.getpaint.net/2013/08/15/paint-net-v3-5-11-beta-is-now-available/

 

(Please note that the update manifest files for the built-in updater are still uploading, so "Check for Updates" may not work for another hour or so. It should all be working for everyone by about 6pm PST.)

  • Upvote 2

Share this post


Link to post
Share on other sites

Will installed effects still remain in the program when I update, or will they need to be re-installed?

Share this post


Link to post
Share on other sites

I am so looking forward to 4.0, but performance improvements are always a welcome gift. :P

  • Upvote 1

Share this post


Link to post
Share on other sites

3.5.11 BETA installed successfully. Two things to note.

1. I run Pdn as administrator (for codelab) - the installer shows an error when trying to start from the final installer screen as it doesn't have the privilege level. However it starts fine from the desktop shortcut and appears to have installed correctly.
(Simply uncheck the start Pdn checkbox if you're running Pdn as administrator.)

2. Median still increases zero alpha by one each time it is run - no biggy, I just assume objects have an alpha greater than 10 in plugins of mine that it affects. (Or use 'Alpha-threshhold' plugin after using Median).

Finally, many many thanks for all your hard work, maintaining 3.5 and developing 4.
Pdn is a pleasure to use and remarkably stable, (especially considering all the half-finished plugins I have installed!   :D  ).
 

Share this post


Link to post
Share on other sites

ERRRRGHHHHHMEGAWD UPDATES MEHEHEHEHE

On a more worded response, really chuffed with this update, hugely excited for the release of 4, can't wait to start writing some tutorials for the new shizzle!

Share this post


Link to post
Share on other sites

Hi,

with previous versions of Paint.NET I got used to deploy it as MSI via group policy in my environment, customizing the DESKTOPSHORTCUT and PROGRAMSGROUP entry in the MSI file. The 3.5.11 MSI won't let me use my previous transform file :-/

So i checked out the first MSI, extracted while 3.5.10 was still installed. From the previous installation, the /createmsi switch created the msi containing my customized parameters - hard coded!

Afterwards I uninstalled Paint.NET and extracted the MSI again with the /createmsi switch. Now the extracted MSIs didn't contain customized parameters and what was confusing me at the first sight, the PROGRAMSGROUP entry was not there anymore!

Creating the transform file by adding the missing value manually it was easy to recreate the transform file for the new version's MSI. It would be nice if the PROGRAMSGROUP entry would have been there.

But I think extracting the MSIs from the original setup file shouldn't overtake customized values hard-coded, although an old version is installed on the specific machine with customizations made by a transform file from a previous installation.

The new package should extract cleanly, and only when installing the MSI on a machine respect the existing customized values at the machine where it is installed on.

But beside this observation I like the way you provide a MSI from another installer in almost no time and without the need to have any frameworks like WiX installed.

Another question: will the future version 4.0 will contain instructions to uninstall previous 3.5.10 and older versions if it is detected on the target machine? ("major upgrade")

Share this post


Link to post
Share on other sites

When you run /createMsi on 3.5.11's installer you will still need to re-specify all the customized MSI property values. It doesn't automatically pick them up.

Share this post


Link to post
Share on other sites

I just wanted to add the new (and clean) MSI to the group policy for deploying Paint.NET. The version is shown as 3.61 instead of 3.5.11. Is this "just a typo" or is this version number intended to be displayed?

Also both the x86 and x64 versions are updating the x86 and the x64 version by default. Is this behavior intended? Maybe both packages have the same upgrade code.

Share this post


Link to post
Share on other sites

I'm looking forward to 4.0 as well. I hope 4.0 will have a Single Windows option. Trying to keep up with 4 separate windows gets a bit nerve racking. 

Share this post


Link to post
Share on other sites

I just wanted to add the new (and clean) MSI to the group policy for deploying Paint.NET. The version is shown as 3.61 instead of 3.5.11. Is this "just a typo" or is this version number intended to be displayed?

Also both the x86 and x64 versions are updating the x86 and the x64 version by default. Is this behavior intended? Maybe both packages have the same upgrade code.

 

It's not a typo, it's just the number I had to use to satiate MSI.

I'm looking forward to 4.0 as well. I hope 4.0 will have a Single Windows option. Trying to keep up with 4 separate windows gets a bit nerve racking. 

 

There is not going to be a "SIngle Window" option. I've never said anything about implementing a feature like that.

Share this post


Link to post
Share on other sites

It's not a typo, it's just the number I had to use to satiate MSI.

 

There is not going to be a "SIngle Window" option. I've never said anything about implementing a feature like that.

I know you didn't say that. It was just a suggestion. Sorry if I worded my statement incorrectly. 

Share this post


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