Rick Brewster

  • Content Count

  • Joined

  • Last visited

  • Days Won


Rick Brewster last won the day on January 13

Rick Brewster had the most liked content!

Community Reputation


About Rick Brewster

  • Rank
    Paint.NET Author and Developer
  • Birthday 06/16/1981

Profile Information

  • Gender
  • Location
    Bay Area, CA

Contact Methods

  • Website URL

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Okay well then it could be an out-of-date GPU driver, or a setting in the GPU control panel. We've seen options for forcing discrete vs. integrated GPU as a big problem causer. You could also try removing all of your plugins -- easier done than said, actually. You just go and rename Effects to Effects.bak, same for FileTypes and Shapes, and then launch the app. If things still crash then just rename them back.
  2. Alright, well, I'm closing this thread then. No need to continue the conversation.
  3. 4.1.4 still has important bugs that have been fixed in the meantime. I really can't stress how important it is to be using the latest version! Just scroll through https://www.getpaint.net/roadmap.html to see all of the bug fixes, performance improvements, and added features. You really can get used to the icons. Just give it some time. I promise you'll get used to it, and all the other stuff (fixes, performance, features) is really worth it.
  4. I see two likely culprits in the list of native DLLs: You should try disabling/uninstalling and see how things go. If things work, then one or both of those apps (whatever they are) likely have a bug in the way they're hooking into apps. Apps that hook other apps (via DLL injection) are notorious for causing crashing like this. Happens all the time.
  5. You might also look into running: 1) chkdsk 2) sfc /scannow (you should be able to find info on these with a quick google search) It's possible that a system file has become corrupt and is interfering with image resource loading (e.g. app icons in the UI). I say that because of the details of the exception in the crash log: Exception details: System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception. (PaintDotNet.Controls.DocumentStrip) at System.Drawing.SafeNativeMethods.Gdip.GdipImageForceValidation(HandleRef image) at System.Drawing.Image.FromStream(Stream stream, Boolean useEmbeddedColorManagement, Boolean validateImageData) at PaintDotNet.Resources.PdnResources.LoadImage(Stream input) in D:\src\pdn\src\Resources\PdnResources.cs:line 377 at PaintDotNet.Resources.PdnResources.GetImage(String fileName) in D:\src\pdn\src\Resources\PdnResources.cs:line 361
  6. What @welshblue said. You're used to the old icons and you liked them, nothing wrong with that. But, the new ones will be just fine once you give them a little bit of time to get used to them. There is no going back.
  7. This has nothing to do with the NVIDIA bug, @Pixey. That has been fixed now with something that auto-detects the crash and tells the user what to do. This just looks like a corrupt installation. Reinstalling should fix it.
  8. You can just edit the crash log to remove any information you don't want to make public. It's just a text file.
  9. It's planned for the 4.3 release. The foundation was already put in with the 4.2.6 update -- tablets and pens can finally be used to draw without weird glitches at the start of each stroke. Pressure sensitivity and a big upgrade to the brush system is for 4.3.
  10. I've been working on 4.2.9 for the last month and a half, and really put some work into some big improvements for performance and memory usage. These improvements cut across almost everything you can do in the app, so having a lot of participation in the alpha and beta builds will be really important. Please install!!! 😁 Memory usage is way down, especially when opening many images. Undo/redo should be a lot faster. Finishing/committing actions with most tools should be a lot faster. Effect rendering, particularly when you have a complex selection, should be much more responsive. A lot of these optimizations will scale with CPU core count (more faster CPU = more faster PDN), but should also show great improvements on low-end systems (e.g. dual core CPU, low-power laptop). It's win-win! 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). Changes since 4.2.8: Reduced overall memory usage (commit size) by up to 1/3rd by eliminating the use of and need for a per-image scratch buffer Greatly improved performance when finishing actions of most tools by employing a shared cache between the render and commit code paths Reduced memory usage when working with many tools by consolidating homogenous tiles (those that are comprised of a single pixel value) Significantly improved performance of most history actions (commit, undo, redo) by switching from NTFS compression to multithreaded LZ4 compression for history files Significantly improved performance of undo/redo with very complex selections (like from the Magic Wand tool) Improved performance of Image -> Flatten (also affects flattening when saving) Improved performance of the Invert Colors and Desaturate adjustments by disabling hardware acceleration for them (too much overhead in copying tiles to the GPU for such trivial rendering kernels) Improved performance when saving by moving thumbnail rendering for the File -> Open Recent menu to a background thread Reduced memory usage when printing, and removed a rare crash that would happen if the scratch buffer couldn't be acquired Added a "busy spinner" to the canvas when using the Magic Wand and Paint Bucket tools Improved performance of effect rendering when a complex selection is active (improved caching) Fixed a layout bug with the image list button Fixed an error that prevented saving some images as JPEGs if they had EXIF Interop metadata (PropertyNotFoundException) Fixed a crash when running on a CPU that supports AVX but with an OS that is configured to not support it (via bcdedit /set xsavedisable 1) Fixed a crash when pressing the spacebar after switching to a tool but before it has received any mouse input events Fixed a rare crash when opening the Levels adjustments with certain types of selections Fixed a crash when checking for updates with an expired alpha/beta build Fixed a crash (FileLoadException) when DLLs are not updated by the updater. Updated WebPFileType plugin to version (thanks @null54) I am hoping/planning to push out the final release by the end of January. Enjoy!
  11. You were on 4.1.6 before the update, or after? 4.2.8 is the latest version, not 4.1.6.
  12. Yeah it's really even not that big of a change, in my opinion. (going from 7 to 10, I mean) Better to get started on it now -- it's only going to get harder as time goes on
  13. If you run out of memory then you won't be able to add more layers. There's no hard limit.
  14. FYI: the upcoming 4.2.9 update should improve this quite a bit. I've switched to using LZ4 compression for history files, and I've multithreaded it and applied some other wizardry. Adding more cores will improve performance for just about every action that results in a history item. Which is pretty much every action, including flattening. And even if you don't add cores it will be a lot better.
  15. This is exactly how it's supposed to work