Yeah, that's how I went about it, though english version. I can't imagine there is some difference in the language of the program that is causing a problem for me. I didn't do anything fancy for the spot light effects. They are just a plain white shape with a layer mask. It is no different from the colors on the mark itself. I could try rasterizing those parts, but that defeats the purpose of vectors then.
I would presume if the plugin is able to load all the other shapes there must be something special with that layer.
But I wouldn't rasterize it, as you said, it would compromize the original idea of vector marks.
For the error all it says is "an unspecified error has occurred". Nice and vague. haha.
Haha, yeah that's how you do good and clear error messages
But I anyway was able to reproduce the problem. I downloaded the latest version of the plugin here
PSD Plugin and I got the same error ("Ein unbekannter Fehler ist aufgetreten" -> hey.. even though it gives no information.. at least it's localized
)
Basically I fould out that previously I had the version of April 2012 (2.1.0) installed and not the version of Nov 2012 (2.2.0) which seems to have this error.
You can get the previous version on the page I linked too, in the list "Other downloads".
If I have the time I may debug Paint.Net with Visual Studio .Net to check what this error is.
I am putting up a poll to include a layered version of all the marks(and the make your own mark) that is not vectored or scalable but still completely customizable for custom marks.
Maybe not a bad idea, so at least everybody can create custom marks, regardless of which graphics program they use.
EDIT:I debugged the code to find that error - seems the autor of the plugin messed up something with the file decoder algorithms in his checkin of
29 July 2012 where he removed the original RleHelper class and added a RleReader with improved performance, but different reader-algorithm. I tried to replace the method with the original method and it worked, but since this stuff is recursive and works with unsafe pointers I didn't identify the bug itself with a quick look at the code, sorry. In the meanwhile, just don't use the last version of the plugin that should work