NeutrinoParticles Editor 2.0.23: Fill Rate Meter, Emitter Solo and GPU Effects in Cocos Creator
NeutrinoParticles Editor 2.0.23 is out, for Windows, Linux and macOS.
Fill rate meter: see what your effect costs the GPU
Video tutorial: Fill Rate Meter (narrated in Ukrainian, with an English voice-over track and English subtitles).
A few dozen huge, overlapping particles can slow a game down more than thousands of small ones, because the graphics card has to paint every pixel of every particle — transparent ones included. The new Fill Rate button on the preview toolbar shows that cost: the average overdraw (how many times the particles paint over each pixel, with the maximum of the last seconds), the share of the area they cover, the most layers stacked on one pixel, and the number of pixels painted per frame.
Its menu adds a Heatmap that colours the preview by the number of particle layers on each pixel, with a legend and the exact count under the mouse pointer. When the export frame is shown, the meter measures inside it and estimates the pixels per frame at the frame's output size, so the number hardly depends on zoom or on your monitor. It works with both the CPU and the GPU preview renderers.
A new Fill Rate tab in Project Settings sets the project's budget: an amber and a red limit for overdraw, covered area and pixels per frame. When the effect goes above a limit, its row in the meter turns amber or red, so you notice an expensive effect while you make it, not after it ships.
Solo emitters, and switch many at once
Ctrl+click an emitter's eye (Cmd+click on macOS) to solo it: the preview then shows only the soloed emitters, and the eyes of the others turn dim. Several emitters can be soloed together; Alt+click solos one emitter alone, and an orange Clear solo eye in the Emitters title bar brings everything back. Like the eye, solo only affects the preview — it is saved with the effect but never changes what is exported.
To change many rows in one go, press on a checkbox or an eye and drag across the other rows, or select several emitters and click the switch on one of them. The eye can now be undone like any other edit, and every such change, however many rows it touches, is a single undo step.
Image sequence export: an easier frame, and several times faster
The render frame is now shown in the preview from the start, drawn with a dark outline and viewfinder corners so it stays visible over bright particles. Drag its edges and corners freely: the output size follows at the same number of pixels per unit. Hold Shift to keep the proportions and the output size, and Alt (Option on macOS) to resize from the centre. Fit to view centres the frame in the view, and the new 1:1 button sets the output size to the frame's size on screen, so the images match the preview pixel for pixel. The panel shows the frame's centre, its full width and height and its four edges in world units.
The export itself is several times faster: images are saved in parallel on all processor cores but one, while the next frames render. The images are exactly the same as before.
Self Rotation can combine several rotations
The rotation of Self Rotation → Controlled is now a multi-value, like a color or a size: add rotation (R) rows and number rows and combine them with a formula. a * b turns by one rotation after another, slerp(a, b, c) turns smoothly from a to b as c goes from 0 to 1 — for example a graph over the particle's life — and inverse(a) undoes a rotation. Rows can be nested, and so can the angle and the axis inside every rotation value. A plain single rotation still costs nothing at run time.
New generator: EvenRing Distance
Video tutorial: Generators (EvenRing Distance) (narrated in Ukrainian, with an English voice-over track and English subtitles).
EvenRing Distance lays the EvenRing ring of emission slots out on the distance the emitter travels instead of time: the emitter's whole capacity is emitted evenly over the Ring length, with a start distance, a distance limit and a shots limit. It is the first exact (not random) distance generator on the GPU, and JavaScript 1.1, C# 1.2 and Unity emit the same shots in the same slots. It is in the scheme palette and in the Emitter Guide's Generation section.
Related: an emitter attached On terminate now keeps its dying parent only while it has particles — in the preview and in the JavaScript 1.1 and C# 1.2 exports, as it already did on the GPU. Before, without a shots or time limit, the parent was kept forever.
Smoother preview, and a path editor that keeps your selection
The preview now times its frames from the display's refresh instead of a free-running timer: an effect playing at 30 fps on a 60 Hz screen holds every frame for exactly two refreshes, without the old stutter, also with several monitors. The grid is several times cheaper to draw, the timeline graph no longer redraws itself every frame, and the editor no longer keeps a CPU core busy while idle. On an Intel UHD 620 laptop at 4K the preview went from about 40 to nearly 60 frames per second.
In the path editor of the Path, Points and TerminatorPath blocks, moving, rotating or scaling keys with the gizmo no longer deselects them, so you can watch the effect from the new position and nudge the keys again right away. The gizmo also remembers whether you last used Move, Rotate or Scale.
Before you update
- macOS 14.4 (Sonoma) or later is now required. The editor moved to a newer version of Qt, which no longer runs on older macOS. On macOS 13 or earlier the automatic update will not start; download and install 2.0.22 from the website by hand instead. Windows and Linux requirements do not change.
- Videos in the preview scene need Media Foundation on Windows. It is part of every Windows edition except the “N” editions; on those, install the free Media Feature Pack from Settings → System → Optional features.
- In GPU effects, Older first / Younger first sorting now looks the same as in CPU effects and in the JavaScript and C# exports: the younger particles lie on top. Before, the GPU drew them the other way round.
Fixes
An EvenRing emitter in the GPU preview no longer fires into every slot when its rate is 0 and comes from a graph, and a graph with a broken first or last key no longer drifts out of sync over minutes of looping. Gen burst position and Number of shots can now be picked directly in a value nested inside another one, a graph's Shift no longer keeps working after it disappeared from the Emitter Guide, and the letters of combined values and the rows of mode buttons in the Emitter Guide are no longer clipped or squeezed. An attached emitter's name follows a rename everywhere, a reflected emitter follows its source path's new shape, and the Attractors visualizer is no longer covered by a picture or video in the scene behind it.
The release also closes a set of crashes and data scares: false “This effect was deleted from disk” prompts in projects whose effects folder is reached through .. or a symbolic link, a crash on every start after an unreadable autosave, and crashes when the scheme changed under a held mouse button, when an effect rename met a refresh prompt, or when the export window was closed while an export was still running.
GPU effects in Cocos Creator 3.8
There is a new Cocos Creator extension, NeutrinoParticles-GPU33, for effects exported in the GPU format: simulation and rendering both happen on the GPU, so hundreds of thousands of particles leave the CPU free for gameplay. In 3D an effect takes its place in the transparent queue with depth test; under a Canvas it is drawn in sibling order, clipped by masks and ordered by Sorting2D. A component is generated for every exported effect, effects play in the Scene view, and their textures go into asset bundles automatically. It needs Cocos Creator 3.8 and WebGL2 on web platforms. The extension is under review on the Cocos Store; the source and the guide are on GitLab.
Runtimes
The Cocos Creator 3.x extension 1.1.10 draws effects under a Canvas with the UI renderer, in the order of the UI hierarchy like sprites and labels: a Mask clips them and the opacity of their parents fades them. Effect textures now load in web and native builds from any folder — the extension marks the right folders as Asset Bundles itself; open the project in Creator once after updating, then build.
Noise is much cheaper everywhere. Generating the noise volumes is about ten times faster in the JavaScript 1.1 runtime and several times faster in C# 1.2, with bit-identical results. In Cocos Creator (3.x and 2.4.x) the curl noise is generated on the GPU, and an effect generates only the noise it uses, in small slices while the game keeps running — no more freeze at start-up. PIXI 7, PIXI 8 and Phaser get generateNoiseAsync() and isNoiseReady, and Phaser can bake the curl noise on the GPU with the new @neutrinoparticles/curl-noise-gpu-v1.1 add-on.
Getting it
2.0.23 is on the downloads page, and the editor will offer it to you automatically. The full release notes list everything.
If something looks wrong, tell us — crash reports include the effect you were working on, which makes them far more useful.
More articles
NeutrinoParticles Editor 2.0.22: Attractors, Generator Settings in the Emitter Guide and Emitter Velocity
NeutrinoParticles Editor 2.0.22 is out, for Windows, Linux and macOS. Attractors: zones that pull, push and swirl particles Video tutorial: ...
Read more 07 Oct 2026NeutrinoParticles Editor 2.0.19: Texture Atlases, Winds and Curl Turbulence
NeutrinoParticles Editor 2.0.19 is out, for Windows, Linux and macOS. Texture atlases, rotated sprites included Video tutorial: Texture Frames (na...
Read more 30 Sep 2026NeutrinoParticles Editor 2.0.18: Export Effects as Image Sequences
NeutrinoParticles Editor 2.0.18 is out, for Windows, Linux and macOS. Export effects as image sequences Besides exporting an effect as code, the...
Read more 16 Sep 2026NeutrinoParticles Editor 2.0.17 Released
NeutrinoParticles Editor 2.0.17 is out, for Windows, Linux and macOS. Stability This release is a stability update. Most of it comes from report...
Read more Participant