toe_head2001

I did some bisecting this afternoon. It's been broken for approximately 1 year. Working: 22.4.1 (April 5, 2022) Broken: 22.5.2 (May 23, 2022) (there a few minor releases between these two versions that can be bisected further, but I just used what was already in my Downloads folder) I also submitted a bug report to AMD.

The updated /ignoreCorruptPDNChunks parameter was included in v5.0.4. https://forums.getpaint.net/topic/122540-paintnet-504-is-now-available/

I just tried this with my RX 6600. Can confirm the issue. Definitely a driver bug when the image resolution is high enough. I'm not sure if this a new bug with the latest Radeon driver, as I never tried using such a large image before. I will do some version bisecting over the weekend... to satisfy my curiosity.

Settings -> Diagnostics -> Open crash log folder

I don't understand your question, since "thread" and "topic" are synonyms in this context.

Also make sure the graphics driver for your G2020 chip is up-to-date. https://www.intel.com/content/www/us/en/products/sku/71070/intel-pentium-processor-g2020-3m-cache-2-90-ghz/downloads.html

Paint.NET is crashing without a crashlog? Okay, let's try this: Right after the paint.net crashes, please open the Windows Event Viewer and look in the Application log. (Event Viewer -> Windows Logs -> Application) The items should be sorted by datetime, so the most recent item should be at the top of the list. Let us know what you find.

The domain is already registered by a large paint company. They are unwilling to sell the registration for a reasonable price.

You posted the diagnostic info. We need to see an actual crash log. Settings -> Diagnostics -> Open crash log folder

Edit -> Paste into New Image (Ctrl + Alt + V) There's no other way. Create a template file with your preferred resolution, and start paint.net by opening that file.

@CircleBox I found the cause the crash. It is indeed caused by bad values being passed to DrawArc. The pen is too wide for the bounding rectangle! I am able reproduce this in LINQPad. (I'm using values I pulled out of the VS debugger at the time of the exception.) Changing the pen width from 2 to 1, and the tiny arc is drawn successfully: I'll post a bugfix release sometime within the next week or so.

Hi @Lisa You can try the Frames plugin. https://forums.getpaint.net/topic/6210-frames/ If you actually provide a link to the video, we could more easily identify the specific plugin.

Hi @CircleBox Despite the exception message, this is not a VRAM issue (or even a system RAM issue). Most likely, a bad value was simply passed to the DrawArc function. If you have the steps to recreate the crash, it can potentially be fixed. Alternately, you can try BoltBait's Hue / Saturation+ plugin.

Make sure you're installed the plugin correctly. You should have 4 files within a subfolder. Within Paint.NET, you will find it in the menus: Effects -> Tools -> Dynamic Draw

@Diaveon Please read our community rules: https://forums.getpaint.net/topic/2932-read-first-the-rules/

Do you use the "Controlled folder access" option in Windows Defender? Or use another overly aggressive security software?

We also have a dark theme here on the forum.

Did you obtain Paint.NET through the Microsoft Store?

I've fixed the image in Manc's post so it displays properly.

I'm not sure I understand your issue. Is there an actual deficiency with BoltBait's plugin? or are you just unwilling to adjust to a different plugin?

You simply delete those two DLL files.

You can't set a default size for new images. You're seeing 2,000 x 1,500 because there's an image on your clipboard with that size.

It's possible, but adding new functionality to this plugin is not high on my list of priorities. This plugin needs a complete rewrite too. Sepcot originally created it 16 years ago, and so it uses some outdated coding conventions. Then I retrofitted UPC functionality into it... in a very hacky way.

Try the Stray Pixel Remover plugin. https://forums.getpaint.net/topic/26533-stray-pixel-remover/

According to Microsoft's documentation, a value of 0 is acceptable for an uncompressed RGB bitmap. https://learn.microsoft.com/en-us/windows/win32/api/wingdi/ns-wingdi-bitmapinfoheader Your friend should submit a bug report for whatever software he is using. As a workaround, he can also re-encode the bitmap using a tool like Imagemagick, which is included by default with many GNU/Linux distros.