PopcornFX v2.14

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
  1. Home
  2. Docs
  3. PopcornFX v2.14
  4. Rendering
  5. Materials
  6. Custom rendering interface

Custom rendering interface


It is possible to extend the list of available rendering features by creating a custom rendering interface file.


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


Note: If features are missing for our UE4, Unity, Lumberyard plugins, you can contact us at support@popcornfx.com so we can discuss adding those to our roadmap.


This page will describe how to create a rendering interface, containing a single rendering feature. This rendering feature will be added to the existing example material created. This remains experimental so it is recommended to follow those steps exactly, you can contact us at support@popcornfx.com if something doesn’t work as expected.

Developer mode

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/)

We’ll follow the existing directory structured described here, and create an Interface folder:
Folder structure

Creating the rendering interface

No creation dialog is available to create rendering interfaces. It’s best to Clone an existing one (here, Editor.pkri):
Clone rendering interface

After properly naming your interface, you can move it to the desired folder:

Folders layout

You can now open the newly created .pkri file, it will display on the left the list of all rendering features present in Editor.pkri. Delete them all.

Delete all

For this example, we’ll be creating one rendering feature named “ExampleFeature”. This feature will have one property named “UVMultiplier” being a Link (per particle value), that will act as it name implies as a multiplier for the uvs used to sample the diffuse texture:

Custom rendering feature

You can now save the .pkri file, and open the material where this feature should be added (we’ll be opening the one created here). Once the material editor is opened you can add your custom feature:

Add rendering feature to material

A feature set can be composed of features from Editor.pkri and other interfaces.

This ensures you are only extending the list of features instead of forking Editor.pkri into your own version.

Now that you material has your rendering feature, its fragment shader code modified, applying it to a billboard renderer provides the following result:

Final result

Was this article helpful to you? Yes No

How can we help?