null54

Layer folders are listed in the Popular Feature Requests thread.

It appears that trick is done using the ICC color profile. Paint.NET currently ignores color profiles when loading an image, but most web browsers will use them. Adobe Photoshop 2021 detects the profile as invalid when loading the image and ignores it.

I received the warning after changing those projects to use the PDN 4.3 libraries.

I encountered a MSBuild warning when updating a few of my FileType plugins for Paint.NET 4.3. Warning MSB3277 Found conflicts between different versions of "WindowsBase" that could not be resolved. There was a conflict between "WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" and "WindowsBase, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35". "WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" was chosen because it was primary and "WindowsBase, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" was not. References which depend on "WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" [C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\5.0.0\ref\net5.0\WindowsBase.dll]. C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\5.0.0\ref\net5.0\WindowsBase.dll Project file item includes which caused reference "C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\5.0.0\ref\net5.0\WindowsBase.dll". C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Ref\5.0.0\ref\net5.0\WindowsBase.dll References which depend on "WindowsBase, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" []. D:\Program Files\paint.net\PaintDotNet.Base.dll Project file item includes which caused reference "D:\Program Files\paint.net\PaintDotNet.Base.dll". PaintDotNet.Base PaintDotNet.Core PaintDotNet.Data D:\Program Files\paint.net\PaintDotNet.Core.dll Project file item includes which caused reference "D:\Program Files\paint.net\PaintDotNet.Core.dll". PaintDotNet.Core PaintDotNet.Data D:\Program Files\paint.net\PaintDotNet.SystemLayer.dll Project file item includes which caused reference "D:\Program Files\paint.net\PaintDotNet.SystemLayer.dll". PaintDotNet.Core PaintDotNet.Data D:\Program Files\paint.net\PaintDotNet.Framework.dll Project file item includes which caused reference "D:\Program Files\paint.net\PaintDotNet.Framework.dll". PaintDotNet.Data D:\Program Files\paint.net\PaintDotNet.SystemLayer.Native.x64.dll Project file item includes which caused reference "D:\Program Files\paint.net\PaintDotNet.SystemLayer.Native.x64.dll". PaintDotNet.Core PaintDotNet.Data DdsFileTypePlus C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Microsoft.Common.CurrentVersion.targets 2203 Has anyone else had this issue?

That may be it, looking up the call stack I see that the destination surface height is 600 and the source surface height is 302. After looking at the 4.2.16 CopySurface implementation in dotPeek, it appears that you missed a srcHeight == dstHeight statement at line 183 in the RenderImpl class.

PaintDotNet.Base.dll!PaintDotNet.BufferUtil.Copy(void* dst, void* src, ulong byteCount) Line 67 C# PaintDotNet.Core.dll!PaintDotNet.Rendering.SurfaceUtil.RenderImpl<PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra>, PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra>, PaintDotNet.ColorBgra>(ref PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra> src, ref PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra> dst, PaintDotNet.Rendering.Point2Int32 renderOffset) Line 187 C# PaintDotNet.Core.dll!PaintDotNet.Rendering.SurfaceUtil.RenderImpl<PaintDotNet.ColorBgra>(PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra> src, PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra> dst, PaintDotNet.Rendering.Point2Int32 renderOffset) Line 153 C# PaintDotNet.Core.dll!PaintDotNet.Surface.CopySurface(PaintDotNet.Rendering.ISurface<PaintDotNet.ColorBgra> source) Line 985 C# PaintDotNet.Core.dll!PaintDotNet.Surface.CopySurface(PaintDotNet.Surface source) Line 973 C# [External Code] PaintDotNet.Effects.dll!PaintDotNet.Effects.Effect.SetRenderInfo(PaintDotNet.Effects.EffectConfigToken parameters, PaintDotNet.RenderArgs dstArgs, PaintDotNet.RenderArgs srcArgs) Line 195 C#

It appears to be somewhat random, I just kept moving the slider until it breaks into the debugger. Buffer.MemoryCopy is throwing an ExecutionEngineException.

That is the cause, see https://docs.microsoft.com/en-us/dotnet/api/system.diagnostics.processstartinfo.useshellexecute?view=net-5.0.

That looks like normal Visual Studio behavior to me. Normally you would have the plugin Visual Studio project located outside of the paint.net folders, and use a post build event to copy the DLL to the appropriate folder.

The surface data is always locked. The following code uses Buffer.MemoryCopy to copy an entire row at once.

According to MSDN the drop shadow is provided by the OS, see https://docs.microsoft.com/en-us/windows/win32/shell/thumbnail-providers#thumbnail-adornments.

Many games use the alpha channel to control the specularity (glossyness) of an image. Unfortunately, paint.net does not have a built-in way to edit the image channels as a grayscale image. You should be able to use the Switch Alpha to Gray and Paste Alpha plugins in @BoltBait's plugin pack as a workaround for that missing feature. Regarding the DDS output format, this guide on Steam indicates that the diffuse map should be saved as BC3 / DXT5. You can also use the DirectXTex Texdiag utility to get the format and mipmap information from the original textures.

Paint.NET requires file type plugins to have a different extension than the built-in formats.

Release version 1.3.7. Changes: Updated to libwebp version 1.2.1. Enabled hardware acceleration (ARM NEON) for the ARM64 build. As of version 1.3.7, Paint.NET 3.5.11 and 4.0.X are no longer supported.

I am enjoying Leverage: Redemption, it is an Amazon/IMDb TV reboot of the American TV series Leverage.