Overview

It is possible to extend the list of available feature sets by creating custom ones.

IMPORTANT: When creating custom feature sets for a production, make sure that it will be supported by the final game engine.

Note: If creating a custom feature set for UnrealEngine, Unity, Lumberyard, O3DE, AfterEffects, you will need to make sure expected features are supported by our plugins, contact us at support@popcornfx.com if in doubt.

Creating custom feature sets for PopcornFX v2 remains a two-step process:

• Create the feature set editor shader(s) that will mirror the final game engine shader
• Create the game engine shader that has the same inputs

We want to streamline that process in future PopcornFX versions, and maybe provide a shader export API for engines that would support it.

This page will describe how to create a custom feature set compatible with a billboard renderer. This remains experimental so it is recommended to follow those steps exactly, you can reach out to us on our discord server if something doesn’t work as expected.

Developer mode

Before doing anything, it’s currently required to enable “Developer Mode” in your editor settings. This will allow edition of materials.

Recommended setup

To make sure everything is organized correctly for your production:

• Never directly modify anything located in the Library/PopcornFXCore folder. Everything contained in that folder is subject to change when updating PopcornFX to a newer version
• Create a custom folder for your project in Library/ (here, we’ll be creating one in Library/ExampleContent/)

To make sure Materials and Rendering interfaces are visible in the content browser, you can select the “Filters” dropdown and enable required assets:

Creating the material

In this example, we’ll create a custom material from scratch for Opaque Billboard particles. This material will support the Diffuse from Editor.pkri, and can easily be extended to add support for additional custom features.

To create a material, right click in the content browser:

You’ll be prompted to name your material, you can uncheck “Open asset” for now. We’ll name the material Example_Billboard.

Creating the fragment shader

Next, we’ll create a fragment shader file:

We’ll also name the fragment shader Example_Billboard.

Note: PopcornFX Editor automatically generates a “passthrough” vertex shader for billboard, ribbon and mesh particles. If no custom vertex shader is assigned to the material, rendering will use that passthrough shader. Thanks to this, we only need to create a fragment shader most of the time for such renderers that don’t need custom vertex shader logic. You can take a look at the VAT custom materials to see an example of custom vertex shaders.

Material editor

Now that the material and its fragment shader are created, you can open the .pkma file by double clicking it:

We have an empty material that has no shader assigned for now, this material is missing the reference “Geometry” rendering feature:

1. Each one of those corresponds to one renderer node type in PopcornFX. This is the rendering feature that will determine which renderer is compatible with your material. Each material can only be compatible with one renderer.
2. Expand the shader editor properties panel: this material has no valid Geometry feature and cannot be used as-is
3. Empty feature list

We have to add the GeometryBillboard feature to the list of feature this material has:

1. The mandatory GeometryBillboard has now been added
2. The shader editor’s panel now displays additional infos, and lets you pick a fragment shader path
3. The renderer preview is now functional: this is what billboard renderer properties will look like when this material is assigned to them

Additional features can be added:

1. Marking all features Mandatory makes them enabled by default (ie. not optional)
2. We can now see our material being rendered purple (it will need a fragment shader)

The material now needs a fragment shader to be specified:

1. Make sure to pick the newly-created fragment shader file

After picking up the newly created .frag, you’ll see the material still does not render properly, we have a compilation error:

This is because Opaque draw calls need to output additional informations, and the generated .frag is invalid:

1. Select ‘Preprocessed Shader’ to visualize the fully generated shader file
2. Shader expects all output values to be initialized: Opaque render pass requires additional output values

This is an issue that will be resolved in future PopcornFX versions: generated .frag files do not currently automatically work with non-transparent draw calls.

We can easily fix this by writing to all output values:

At this point our material actually renders on screen as Opaque so it can be used by billboard particle renderers in effects. We’ll augment the fragment shader a bit so it supports sampling the Diffuse texture and the per-particle color:

PopcornFX Editor has its own (undocumented) GLSL augmented shading language, with a series of macros (ie. SAMPLE) allowing you to retrieve per particle values, or draw call constants.

You can leverage #if defined(HAS_*) checks in your shader to detect if a rendering feature was enabled or not by the VFX artist on the renderer node:

1. Diffuse is not mandatory: this becomes a toggle on the renderer node.
2. Entire parts of the shader becomes ignored / compiled out if Diffuse is not enabled on the renderer
3. The default color is chosen, based on shader code logic

As Diffuse is now optional, two shader permutations are generated, you can inspect each:

Best pratices

As mentioned, it’s best to create a specific folder for your production(s) that will contain all public templates, materials, common content.

Inlined templates

Currently, there is no way to specify project wide what material is picked up by default when creating a particle renderer. Right now it defaults to Default_RendererType.pkma

This is something that can be addressed easily by creating your own renderer presets, using the “Inlined templates” system.

We’ll be using the same example folder structure, creating a new folder for templates, and an effect file containing them:

Opening that effect file, you can create a template, with the following settings:

1. Make sure the template is public
2. Auto Inline needs to be checked, this means when this template is placed in a nodegraph, its content will be pasted in, instead of a template instance.
3. Class type set to “Renderer” will color the template in yellow
4. You can setup some category and keywords for the contextual menu and template shelf

Opening the template, you can now create a single billboard renderer, with the Feature set applied:

Once this is done, you can save and quit this templates file, opening an example effect, opening the contextual menu now properly lists our template as it’s public:

Selecting our template, its content is inlined instead of having a regular template instance placed in the graph:

This setup is ideal so artists work with your materials and renderers.