Jump to content

Rick Brewster

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Rick Brewster

  1. Okay I've filed an issue over on GitHub, I'll look into it for 4.2.13
  2. Why do you have an extra copy of Paint.NET v4.2.10 in your Effects directory? That's completely baffling to me why you'd copy all of Paint.NET's DLLs into the folder for effect plugins 🤔 e.g. PaintDotNet.*.dll. Delete those files. PaintDotNet.Base, Version=4.210.7348.40816, Culture=neutral, PublicKeyToken=null @ C:\Program Files\paint.net\Effects\PaintDotNet.Base.dll PaintDotNet.Core, Version=4.210.7348.40816, Culture=neutral, PublicKeyToken=null @ C:\Program Files\paint.net\Effects\PaintDotNet.Core.dll PaintDotNet.Data, Version=4.210.7348.40816, Culture=neutral, PublicK
  3. Probably not. Laptops are very integrated systems. I would definitely start by trying to update the drivers. Windows Update may be able to do it all for you. My guess is you've got some memory (RAM) going bad somewhere. Higher refresh rates require more memory bandwidth, which puts more load on the RAM, which means more electrons and more heat (oh, maybe try cooling it down or something, too). Any kind of visual distortion could be an indication that the data being sent to the GPU is getting corrupted. You can also go into the app's Settings and turn off "Hardware accel
  4. Each layer you add at 20K x 20K will require an additional 1.6 GB of memory.
  5. Your video card (GPU) driver is probably old/broken. I'd focus on that.
  6. It's just aliasing. Nothing harmful. The cure would be worse than the cold.
  7. This isn't actually a new issue. I've had a bug filed for awhile. Thanks though!
  8. For example, this post is directly next to yours and has the right solution ... https://forums.getpaint.net/topic/116529-error-during-installation/ Please don't invent your own solution. It will just break things further.
  9. I have no idea why you did that. The solution to the MSI error is well known. You will still have problems updating to newer versions, you haven't actually fixed anything.
  10. This is a hotfix for a few important issues that have come to light with the 4.2.11 release. 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 should be offered the update automatically within the next week or so. You can get the update sooner by going to ⚙ Settings → Updates → Check Now. You can also download and install it directly from the website. Changes since 4.2.11: Fixed an error that was pr
  11. This is a hotfix for a few issues that have come to light with the 4.2.11 release. To get this update, make sure you have "Also check for pre-release (beta) versions" enabled in Settings, and then click on the Check Now button. (Unfortunately alpha/beta releases are not currently available for the Microsoft Store version of the app). You can also download install this build directly: https://www.getpaint.net/files/zip/test/paint.net.4.212.7453.40940.install.zip Changes since 4.2.11: Fixed an error that was preventing some old PDN images from loading (repor
  12. Here's a build with a hotfix: Install that and this will be fixed. The fix will also be a part of the final/public release of version 4.2.12, coming soon. This issue was only affecting PDN images saved with Paint.NET v3.5.8 or earlier (AFAICT).
  13. You can't install Paint.NET to an external disk, whether it's a USB stick or a hard drive. This is blocked by the installer because it caused all sorts of problems. It was really a complete disaster.
  14. That might actually be a bug in the new Paint.NET update. I can fix it pretty easily for 4.2.12, which is coming soon.
  15. Try renaming it to end in .png and see if it works. That's a common mistake (that is, accidentally saving as PNG type into a .pdn file)
  16. I haven't tried this yet but I've heard good things, https://www.autohotkey.com/
  17. btw I'm planning on making this easier. For instance, if you have both installed then when you launch one you'll see a message, "Hey you have both installed ... you want to uninstall the 'classic' version right?" and a button that just does it for you.
  • Create New...