Editing any value (color, parameter, texture) in cascade leads to a crash of the engine.
Logs claim “ParticleSystemComponent’s Template is null”
Ensure condition failed: Template [File:D:\Build++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Engine\Private\Particles\ParticleComponents.cpp] [Line: 3141]
I really have no idea what’s going on. I startup UE4, go into cascade by opening any particle system I created, then go to modify one parameter, then the engine instantly crashes.
works fine for me in 4.12.
can you record whatever you are doing so a dev can try and recreate the issue following your steps?
did you build engine from source? regular binary?
give us as much info as possible 
does this also happen when you create a new particle system?
If so/if not, perhaps try and migrate the effect, see if it also happens in a clean project, and if it does… send it over so one of the devs can check it out.
It also happens when I modify a value on a fresh particle system. It also happens in other projects on my computer, although none of the team that shares version control with me seem to have this issue.
hmm, try other ue4 versions… if that doesnt work… uhm…
a clean ue4 engine reinstall.
also full error log posting. this is way beyond my capabilities though 
Seems unavoidable at this point. Thanks for your time nonetheless.
Hey LordFriteuse-
Can you test creating a new project with Starter Content and let me know if you have the same crash when modifying one of the particle systems included ( for example). If this does crash for you, please add the callstack and log files from the crash for additional information. If you do not get a crash, please include the callstack/logs from your project that is crashing along with a copy of the particle system that causes the crash along with the steps taken to setup the particle system.
Just tried that and it crashed all the same. Here’s the log I pulled, plus the ones from my current projects : Google Drive: Sign-in
I’m currently installing the debug symbols to get the callstack files.
What OS are you on? Have you run all the software updates for your OS? And graphics drivers updates?
What exactly did you do after creating the project leading up to when the crash occurred? Can you also provide your DXDiag for more information. Also let me know if CleanCut’s suggestion of installing OS and video driver updates helps.
So, checked my OS, it’s up to date, updated my GFX driver, uninstalled UE4, shut my computer down, reboot, reinstall UE4 4.12.5, lauch my test project, in the starter content, pick the explosion effect, make the first emitter first burst count 2 instead of one, the engine instantly crashes.
The crash handler gives me that : http://pastebin.com/EZXhjn6n
And here is my DXDiag : http://pastebin.com/b1dxDrqW
I noticed that the amount of Ram in your machine is below the recommended specs for engine development (A new, community-hosted Unreal Engine Wiki - Announcements - Epic Developer Community Forums ). To help determine if the crash is caused by an out of memory issue, you’ll need to cause the crash again then go to ProjectName/Saved/Logs and grab/post the most recent .log file in that folder.
Here you are : Google Drive: Sign-in
Although, it seems strange because it has never been an issue until recently. I’ve worked on that project for months now with no trouble, and suddenly, without changing my computer configuration, it started being an issue, while neither the BP editor or the material editor have given me any kind of trouble.
If I might ask: how would insufficient memory cause the particular error encountered?
Hey LordFriteuse-
Modifying burst count as you mentioned does not cause a crash on my end. Can you let me know if the same crash occurs in 4.13 for you as well?
I can’t say for sure that memory is the cause for this issue. I simply saw that it could be an issue and wanted rule it out as a possible cause.
It seems the issue doesn’t appear on 4.13 projects, so the problem is going to be more or less solved for us as soon as Wwise is updated for 4.13 as well, at the very least I can get work done.
In any case, I can’t thank you enough for your time, and I hope I won’t have to bother you guys once more.