Jump to content


  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

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

taoyue's Achievements


Contributor (5/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. Please send me a copy of the PSD file, and I'll take a look at it. My email address is listed here: https://www.psdplugin.com/ If the file is too big to fit in an email, please upload it to OneDrive and share the file to my email.
  2. Ievgen actually contacted me a couple weeks ago, and I explained that I couldn't take the changes. There are a lot of issues with the approach that he has taken. It's using the layer name as a form of markup, but the text is actually localized. Paint.NET can't view or edit the layer groups, and most of the blend modes will not work correctly. You'd be able to save a file, but you wouldn't know what it looked like until you load it into Photoshop. You also wouldn't know if you'd screwed up the layer groups until you'd already overwritten your original file. It's just very problematic to do this in a filetype plugin. Layer groups are really an image editing feature. Whenever Paint.NET gets layer groups, I will update the PSD Plugin to load and save layer groups. But not before.
  3. Can you strip down the file to a minimum repro case? Remove half the layers and see if the PSD Plugin can load it. If it loads successfully, then the problem was in one of the layers that was deleted. If it still doesn't load, then the problem can be found in one of the layers that remains. Keep halving the layers until you're down to one, and then erase the contents of the layer. The error message indicates a parsing error, so I don't need to look at the contents of the file. The image can be blank. As long as the file still fails to load in the PSD Plugin, I can take a look at the structure of the file to see what's causing it.
  4. Please send me a copy of the PSB file that causes this error. If the file is too large to email, please upload it to OneDrive and share it to me. My email address is at the top of the PSD Plugin website: https://www.psdplugin.com/
  5. There is not enough information yet to diagnose the problem. Please post screenshots of File Explorer, opened to the following directories. Use Detail mode, and maximize the window so we can see filesize and timestamp. C:\Program Files\paint.net C:\Program Files\paint.net\Effects C:\Program Files\paint.net\FileTypes
  6. This is not a common error message. Please send me the PSD file so I can investigate the problem further. Use the email address at the top of the PSD Plugin web page: https://www.psdplugin.com/ If the file is larger than about 20 MB, please upload it to OneDrive instead and share it with me using that email address.
  7. We need some more information to diagnose this problem. Please post screenshots of Windows Explorer, opened to the following directories. Use Detail mode, and maximize the window so we can see filesize and timestamp. C:\Program Files\paint.net C:\Program Files\paint.net\Effects C:\Program Files\paint.net\FileTypes
  8. It would be 164,771,712 bytes if the file has one layer. PSD files can contain thousands of layers, so that file could require hundreds of GB of memory to load into Paint.NET. The problem is that Photoshop has partial layers and Paint.NET doesn't. Because layers are cheap in Photoshop, graphic designers can use layers like candy. They'll create a new layer for a 10x10 image element. When the file is loaded into Paint.NET, that 10x10 layer turns into a full 3892 x 3528 layer.
  9. Codeplex has finally taken action, and files can now be downloaded successfully on Chrome and Firefox. Due to the quick reporting from users, the PSD Plugin was one of the first projects on Codeplex to workaround the problem. I also have reason to believe that the operators of Codeplex took action based directly on my recommendations. Therefore, every project on Codeplex owes a debt of gratitude to the users of the PSD Plugin. Thank you!
  10. There is currently a URL block in effect against all downloads on Codeplex. The file checks out with a clean bill of health on VirusTotal.com. I have placed a link to the alternate download site on the PSD Plugin Codeplex page, and I have reported the problem to the people who run Codeplex. Since it is a URL block, that's about all I can do. Google requires the operator of the website (Microsoft) to get in touch with them to get the block lifted.
  11. It has come to my attention that Codeplex downloads are being blocked in many browsers, including Chrome. Every download on Codeplex.com is being blocked -- even Microsoft programs like the Windows USB/DVD Download Tool! If you are running Windows 10, the Edge browser can still download the PSD Plugin successfully. If you are not using Windows 10, you can download the latest version of the PSD Plugin here: http://www.psdplugin.com/
  12. PSD Plugin 2.4.1 and earlier do not work on Paint.NET 4.0.11 and later. Please upgrade to version 2.5.0 of the PSD Plugin: http://psdplugin.codeplex.com/downloads/get/1606282
  13. Windows Defender does not alert on PSDPlugin-2.5.0.zip. VirusTotal also gives it a clean bill of health at 55 different malware scanners: https://www.virustotal.com/en/file/309c44f2ceec555b0efddda81679a54a0bb89fccc38b784cc4c8609e87e4327e/analysis/ The problem may be caused by a browser add-on. I would suggest using a different web browser to download the plugin. Windows 10 Edge would be a good choice because it has very few add-ons available. However, any web browser will do except the one that you normally use. Make sure to copy-paste the direct link to the download: http://psdplugin.codeplex.com/downloads/get/1606282 If you continue to have this problem even with a different web browser, please do NOT delete the file. Submit the file to VirusTotal for analysis, and post the URL here.
  14. The timestamp check is actually not just to verify the file version, but also to check for side effects. As we saw above, third-party ZIP tools can have trouble with things that work correctly using the Windows built-in ZIP handler. The built-in ZIP handler in Windows always extracts files with the time set to the local time zone. No matter which time zone the user is in, the same times will be displayed in Windows Explorer. I just tried with my system set to Cyprus time (Eastern European time zone), and it shows the correct time.
  15. Those errors only appear if you have PSD Plugin 2.4.1 or earlier installed. If it is showing up, then PSD Plugin 2.5.0 is not installed properly People seem to be having trouble because upgrading requires that the old version be overwritten. You don't have to do this on fresh installs, so this problem doesn't come up. The best workaround is to first delete the old version: Restart the computer. Delete Photoshop.dll from C:\Program Files\paint.net\FileTypes Start Paint.NET and make sure that it cannot open or save PSD files. Close Paint.NET. Once this has been done, you can then do a fresh install of PSD Plugin 2.5.0: Download a fresh copy of PSD Plugin 2.5.0 from: http://psdplugin.codeplex.com/downloads/get/1606282 Right-click the ZIP file and select "Extract All ..." Make sure PhotoShop.dll has the timestamp: 9/11/2016 10:35 PM Copy PhotoShop.dll into C:\Program Files\paint.net\FileTypes
  • Create New...