Red ochre

I too get the 404 result - perhaps @MadJik needs another host? Edit: Perhaps my Helix effect could be used if you can't get a Sinewave download. (set both Radii the same)

Excellent sentiment, striking image... perhaps conceal the watermark and soften the petal edges?😉 Surely someone could add some Novichok to Poo-tin's food! Not just for the women and children in Ukraine but all the young Russian conscripts too... and all of us if it goes nuclear.😟

Changing the way the gradient tool works is @Rick Brewster's decision but my Gradients Galore plugin has an ellipse option which uses the selection.

Welcome to the forum @MadManDiscoBear A good start with the flame shape . Perhaps you meant to share it in the shapes thread here?

Welcome to the forum Dil! You could use a plugin called Gridwarp - found here. - set it to use a 2 by 2 grid size and move the middle nub upwards.

And/or, when you have created your folder of often used images, right click on it and choose 'Pin to Quick access' so it is always at the top of the explorer folder list.

Ah - At least now I understand what you mean now but sadly cannot offer an explanation and cannot reproduce (I'm still on 4.3.7, sorry @Rick Brewster). @wacher what build are you using?

I'm still not quite sure what you mean either. Try changing the 'Antialiasing' quality. See Antialiasing here: https://www.getpaint.net/doc/latest/LineCurveTool.html#10

I published this 10 years ago! Selection2clear . I haven't updated it to 'clear' with transparent black (originally layers were transparent white) but it still works. Where does the time go?... Perhaps @Peter1 could use codelab to create his own bespoke version - it's not exactly complex!

Or sometimes 'craquelleur' 😉

Sorry to double post, just wanted to say thanks to @Pixey and @toe_head2001 for the Galleria addition.👍 I've updated page one now too.

Happy Valentine's lynxster4 ... Never my favourite day of the year but I'm a grumpy old bloke now and can safely ignore it.😉

@Kamikaze - Glad you are finding them useful and thanks for commenting!

@Ladybug, @Vagabondi, @lynxster4, @Pixey, @Kamikaze, @ReMake, @MJW, @otuncelli and @toe_head2001. Thank you for all the positive feedback and the reps.🙂 @Vagabondi - Yes that's Facet and some T.G.A - I also used some of MJW's height-map plug-ins and @pyrochild 's Smudge and Liquify are always useful.

More I'm afraid 😉 - clickable hopefully!

? The help documentation is the fourth item listed on the forum home page.

Wow - that was quick! Many thanks - will give it a try. ... Works perfectly! - very useful.

Pre and post-build events In VS 2019 I could set these using the project's properties to use @null54's code to copy the newly built .dll into the Effects folder (provided VS was run as Admin). I notice the VS 2019 ".csproj" shows this as <PropertyGroup> <PostBuildEvent>copy "$(TargetPath)" "C:\Program Files\paint.net\Effects" /y if "$(ConfigurationName)" == "Debug" copy "$(TargetDir)$(TargetName).pdb" "C:\Program Files\paint.net\Effects" /y</PostBuildEvent> </PropertyGroup> <PropertyGroup> <PreBuildEvent>del "C:\Program Files\paint.net\Effects\$(TargetName).pdb"</PreBuildEvent> </PropertyGroup> But the VS2022 ".csproj" already contains <Target Name="PostBuild" AfterTargets="PostBuildEvent"> <Exec Command="cmd /c explorer &quot;$(TargetDir)&quot;&#xD;&#xA;exit 0" /> </Target> Simply adding the VS19 code to the VS22 .cspoj fails to build. (paint.net was not running and VS22 was at Admin level) Does anyone know the correct way to add these commands in VS22 ? - Should it be incorporated into the <Target.../Target> block. If so how exactly?... I can be very dense sometimes!🙄 Many thanks in advance. (I can manually copy over the .dll from debug to Effects but found the previous VS19 way very convenient for quickly testing effects.)

I would still recommend you read this

That works! - many thanks.

Thank you! - I'll just ignore the warning. @Rick BrewsterI assume the .csproj file is created by codelab and I don't see any reference to WPF or WindowsBase ? <Project Sdk="Microsoft.NET.Sdk"> <PropertyGroup> <TargetFramework>net6.0-windows</TargetFramework> <GenerateAssemblyInfo>false</GenerateAssemblyInfo> <UseWindowsForms>true</UseWindowsForms> <AllowUnsafeBlocks>true</AllowUnsafeBlocks> <RootNamespace>myVS22TemplateEffect</RootNamespace> <AssemblyName>myVS22Template</AssemblyName> <Deterministic>false</Deterministic> </PropertyGroup> <ItemGroup> <EmbeddedResource Include="myVS22Template.png" /> <EmbeddedResource Include="myVS22Template.sample.png" /> </ItemGroup> <ItemGroup> <Reference Include="PaintDotNet.Base"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Base.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Core"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Core.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Data"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Data.dll</HintPath> </Reference> <Reference Include="PaintDotNet.Effects"> <HintPath>C:\Program Files\paint.net\PaintDotNet.Effects.dll</HintPath> </Reference> </ItemGroup> <Target Name="PostBuild" AfterTargets="PostBuildEvent"> <Exec Command="cmd /c explorer &quot;$(TargetDir)&quot;&#xD;&#xA;exit 0" /> </Target> </Project> Thank you both for your help!

Many thanks for your input Rick, unfortunately that didn't work for me.☹️ With VS22 closed I deleted the 'bin' and 'obj' folders, then restarted VS22 via the .sln file. Saved all, tried 'clean solution' then selected 'build'. It builds but I'm still getting the same error warning? Please excuse my ignorance: 1. What actually is "WindowsBase"? - does it convert C# to IL or IL to machine code or both or neither? 2. C:\Program Files\dotnet\packs\MicrosoftNETcore.App.Ref\6.0.1\ref\net6.0\WindowsBase.dll is there. Where is it getting "WindowsBase, Version=4.0.0.0" from? Is this part of the O.S. as I cannot see it as an installed package? I'm running windows 10 Home 21H2 (OS build 19044.1469) (originally windows 8.1) and cannot update to windows 11. 3. Is there something in the Codelab generated project that references version 4 that can be edited? 4. Would it be practical to somehow unistall WindowsBase, version=4.0.0.0, if I can find it? (screenshot below) 5. What are the consequences of ignoring the warning? - will effects always be built with an obsolete version of dotnet? Sorry for being a 'pain' but I really don't want to search for some dodgy version of Pdn 4.2.16 just to alter some of my effects using VS19!🙄 ... Or is the warning irrelevant for me as I'm unlikely to need the latest dotnet C# features? Would uninstalling any of these help?

When using codelab (version 6.4.7995.19949) to create a project then opening it with VS22 I keep seeing this warning when building the .dll.(see below) Is this a problem? (When the .dll is copied into Effects there are no loads errors and it seems to function ok.) Any advice appreciated. I have briefly read the link for Warning MSB3277 but it is WAY over my head! Should I be manually editing something in C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\amd64\Microsoft.Common.CurrentVersion.targets ? (The warning mentions line 2304) Many thanks for any feedback.

I think what @dipstick is doing is selecting an area around the text and copy/pasting this into a new layer. This is then an 'object' (opaque pixels on a transparent layer) that my object bevel effect can be applied to. So in other words it is the background that appears bevelled and the text remains flat. The same principle should work using Boltbait's or other bevel effects. Note lighting direction is important too. We tend generally to interpret convex objects as being light at the top left hand side and assume them to be convex or incised if the top L.H.S. is dark.

Blasphemy! 😁 Love the textures in Psychedelic Skies.