Blog
Here you can find all our activities. We will try to keep you informed about everything on our side. If you subscribed to the newsletter, you will receive notifications about the posts going to be newly published.
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: Attractors (narrated in Ukrainian, with an English voice-over track and English subtitles). The scheme has a new Attractors block (Functions → Move). Place spheres, cylinders and paths in the preview and give each one a pull toward or away from its core, a swirl around its axis and a flow along it, with a dead core in the middle and a falloff to the edge. Feed the block into a ForceMove as a force or as a wind, and you have a tornado, a vortex drain or a magnet. The field is edited right in the preview: one button per attractor type, the gizmo to move, rotate and scale, handles for the radii and the length, and the property panel for exact values. While you edit, every attractor shows its field — white streamlines with arrows for the swirl and the flow, green or red arrows for the pull toward or away from the core. A Path attractor is a tube through keys you place in the preview, with its own radius at every key, so it can widen and narrow along the way: pull draws particles to its centerline, swirl spins them around it, and the flow carries them along it from the first key to the last, turning smoothly round its bends. Hold Shift over the path to see where a new key would go, then click to insert it. You do not need the scheme for it: in the Emitter Guide, with Movement set to Forces, Add Force... and Add Wind... now offer Attractors. A new entry starts with one sphere at the center of the world, already pulling particles in, with a Strength that scales the whole field and Edit attractors... to open it in the preview. Attractors export to JavaScript v1.1, C# v1.2 and the GPU renderer. Every generator setting in the Emitter Guide Video tutorial: Generators (Periodic) (narrated in Ukrainian, with an English voice-over track and English subtitles). The Generation section now shows every number of the chosen generator — start delay, start phase, burst, the time and shots limits, the period settings of Manual Keys — as regular Emitter Guide values: a fixed number, an emitter property, or a graph over the emitter's or the effect's time. The “Other generator's properties…” button is gone. Switching an emitter between Periodic, Approx Rate and EvenRing now keeps your rate, start delay, limits, start phase and burst — graphs included — instead of resetting them. A link button on the Termination title bar ties the generator rate to the particle's Max Lifetime, so the emitter stays full as you change the life. New emitters start linked; if the setup stops allowing the link, it turns itself off and the editor tells you why. Approx Rate and Approx Distance look the same on the CPU as on the GPU Both generators used to produce an even stream on the CPU — a particle exactly every 1 / rate seconds, or every so many units of travel — while the GPU renderer produced them at random moments around the same average. Now the CPU preview and the JavaScript v1.1 and C# v1.2 exports produce them the GPU way: the average amount is the same, the moments (or the points along the way for Approx Distance) are random, so the stream looks organic. For an even stream use Periodic, EvenRing or By distance. Periodic no longer skips shots when the emitter is full. At the rate the link to the lifetime sets, the particles in flight fill the emitter exactly, so each shot needs the slot of a particle dying at the same moment; the shot used to come first and was dropped. Now the dying particle frees its slot first. A Periodic or Approx Rate effect with a fixed seed may look slightly different after re-export. A new terminator: Condition The Termination section can now hold a Condition terminator next to Max Lifetime and Path. It compares two values, A and B, every frame and kills the particle as soon as A reaches B. Both are full Emitter Guide values, so A can be, for example, the X of the particle's position and B a fixed number — an axis-aligned border that costs much less than a terminator path. See other graphs while you edit one When a particle's size, transparency and movement all change at the same moments, their keys used to be lined up by switching between graphs again and again. Now any graph can be pinned as a visualizer — with the pin button in the Graph Editor's title bar — and its outline stays visible, faded and read-only, while you edit any other graph of the effect. Hover an outline to see its name and emitter, click it to jump to editing that graph. Graphs made by the Emitter Guide now carry names after what they belong to, such as Size / Start or Transparency. The Graph Editor's buttons moved into its title bar, so the graph gets the whole height of the window, and a graph's Shift now comes back exactly as you left it when you turn it off and on again. Child emitters that continue their parent Video tutorial: Smooth Fade-Out with Attached Emitters (narrated in Ukrainian, with an English voice-over track and English subtitles). Values in the Emitter Guide can now read what another section computes for the particle: EG: Size, EG: Color, EG: Transparency, EG: Rotation and EG: Texture frame. Set the size or color of an emitter attached with On terminate to EG: Size or EG: Color, and an explosion, a splash or a trail starts at the size and color the particle had when it died, with no visible jump. An attached emitter can also take over its parent particle's orientation: Emitter property is now offered on rotation values too, so the parent can hand its exact rotation to the child through EG: Rotation. Both work in the JavaScript, C# and GPU33 exports. And it can carry the parent's motion on: the new Emitter Velocity value, next to Emitter position, reads the velocity of the emitter itself — the direction and speed it moves with, zero while it stands still. Use it in combined values: particles that inherit only part of the emitter's motion, a trail stretched along the way the emitter flies, a force or wind that grows with the emitter's speed. An emitter attached On terminate now starts with its parent particle's velocity in the CPU preview and in the JavaScript and C# exports, as it already did on the GPU. EvenRing, fixed across the board The shot ticks on the timeline no longer drift away from the real shots. The shots limit works on the GPU renderer with a start phase below 1 or a start delay. Short-lived EvenRing streams no longer have gaps from late slot reuse — in the preview and in the JavaScript v1.1, C# v1.2 and GPU exports. An EvenRing emitter attached On terminate fires again on the GPU renderer, at the parent's last position. A looped Manual Keys generator shoots in every period again. The editor warns when a generator's Burst is larger than the emitter's maximum number of particles, which used to make an EvenRing emitter show nothing on the GPU. Re-export GPU effects that use EvenRing to pick up the fixes. Smoother editing, safer exports Editing an effect with a large painted Area no longer freezes the editor for seconds with the GPU renderer: the area is now passed to the GPU as data instead of being rebuilt into its shaders on every change. While you edit an Area, its checkerboard fades back as soon as the mouse leaves the Preview window, so you can see the particles it produces. A zoomed-out timeline no longer slows the whole editor down, and Loop on the timeline restarts the GPU preview reliably, also with a later Preview Start. Exporting no longer silently drops emitters the export target cannot take — for example a Points or Grid block exported to JavaScript v1.0. The export window lists each left-out emitter with the reason, and an export with nothing left keeps the previously exported file instead of overwriting it with an empty effect. Export warnings and errors are now shown in the interface language. The release also carries a long list of fixes for mirrored emitters and for crashes after undo, reload and discard — including a crash after deleting Manual Keys shots on the timeline and one when opening a mirrored effect whose source cannot be loaded. Runtimes The PIXI 7 runtime makes far fewer WebGL calls on WebGL2: about 12 per effect per frame instead of about 59. If your code changes WebGL state directly through gl.* calls, call renderer.reset() afterwards, as PIXI requires for its own content. The Cocos Creator 3.x extension 1.1.9 no longer compiles the runtime into the game twice and renders correctly after game.restart(). Both it and the Cocos Creator 2.4.x extension 1.1.2 get a new NeutrinoEffectPreloader that loads an effect's textures up front, so it draws from its very first frame, and texture-grid frames now play in the same order as in the editor. Getting it 2.0.22 is on the downloads page, and the editor will offer it to you automatically. Effects saved with 2.0.22 do not open in older editor versions. 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.
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 (narrated in Ukrainian, with an English voice-over track and English subtitles). Until now a texture could only be used whole or cut into an even grid, so a sprite sheet from a packing tool — irregular cells, some sprites stored turned on their side — could not be used as it was. The Emitter Guide's Texture section now has a Frames mode: a list of frames, each a rectangle anywhere on the texture and turned at any angle, and the particle's frame index picks which one it shows. Edit Frames... opens the frame editor. Draw and drag frames over the texture, rotate and resize them with handles or type exact pixel values, or cut the whole sheet into equal cells with Slice Grid... — numbered in the same order as the Grid mode, so switching over keeps your animation. A frame's content can be turned or mirrored without moving the frame, which is the fix for a sprite the packer stored rotated. Changes show in the effect's preview as you work, Cancel puts everything back, and OK lands the whole session as a single undoable step. TexturePacker atlases can be linked directly: pick the atlas .json in the new Atlas field and the frames — rotated and trimmed sprites included — come straight from the file. The effect then follows the file: repack the atlas and the frames update within a second, each sprite keeping its index by name, so an animation does not scramble. A broken or half-written file is reported and changes nothing. If you would rather not follow the file, Import Once takes the frames as they are, and Convert to Manual stops following it while keeping them. Winds, and a new kind of turbulence: Curl Video tutorial: Curl Turbulence (narrated in Ukrainian, with an English voice-over track and English subtitles). The Movement → Forces section now holds two lists. Next to forces, which push particles directly, there are winds: a wind is a flow of the air itself, and particles are dragged along with it rather than pushed. Add one with Add Wind... — Directed, Curl or Turbulence. Effects made before this version keep their movement exactly as it was. Curl is a new turbulence, available both as a wind and as a force. Unlike the classic turbulence it has no spots that suck particles in or push them out, so particles swirl and flow around each other instead of bunching up — the look of smoke, water or a gust through leaves. All four of its settings — Strength, Wavelength, Animation speed and Space offset — can be random, follow a curve or be combined like any other value. Curl is also a value type: any 3D value, such as a color, an offset or a velocity, can sample the field, and in the scheme it is the Curl Noise block. Each Curl source has a Variant from 0 to 47 that swaps and flips the axes of the field, so two sources in one effect no longer have to move alike, and trying another look is one drag of a slider. Show visualizer draws the field in the 3D preview as streamlines that drift with the flow while the preview plays. Curl exports to JavaScript v1.1 and C# v1.2 and runs in the GPU preview. Each integration's documentation shows how to set up the field in your game. The classic turbulence is now marked as legacy: effects that use it keep working exactly as before, but for new effects use Curl. Points: particles exactly where you put them Video tutorial: Points Value (narrated in Ukrainian, with an English voice-over track and English subtitles). Pick Points as the type of a 3D value — most usefully Starting Position — or add the Points block to the scheme, and place the points in the Preview window with the path editor. Each particle is born at one of the points, never between them: lamps around a sign, sparks at the tips of a star, studs placed by eye. Feed it from Emitter Time to light the points one after another, or use a burst with one particle per point. Points is supported by JavaScript v1.1, C# v1.2 and GPU export, up to 1024 points per block. Smoother editing The path editor now shows how many keys a path has and how many are selected — handy when the same number has to go into a burst size. Switching Show visualizer on a block no longer restarts a playing preview, long paths no longer slow the preview down while you are not editing them, and a picture or video placed in the preview scene no longer hides block visualizers at the same depth. AI agents connected through the editor's MCP server now see the editor's notifications, so an agent no longer reports that something “failed silently” when the editor had in fact said why. If a second agent connects while the first is still working, the editor warns that they may overwrite each other's changes. Closing a project no longer occasionally closes the editor when a file in the project folder changes at that moment — for example when a sync client such as OneDrive touches it. Getting it 2.0.19 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.
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 editor can now render it frame by frame into numbered PNG images — for a video editor, a sprite sheet, or an engine that plays image sequences. Press Export Image Sequence on the preview toolbar and the Export Images panel opens next to your other panels. What you get is what the preview shows: the same renderer, bloom and background. A frame in one of the preview’s planar views — Front, Top, Left and so on — marks the area to render; drag its edges and handles with the mouse or type exact values. Choose the image size, the time range (or let it follow the preview’s), the folder and the file prefix. Transparent background gives images with an alpha channel, ready for compositing, and Include scene objects brings in the pictures and image sequences placed in the preview. The render runs in the background, so you can keep working while it goes. It never leaves a half-written sequence behind: the images land in the folder only once the whole sequence is done. The settings are saved with each effect. See Exporting image sequences for the details. Textures in the Emitters list Each emitter now shows a small thumbnail of its texture next to its name, which tells emitters apart at a glance far better than their names do. Hover it to see the texture enlarged; on the selected emitter, click it to go straight to the texture picker. Right-click an emitter and pick Reveal texture in file manager to open the texture’s folder with the file selected. A texture you edit outside the editor updates everywhere on its own. A signed and notarized macOS editor The macOS editor is now signed with the NeutrinoParticles Developer ID and notarized by Apple, so it opens like any other downloaded application — no more “cannot verify the developer” on first launch. Automatic updates on macOS now check that a new version is signed by us before they install it, and leave your current version in place if the check fails. Samples are read-only The bundled Samples project can still be opened, explored and edited, but nothing is written back, so an update can no longer overwrite your changes there. To keep working on a sample, drag it into your own project to get an editable copy. Stability This release also fixes several crashes, most of them from reports you sent us: when right-clicking in the emitter scheme, when copying emitters after an undo, when removing a value row from a mirrored emitter, and when opening certain effects made in older versions. On macOS, picking an image or a colour no longer closes the editor. Getting it 2.0.18 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.
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 reports you sent us, and it covers: Copying and pasting an emitter. On some effects — the Portal sample among them — pasting a copied emitter ended the session instantly, taking unsaved work with it. It affected effects where a section of the Emitter Guide had been rewired by hand in the scheme: Start Velocity, Movement (Manual), the generator and Max Life. Closing an effect with a floating Timeline. With the Timeline torn out into its own window, closing the effect — or the editor itself — could end the session outright. Reported from macOS, but the same flaw existed everywhere. Floating panels on macOS. Dragging a panel out into its own window occasionally produced a window covering the whole screen, with the panel drawn as a small rectangle in the middle. Graphics The GPU renderer now starts on AMD cards. Generated shaders carried a precision statement that strict desktop OpenGL drivers reject outright, so on those cards the GPU renderer would not initialise at all — neither in previews nor in exported effects. Existing effects need no changes, but re-export to pick up the fix in generated code. A driver rejecting a shader is no longer silent. Such a failure used to leave the preview simply empty, with nothing explaining why and no report reaching us. The editor now says what happened and, when the whole GPU renderer is affected, suggests switching to the CPU renderer so you can keep working. That reporting is how the AMD problem above came to be found: these failures depend on the specific graphics card and driver, so they cannot happen on our own test machines. For PIXI GPU-compressed textures — KTX/ASTC, BC7 and ETC — now render correctly. Such a texture cannot be premultiplied while loading, because the browser’s premultiply step does not apply to compressed uploads, and the renderer now honours that instead of assuming otherwise. A soft glow that came out as an opaque disc on Add materials looks right again, and ordinary images are unaffected. The fix ships in the updated PIXI v7 and v8 runtimes. Getting it 2.0.17 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.
Read more 10 Sep 2026NeutrinoParticles Editor 2.0.16: AI Agents Can Now Drive the Editor
NeutrinoParticles Editor 2.0.16 is out, for Windows, Linux and macOS. AI agents can now drive the editor The editor ships with an embedded MCP server, so AI agents — Claude Code, Claude Desktop and other MCP clients — can work in it alongside you. An agent sees the interface as a tree of named elements and drives it the way a person would: clicks buttons, switches modes, picks from menus, sets values in any panel or dialog. It can open projects, create and edit effects, undo and redo, configure exporters and export effects. Every action it takes is a single undoable step, so anything you disagree with is one Ctrl+Z away. Nothing happens behind your back. Signing in stays a human action. If an agent closes the editor with unsaved work, the usual prompt appears and the agent has to show it to you rather than answer it for you. Agents also hit walls that we never see — something unreachable, confusing, or simply broken. When that happens, an agent can send a feedback report with screenshots straight to us. Only with your explicit consent, from a signed-in account, and carrying nothing beyond the editor version, your OS and the active renderer. It is off by default. Turn it on in Editor Settings, or start the editor with --mcpServer. The server listens on 127.0.0.1 only — it is not reachable from outside your machine. Colour codes for emitters Once an effect has a lot of emitters, telling which timeline flag or which window belongs to which one gets hard. Right-click an emitter in the Emitters panel and pick Color Code: Auto Color picks a bright colour for you, keeping it as far as it can from the ones already in use, Custom Color opens a full colour picker. The colour then shows as a small flag next to the emitter's name and on its generator flags in the Timeline, so everything belonging to that emitter reads as one at a glance. Colours are saved with the effect. A new value type: Particle Speed Any 1D value can now read how fast a particle is moving, straight from the value type menu — no need to build it out of Particle Velocity and a length expression. It works on its own and as the X axis of a graph. Effects already using the Over particle speed graph keep working exactly as before, while getting simpler inside: every value reading the speed now shares one calculation instead of each carrying its own. Fewer random crashes The preview runs your effects on V8, the JavaScript engine behind Chrome, and it has been upgraded from a two-year-old version to the current one. That closes a rare crash that could take the editor down while you edited a value or an expression, and previews now behave even closer to what your effect will do in a real browser or game runtime. On Windows, international text APIs in preview scripts work as they do in a browser instead of closing the editor. Beyond the engine, this release fixes crashes when adding a graph key by clicking on a curve, when pasting certain emitters, when several projects are open at once, and when files change on disk while a dialog or menu is open. The editor is also far less likely to shut itself down when a screen-capture tool or shell extension briefly holds its window busy — that pause is no longer mistaken for a freeze. Crash reports from macOS and Linux now say what actually went wrong. They used to arrive missing the one log line that names the problem, which made them hard to act on. Nothing changes in how the editor behaves — it just means crashes get fixed faster. Getting it 2.0.16 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.
Read more 03 Sep 2026NeutrinoParticles Editor 2.0.15 Released
NeutrinoParticles Editor 2.0.15 is out, for Windows, Linux and macOS. Stability This release is a stability update. Work across the editor is now steadier, with fixes in the preview and timeline, the project and emitter trees, the Area editor, generators, and the emitter scheme. Heavy effects behave better too: if a preview simulation ever stops responding, the editor no longer waits on it — that effect’s preview stops on its own, and the editor stays fully alive so you can keep working and save. For Cocos Creator Particles now render correctly on Mali GPUs — Samsung Galaxy S10 and S20 and other Exynos-based devices — where textures and colours could come out wrong. The fix ships in the updated Cocos Creator extension and in the PIXI, Phaser and web runtimes. Getting it 2.0.15 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.
Read more 31 Aug 2026NeutrinoParticles Editor 2.0.14 Released
NeutrinoParticles Editor 2.0.14 is out, for Windows, Linux and macOS. Graphs over anything Until now a graph could only run over time, or over one custom value, and you had to pick which kind up front — six separate types in the menu. Now there is one Over value. You choose what its X axis is: particle life, particle speed, a value of your own, or something you build from several. The old menu entries are still there as shortcuts, so the quick way to a graph over particle life is exactly what it was. Your existing effects open unchanged and export exactly as before. For example, the color of particles as a Graph over Nuber of Particles: Two new things a value can read Any value can now read how many shots a generator has fired, or how many particles are currently alive. Use the shot count to make each burst different from the last — a different colour, size or direction every time. Multi-Value in one click The value menu now offers a × b and a + b ready-made. One click builds the whole thing instead of you switching the value, adding a row, typing a number and typing the expression. A graphics problem no longer closes the editor If the preview hits a graphics problem, only the preview stops now — you get a notification and a red border, and the editor keeps running so you can save your work. Opening an effect starts the preview again. Smaller things Collision shapes each have their own button in the preview toolbar, so adding one takes a single click. Path points snap to the grid while you drag them. Origin has its own icon in the Emitter Guide instead of sharing one with Starting Position. And in the Chinese interface the preview now reads in Chinese too, where it used to show question marks. This release also fixes a rare crash when closing or deleting an effect, and an error that appeared when shutting the editor down. Getting it 2.0.14 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.
Read more 22 Aug 2026NeutrinoParticles Editor 2.0.11 Released
NeutrinoParticles Editor 2.0.11 is out, together with updates across the runtimes and the website. 2.0 was a big release; this one is about living with it. Three things stand out: updating the editor no longer deletes your files, the interface now speaks Chinese, and the Emitter Guide can drive any 3D value with noise, without touching the scheme. Updating no longer takes your effects with it This is the important one. Until now an automatic update cleared the whole editor folder before unpacking the new version — so if you kept effects in there, next to the bundled samples, they went with it. The editor now knows which files are its own and removes only those. Anything of yours in that folder is left alone. Updating from an older version still has to clear the folder, because those versions never left such a record — the editor warns you first and lets you cancel and move your files out. Either way, the bundled samples are always replaced, so if you have edited one, save it under a different name. The editor speaks your language A Language setting in Editor Settings switches the interface between English and Simplified Chinese, and by default the editor follows your system language. The whole interface is translated — menus, dialogs, the block palette and scheme, the Emitter Guide, block properties, the graph editor. Block tooltips deliberately keep the original English block name alongside the translation, so Chinese users can still follow English documentation and video tutorials. A Chinese font ships with the editor, so the interface reads correctly on any system. Your effects are untouched: names, presets and exported code stay exactly as they were, and a project saved in one language opens identically in the other. A new Noise value in the Emitter Guide In the Emitter Guide, any 3D value — a colour, a size, a position offset — can now be driven by a 3D noise field. You pick Noise from that value's type menu, the same menu you already use to switch a value between a constant, a random range or a graph. No scheme editing needed. By default the field is sampled at the particle position, so it reads as a coherent field in space rather than as per-particle randomness: particles near each other get similar values, and drifting through the field makes them flow. Smoothness, animation speed and output scale are all exposed, and the scale can itself be randomized or animated. Elsewhere in the editor The path editor gained a Reverse Direction button, which flips the direction a path runs in while keeping its exact shape, Bezier handles included. The Emitter Scheme canvas is now darker than the panels around it, so the scheme no longer blends into its neighbours. The interface font now looks the same on Windows, macOS and Linux, which it previously did not. And the editor no longer gives up on itself during an ordinary slow moment — such as a file dialog opening a folder on a network drive — instead of costing you the session. Runtimes and exporters PIXI v8: effects are drawn in the right place again. Anything added to the stage before an effect was being painted on top of it instead of underneath, so the effect looked stuck behind the scene. GPU renderer: the preview now matches the exported effect where it used to differ — very bright particles are capped the same way in both, and values driven by system time animate correctly at particle construction instead of staying frozen. The Cocos Creator and MonoGame packages, and the JavaScript, C# and GPU exporters, are all refreshed alongside this release. On the website Signing in and signing up were mangling passwords containing certain characters, which is why the site would sometimes accept a password that the editor then rejected. That is fixed. Registration links, which are single-use, now explain themselves instead of showing a bare error when clicked twice, and a fix to the site's scripts now actually reaches returning visitors rather than sitting behind a stale browser cache. The documentation has new pages for the Noise value type, the language setting and the path Reverse Direction button. Stability This release also clears out a run of crashes: opening an effect that contains a mirrored emitter, switching between GPU effects, changing the dimension of a multi-row value, and editing in the Emitter Guide while the panel refreshed underneath you. Along with those, a half-typed value name is no longer silently saved when the panel refreshes. The release notes describe each one in detail. Getting it 2.0.11 is available for Windows, Linux and macOS on the downloads page. The JavaScript and C# runtimes update through npm and NuGet as usual. If you hit something odd, tell us — crash reports carry the effect you were working on, which makes a report far more useful than it used to be.
Read more