Rick Brewster

We've been using that utility for years without issue. It's a dangerous utility, but so is everything else on your computer. At any point you could open the Registry Editor and randomly delete everything. However, that utility is still included with every single Windows intallation.

Platform Update is only needed for Vista. You have everything you could have.

It also won't support DirectCompute unless you're on Windows 7, or Windows Vista SP2 with the Platform Update.

Here's a better idea: have the plugin author use SubMenuNames.Distort instead.

Let's see if this can get it any more attention. http://blog.getpaint.net/2010/07/17/gpu-blur-effects-pack-for-paint-net/

And did you try the Windows Installer Cleanup utility? Make sure you read the sticky post at the top of this forum that is in all caps.

Sorry, you must use English.

My bet is that you misread "maximum" as "minimum."

btw, they all say "Offset Red" ... there's no Offset Green or Offset Blue

Err, you mean like Utilities -> Manage Fonts? That's all it does: it launches the Fonts folder / control panel.

I'm un-pinning this for now because the pinned list of plugins needs to be trimmed a little. But, this post will at least bump it to the top of active topics.

Look, if Paint.NET is complaining about DdsFileType.dll then you've got the wrong version of Paint.NET installed. Maybe you had 3.36, then installed 3.5.5, and then it said you needed to reboot and the you didn't, and then the files wound up in a some-updated-some-not-updated state. This seems like the highest probability right now.

Oh snap, I was just about to post that

Then Punto has a bug, and they should fix it. Report this to them. Any time you use some niche utility that installs a hook, and then an app crashes, it's the utility's fault and not the app's.

No. GIMP has a splash screen because it's a giant bloated piggy. Paint.NET is taking awhile to load on your system because your computer is loaded down, not because Paint.NET is slow. Not having a splash screen also keeps me more accountable for maintaining good startup performance. It's never coming back and I find it comical that you're asking for its return! What will you ask for next, a splash screen for Firefox?

Paint.NET "supports" up to 65535 x 65535 pixels, so any effect should also work that high. Normally this isn't a problem because even at such a small value there isn't much probability of oveflowing an Int32. However, I should point out that if you are doing your own pointer arithmetic, e.g. get the Scan0 pointer then multiply Y and Stride, that you should not. Use GetRowAddress() instead, as it does need to do some bouncing with 64-bit ints in order to ensure an overflow doesn't happen. I found this only late in the v3.5 release cycle and fixed this. v3.36 won't actually work with images over a certain size because of silent overflows when calculating pointer offsets. I put supports in quotes because the memory requirements would be 12GB to start, plus 4GB per layer. Not very feasible with the current architecture.

Your best bet is to hitch a ride on the next NASA space probe passing through the asteroid belt between Mars and Jupiter. Bring a can of paint and a camera. How do you think they filmed the opening scrolling text for Star Wars? That stuff was done in outer space, they spared no cost. </just kidding>

All of the effects are giving me an E_INVALIDARG error in a message box when I try to apply them to this image (15204 x 4620 px): http://en.wikipedia....rn_Sky_edit.jpg

Well if I integrate it into Paint.NET proper, I would simply write my own D3D interop layer. Then installation would be no issue. I would also probably make it so that an effect can use HLSL without needing any of the D3D goop: just give me an HLSL fragment in place of OnRender().

I'm closing this thread because there's no need for any further discussion on it.

Very cool. Maybe I should just get this built-in to PDN 4 anyway

Or you can hold down the shift key and watch the status bar.

v3.36 probably should've been called v3.3.6. That is, major version 3, minor version 3, update 6. v3.5.5 has a file version of v3.55. The 3rd and 4th version fields are basically a time stamp, and not part of the product name. It's just a better way of publishing the version number. If you want to call the folder v3.50 then go ahead. Also, I should point out that while 3.5 and 3.50 are mathematically equally, they are not equal when it comes to versioning. That's because a version is 4 integers that just happen to be separated by periods so that it looks like a single number. I don't know why you'd want to archive old versions of Paint.NET though. It's 3.5MB, free, and there's no reason to ever install an older version (we never support older versions in any way). And, also, what BoltBait said.

Edit -> Paste into New Layer

Yeah you're still using 3.36 according to the crash log.