Jump to content

Ishi

Members
  • Posts

    471
  • Joined

  • Last visited

  • Days Won

    8

Ishi last won the day on January 24 2017

Ishi had the most liked content!

2 Followers

Profile Information

  • Gender
    Male
  • Interests
    Drumming, arts, writing, computers, toying with PDN

Recent Profile Visitors

2,675 profile views

Ishi's Achievements

Rising Star

Rising Star (9/14)

  • Reacting Well Rare
  • Very Popular Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

195

Reputation

  1. I only have the PDN filetype to open on Paint.NET. Also, the developer himself told me that thumbnails don't work for .PDN files if you only use the portable version. Not a huge issue for me though I have encountered a problem with the 32-bit portable version while opening huge .PDN files with many layers as it would needlessly use a lot of RAM.
  2. Or just copy the portable Paint.NET folder that you have now added with the Effects and FileTypes folders into every single machine of the same lets say x64 system via a network share whatever. Will save a lot of time.
  3. Yeah, I prefer portable installations too and manually configuring them. You also have to collect your desired plugin DLLs on the Effects folder and copy that Effects folder to every single portable installation of Paint.NET you have since if I'm not mistaken, a portable installation does not have the Effects nor the FilesTypes folder by default and even if it has, those would start empty by the way.
  4. No, the ZIP package of the official portable version as it is now, does not automate that. A Registry entry that automatically associates the file types would not be of much use if different users decide different directories to extract their portable Paint.NET installations other than C:\Program Files since a .REG file targets a specified path. I personally have my installation on the D: drive. Also, users would not want all file types to be associated with Paint.NET and for that lets say, they have to edit the REG file to only associate the file types they want. If ever, it had to be an installation setup made specifically for the portable version of Paint.NET with a custom installation option with checkboxes that lets you choose all these.
  5. I did this cause I currently use the portable version. You just right click a .pdn file, then click Open or Open with and just browse to the folder where you unpacked the files of the portable Paint.NET version and select the file paintdotnet.exe which is the actual program itself. There should be another one that is paintdotnet.ico but do not select that because its only an icon file. Make sure you check the box that says says use this program to open this kind of file and from then on, you could associate .pdn files to open with the portable Paint.NET. This however will not make image thumbnails for .pdn files like jpegs and pngs that only work if you installed the regular version of Paint.NET..
  6. First of all, please use the clone stamp tool. Here is a tutorial. You may also search the plugin for Paint.net called Content Aware Fill. It is the plugin that uses the adjacent background and colors to fill a selection you want to cover up.
  7. Hello, I was wondering if someone might look into making a plugin that adds preset color grading effects, with an intensity slider if possible. I find it troublesome to manually adjust color and tone settings that using presets would be much easier. Thanks.
  8. The 14MB one? I guess we have an attachment limit. Let me send the 14MB (3200x1280 res) one first to serve as a control but how do I send it? I just re-attempted to open the 29MB PDN now with the memory cleaner turned off this time and it went to a whooping almost 1.3GB usage. This file has 3000x2500 resolution by the way. I don't think I ever had a time that PDN's RAM usage went this high, at least that I know of. The 14MB (3200x1280 res) file still uses up the 800MB range when I opened it again now. I also opened other files with the following stats: (7.28MB file 200MB usage 1344x960 res) (13.1MB file 260MB usage 1600x1280 res) (//should have been closer to the 14MB file but no?) (20.9MB file 570MB usage 3000x2500 res) I guess we might have a resolution size threshold before it starts using too much RAM based from what I was able to gather but with some oddities.
  9. Alright, I will try the x64 Portable on my other PC rig on the same file or a copy of that file since it may have been corrupted when I terminated PDN portable yesterday using Task Manager when it was taking too long to load the file. This is an old x86 laptop by the way but I don't recall this issue with PDN standard 4.2.16 and below. Also, I have opened a 14MB size PDN just now and it seems OK except from the fact that I noticed needless memory spikes over 800MB that would drop down dramatically because I have a memory cleaner that is set to clear memory when usage goes way up. I exited PDN, turned off my memory cleaner and opened the 14MB file again and usage stays above 800MB for some reason before I even do anything. I opened a 6.4MB file and usage is just around 155MB. My theory is that this version and build (x86 4.3.2 Portable) has an issue of using too much memory on larger files.
  10. Also this version and build (4.3.2 x86 Portable) seems to have trouble loading a PDN file that I know has lots of layers and content. That PDN project was created on this same old machine using a standard version of PDN 4 last year and and its 29MB in size but did not have that problem though understandably it loads slower than others. I took several minutes and the RAM usage of PDN would spike way up whilst loading. Now it gave me an error saying the file is corrupt or was saved on an earlier version of Paint.NET.
  11. Thanks for the update Rick. I just upgraded from 4.2.16 and I removed that version using Revo Uninstaller completely before using the portable build of this new v.4.3.2. Things are snappier than usual. However, since the previous version was uninstalled completely, my PDN files were again alienated from Windows that I had to use Open With and browse to the new PDN exe to open the files. That did not restore the thumbnails on Windows Explorer to show image thumbnails. I now only have the PDN icon on them. How do I fix this? Is this a natural consequence of using a portable build and removing the standard one? Thanks.
  12. Thanks for the tip. I have the updater disabled on my standard PDN though. I always prefer a manual update on every program that I use.
  13. I'm unpacking it right now. This portable build has so many directories. Where do I put the plugin DLLs here? Thanks.
  14. Am I right in saying that this version is the first to have an official portable build of PDN? Also, would it be fine to totally clean uninstall my old standard version of PDN with Revo Uninstaller and use the portable PDN with its pre-bundled .NET 5? Thanks for the hard work with this program.
  15. I disabled hardware acceleration. Magic wand worked better this time, without the square glitches. Re-enabled hardware acceleration just to make sure, and so glitch came back. Disabled it again and works fine again.
×
×
  • Create New...