Rick Brewster

Administrators
  • Content Count

    16,253
  • Joined

  • Last visited

  • Days Won

    138

Everything posted by Rick Brewster

  1. 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.
  2. 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 1.3.2.0 (thanks @null54) I am hoping/planning to push out the final release by the end of January. Enjoy!
  3. You were on 4.1.6 before the update, or after? 4.2.8 is the latest version, not 4.1.6.
  4. 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
  5. If you run out of memory then you won't be able to add more layers. There's no hard limit.
  6. 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.
  7. This is exactly how it's supposed to work
  8. Yeah the protocol stuff is really picky about quotes and spaces. Once you get it right, it's happy, but it's super mean until then.
  9. Also, paintdotnet:/repair doesn't work from the command-line. You have to use start paintdotnet:/repair
  10. /repair is not applicable for the Store version, only the Classic version. It is ignored by the Store version. PdnRepair doesn't exist for the Store version, as its job is to do an MSI repair and Store uses APPX instead of MSI. Technically you can just run PaintDotNet.exe with the /repair switch, but that defeats the point of using /repair because you may as well have just run PdnRepair if you can find PaintDotNet.exe.
  11. Don't turn on sharpening globally. Turn it on for each game. There's no possible fix on my side, you just have to avoid using global settings like this. It's just a dumb thing NVIDIA did with their driver.
  12. If you're specifying MSI properties then the .MSI file has those baked in and it will invalidate the digital signature. A normal installation, with the EXE, will use the unmodified MSI files and these do have a valid digital signature. You can see for yourself if you 1) boot up the installer, 2) leave it alone once it gets to the first part of the wizard (where it asks "Quick" vs "Custom") and then 3) navigate to %TEMP%\PdnSetup and find the *.MSI files. I really don't recommend using MSI/GPO deployment if you can. It's much better to use the EXE.
  13. One week left! IT'S TIME TO UPGRADE EVERYONE It should still be free ... https://wccftech.com/how-to/upgrade-windows-7-download-windows-10-free/ And via ZDNet: https://www.zdnet.com/article/heres-how-you-can-still-get-a-free-windows-10-upgrade/
  14. @TrevorOutlaw I'm guessing this only started happening since 4.2.6? (not in 4.2.5 or earlier?) If you or someone else can get a reliable repro -- and often a video really helps illustrate how to do it -- I will definitely look into it.
  15. It's probably a DDS that you saved with an extension of .BMP.
  16. You're bumping into this: https://forums.getpaint.net/topic/115743-v428-attempting-to-select-layers-with-spacebar-causes-application-crash-reproducible/ for I've fixed it for the next update, but for now you'll just have to be careful with the spacebar ... make sure to wiggle the mouse over the canvas first whenever you switch tools
  17. If you send me the PDN file I can look into it, but it's worth pointing out that turning off the pagefile doesn't actually help performance. That's just one of those "tweaker" superstitions.
  18. And if possible please attach the image (may need to ZIP it up first) Yeah please provide information other than "it doesn't work" when reporting an issue ... we're not psychic :-\
  19. The Kotaku article has some poorly chosen quotes that paint Macaw45 in the wrong light ... Better to read the original Twitter thread
  20. Yeah this is a bug with the "hold spacebar to pan" functionality. I've got it fixed for the 4.2.9 release, which should be gathering momentum towards release now that Christmas break is almost over. It happens if you switch to a tool (any tool) and then press spacebar before the mouse has made any contact with the canvas. The "last mouse position" is initialized to NaN (not a number, kinda like null), but isn't checked against that before it's used when trying to deal with the "spacebar pan" functionality.
  21. I'm moving this thread over to the Translation and Localization section where it really belongs
  22. @Ferdari, you're asking others to do a lot of work on your behalf, and making assumptions about a lot of other people's decisions and motivations to fit your personal narrative and agenda. Chill out! @Ego Eram Reputo's suggestion is the best one. If you truly are an "advanced user" as you claim to be, you'll figure out a solution. Maybe you fork the plugin, maybe you just find or write a little command-line utility to automate stripping out the metadata. Maybe you'll even come full circle and share your solution with us. Stop expecting everyone else to cater to your demands, and stop expecting everything to be super easy. That's not how you make progress, here or in life.
  23. Yes, you'll need an account at Crowdin. I can't just take translation "drop offs", I need someone who's going to be able to translate changes that are made over time.
  24. You can also see if this toolbar setting does anything for your needs: