Rick Brewster

You could post the source code (GitHub preferred but a ZIP is fine too). I’m pretty sure someone would be willing to get it fixed up.

CPU temperatures can ramp it very high and very quickly (like <1s). The temperature that the AIO reports is not the same as the temperature of the CPU die itself.

Hi @xod, great stuff! Because your plugin is not self-contained (it's not a single DLL), it is required that you publish it according to these rules: https://forums.getpaint.net/topic/118743-new-packaging-requirements-for-plugins-starting-with-pdn-43-net-5/, Imagine if other plugins needed to use SkiaSharp, and they wanted a different version, and everyone tried to install both plugins into the same directory. It will not work out well. These rules help to prevent that. Just fix that up, republish, and you're good to go!

Could also easily be overclocked or under-cooled. Saving .PDNs is heavily multithreaded, and the 14900K is a super hot CPU that needs high quality components (power supply, cooler, RAM, etc.) that are properly configured

Sounds 100% like bad hardware components. Paint.NET can’t cause your system to crash and burn that hard without help from bad hardware.

That’s exactly what it is. NVIDIA driver bug. Make sure you have the latest version of it.

btw in PDN v5.1, I'm hoping to include a HistogramEffect2 that I've just got working. Instead of outputting a normalized array of floats for the chosen channel, it will output an array of Vector256<long> with direct value counts for all channels. It will also work on images up to 1M x 1M px (so, 1 terapixel 😂). I'm using this for porting over Auto-Level, Levels, and Curves over to GPU rendering.

5.0.13 included a fix to enable this specific plugin to work again.

It's also just a bad strategy to use if you're lobbying for a feature. I'm never going to add something because someone was grouchy and argumentative at me. @Tactilis has successfully lobbied for several things and uses a straightforward evidence-and-logic-based discussion strategy.

Paint.NET is not the right software to use if you require a CMYK-based workflow. Simple as that.

Just because you don't know the reason doesn't mean there isn't a reason. And nobody's forcing you to do anything. "There is no reason..." is a cheap debate tactic that attempts to shift the burden of proof to the other side, and I really recommend avoiding it. Software is complicated and things take time. Just because something is missing doesn't mean it's an intentional/desired design choice.

Also the #1 reason for signatures not verifying is that your system date/time is wrong. I’d check that first. The #2 reason is that you haven’t been installing Windows Updates. They do send down updates to certificate stuff from time to time, and Paint.NET is now using a newer certificate authority (it’s one of Microsoft’s, via Azure Code Signing). So make sure you’re caught up with all system updates.

Literally no one here is saying that.

I dunno that might be an interesting thing to add though

You can also use the Pan (hand) tool. I tend to use Space + Left Mouse Button for panning, which is available when any tool is active and when View -> Zoom to Windows is not enabled (it's always enabled after opening an image). After opening an image, press Ctrl+B to toggle off View -> Zoom to Window, then Space + LMB for panning.

Sounds like Effects -> Blur -> Surface Blur ?

Looks like a mixup between linear and sRGB colors. Should be a straightforward fix.

This is a small update that fixes some bugs, adds a new Latvian translation, and updates the bundled AvifFileType plugin. Get the Update There are two releases of Paint.NET: Microsoft Store release (recommended) You can purchase it here. This helps fund development and is an alternative or supplement to sending in a donation. If you already have it installed, the update should happen automatically once Microsoft certifies the update, usually within the next day or so. To get the update immediately (once it's certified), you can follow the instructions listed here. Classic Desktop release Download the installer from the website. This is the recommended download if you don't have Paint.NET installed. It can also be used to update the app. If you already have it installed, you should be offered the update automatically within the next few days, but you can also get it immediately by going to ⚙ Settings -> Updates -> Check Now. Offline Installers and Portable ZIPs are available over on GitHub. Change Log Changes since 5.0.12: New: Latvian (lv) translation Fixed the Colors window sometimes showing up at weird sizes if the system scaling (DPI) was changed between sessions Fixed a crash in the Simulate Color Depth plugin (reported by @toe_head2001) Updated the list of libraries/contributors in the About dialog with some libraries that got missed (mostly from Microsoft) Fixed some clipped/invisible text in the installer when going through the Custom flow Added the GPU driver version to Diagnostics info Fixed HistogramEffect's Bins property https://forums.getpaint.net/topic/124026-getting-an-error-when-trying-to-use-histogrameffect-codelab-sample/?do=findComment&comment=618040 Updated the bundled AvifFileType plugin to version 1.1.30.0 (thanks @null54!)

Okay thanks; I've filed a bug for this, but I don't have an idea when I'll be able to look at it

Already answered by @Tactilis above. Upgrade your PC so it has more memory (RAM). This may require buying a new PC, since it looks like you're using a laptop and those can't always have their RAM upgraded. I should probably fix PDN itself so it reports this to the user (you) as Out Of Memory instead of File Is Corrupted.

Only History and Layers can be resized that way.

I got it down to 9.5s by calculating 3 px at a time 😎

Looks like a GPU driver or GPU configuration (control panel) problem, or you have some other software that’s interfering or causing the glitch. Like recording/broadcasting or overclocking software.

(Correction to data above: I've been using a 12K x 8K image for performance testing, not 18K x 12K)

I was able to convert this to a compute shader that calculates 2 pixels at a time: 10.5 seconds 😁 Increasing that to 4 pixels reduced performance, likely because of occupancy spillage.