![]() PaintDotNet.Base PaintDotNet.Base, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null PaintDotNet.Core PaintDotNet.Core, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null PaintDotNet PaintDotNet, Version=4.216.7781.39227, Culture=neutral, PublicKeyToken=null Mscorlib mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Hardware accelerated rendering (GPU) TrueĬPU Intel(R) Core(TM) i7-2600 CPU 3.40GHzįeatures SSE, SSE2, SSE3, SSSE3, SSE4_1, SSE4_2, AVXįlags AcgCompatible, SupportMonitoredFences, KeyedMutexConformanceĭXGI Formats A8_UNorm, B8G8R8A8_UNorm, R16G16B16A16_UNorm, R16G16B16A16_Float, R32G32B32A32_Floatīuffer Precision UNorm8bpc, UNorm8bpcSrgb, UNorm16bpc, Float16bpc, Float32bpcįlags Software, AcgCompatible, SupportMonitoredFences, KeyedMutexConformance I have successfully setup the PDF open and save before on machines in the past, but the last four or so times I tried to setup on new machines always get this message:Īt (Stream input) in D:\src\pdn\src\Data\FileType.cs:line 497Īpplication 4.2.16 (Final 4.216.7781.39227) I am getting the following error message when I try to open a PDF in and can not figure out how to solve the problem. ![]() (ghostscript 9.22, PaintNet 4.016) This would point to Win 10 as a culprit. I have the exact same setup at my office PC, which runs Win7 and the plugin works fine there. While some forum members claim that you have to put it in FileTypes. txt file attached to plugin says to, quote:Ĭopy the two files OptionBasedLibrary vX.X.dll/.dlc to the Paint.NET\ folder (NOT to Paint.NET\FileTypes\ !!!) It used to work fine, but stopped after I reinstalled Windows to newest version.ġ) Ghostscript 9.10 9.26 9.22 9.53.3 (always removed the entire folder after uninstall finished)Ģ) Running different (4.0.16 4.2.15)ģ) Moving plugin files around. System.FormatException: Input string was not in a correct format.Īt (Stream input)Īt (Stream input) in D:\src\pdn\src\Data\FileType.cs:line 512Īt (Func`2 f, T1 arg1) in D:\src\pdn\src\Base\Functional\Func.cs:line 158
0 Comments
Leave a Reply. |